Status

Percentage Progress | Vectors (Formerly: SP Percentage progress bar)

backgroundColor	0052CC
percentage	100

Owner

Prasad Naidu

Stakeholders

NG-ext, Bernard PILLAY-ext, Lawrence GARCIA-ext, Angel Luis

Purpose

The purpose of this document is to define the conversion approach to create Business Partners - FI Customer (FLCU00) in S/4 HANA.

Business Partner - FI Customer Role captures the Customer’s FI data attributes such as Reconciliation Account, Tax Code, etc. at the Company Code level.

Conversion Scope

The scope of this document covers the approach for converting active Customer Master Data from Legacy Source Systems into S/4HANA Business Partner FI Customer (FLCU00) Master Data Design Standard.

The CNV-3007 Business Partners – General (Role 000000) relevancy criteria will also be used for this conversion document.

The relevancy already applied in CNV3007. Once the customers in scope are finalized and extracted, we need to check the KNB1, KNB5 and KNBW fields for those customers in the legacy system and apply the transformation rules as per the source-to-target mappings.

List of source systems and approximate number of records

Source	Scope	Source Approx. No. of records	Target System	Target Approx. No. of records
PF2	Based on relevancy criteria exists in General Role / data as per CNV-3007 Business Partners - General (Role 000000)	55371	S4	4200
WP2	Based on relevancy criteria exists in General Role / data as per CNV-3007 Business Partners - General (Role 000000)	36983	S4	24000

Additional Information

Multi-language Requirement

Document Management

Legal Requirement

Special Requirements

Target Design

The technical design of the target for this conversion approach.

Table	Field	Data Element	Field Description	Data Type	Length	Requirement
KNB1	KUNNR	KUNNR	Business Partner Number	CHAR	10	Required
KNB1	BUKRS	BUKRS	COMPANY CODE	CHAR	4	Required
KNB1	AKONT	AKONT	RECONCILIATION ACCOUNT	CHAR	10	Required
KNB1	KNRZE	KNRZE	HEAD OFFICE	CHAR	10	Optional
KNB1	ZUAWA	DZUAWA	SORT KEY	CHAR	3	Required
KNB1	FDGRV	FDGRV	PLANNING GROUP	CHAR	10	Optional
KNB1	ALTKN	ALTKN	PREVIOUS ACCOUNT NUMBER	CHAR	10	Optional
KNB1	GRICD	J_1AGICD_D	ACTIVITY CODE	CHAR	2	Optional
KNB1	ZTERM	DZTERM	PAYMENT TERMS	CHAR	4	Required
KNB1	GUZTE	GUZTE	CREDIT MEMO PAYMENT TERMS	CHAR	4	Optional
KNB1	TOGRU	TOGRU	TOLERANCE GROUP	CHAR	4	Optional
KNB1	KULTG	KULTG	CHECK CASHING TIME	DEC	3	Optional
KNB1	XZVER	XZVER	RECORD PAYMENT HISTORY	CHAR	1	Required
KNB1	ZWELS	DZWELS	PAYMENT METHODS	CHAR	10	Required
KNB1	ZAHLS	DZAHLS	PAYMENT BLOCK	CHAR	1	Optional
KNB1	XVERR	XVERR_KNB1	CLEARING WITH VENDOR	CHAR	1	Optional
KNB1	XPORE	XPORE	SINGLE PAYMENT	CHAR	1	Optional
KNB1	WEBTR	WEBTR	BILL/EX. LIMIT	CURR	13	Optional
KNB1	LOCKB	LOCKB	LOCKBOX	CHAR	7	Optional
KNB1	BUSAB	BUSAB	ACCOUNTING CLERK	CHAR	2	Optional
KNB1	EIKTO	EIKTO_D	ACCOUNT AT CUSTOMER	CHAR	12	Optional
KNB1	ZSABE	DZSABE_D	USER AT CUSTOMER	CHAR	15	Optional
KNB1	TLFNS	TLFNS	ACCOUNTING CLERKS TELEPHONE NUMBER	CHAR	30	Optional
KNB1	TLFXS	TLFXS	ACCOUNTING CLERKS FAX NUMBER	CHAR	31	Optional
KNB1	INTAD	INTAD	CLERKS INTERNET ADDRESS	CHAR	130	Optional
KNB1	XDEZV	XDEZV	LOCAL PROCESSING	CHAR	1	Optional
KNB1	KVERM	KVERM	ACCOUNT MEMO	CHAR	30	Optional
KNB1	SPERR	SPERB_B	COMPANY CODE POSTING BLOCK	CHAR	1	Optional
KNB1	LOEVM	LOEVM_B	COMPANY CODE DELETION FLAG	CHAR	1	Optional
KNB1	EKVBD	EKVBD	Account Number Buying Group	CHAR	10	Optional
KNB5	MAHNA	MAHNA	DUNNING PROCEDURE	CHAR	4	Optional
KNB5	KNRMA	KNRMA	DUNNING RECIPIENT	CHAR	10	Optional
KNB5	BUSAB	BUSAB_MA	DUNNING CLERK	CHAR	2	Optional
KNB5	MABER	MABER_MA	Dunning Area	CHAR	2	Mandatory
KNBW	WITHT	WITHT	WITHHOLDING TAX TYPE	CHAR	2	Optional
KNBW	WT_WITHCD	WT_WITHCD	WITHHOLDINGTAX CODE	CHAR	2	Optional
KNBW	WT_AGENT	WT_WTAGT	WITHHOLDING AGENT	CHAR	1	Optional
KNBW	WT_AGTDF	WT_AGTDF	WITHHOLDING OBLIGATION FROM	DATS	8	Optional
KNBW	WT_AGTDT	WT_AGTDT	WITHHOLDING OBLIGATION TO	DATS	8	Optional
KNBW	WT_WTSTCD	WT_WTSTCD	WITHHOLDING TAX ID NUMBER	CHAR	16	Optional
KNBW	WT_EXNR	WT_EXNR	Exemption Certificate Number	CHAR	15	Optional
KNBW	WT_EXRT	WT_EXRT	Exemption Rate	DEC	5	Optional
KNBW	WT_EXDF	WT_EXDF	Date on Which Exemption Begins	DATS	8	Optional
KNBW	WT_EXDT	WT_EXDT	Date on Which Exemption Ends	DATS	8	Optional
KNBW	WT_WTEXRS	WT_WTEXRS	Reason for Exemption	CHAR	2	Optional
BUT100	PARTNER	BU_PARTNER	Business Partner Number	CHAR	10	Mandatory
BUT100	RLTYP	BU_PARTNERROLE	BP Role	CHAR	6	Mandatory

Data Cleansing

ID	Criticality	Error Message/Report Description	Rule	Output	Source System
		NA

Conversion Process

The ETL (Extract, Transform, Load) process is a structured approach to data migration and management, ensuring high-quality data is seamlessly transferred across systems. Here’s a breakdown of its key components:

Extraction

Data will be extracted using Syniti ADMM from ECC

2. Transformation
Once extracted, the data undergoes cleansing, consolidation, and governance. This step ensures data integrity, consistency, and compliance with business rules. The transformation process includes:
- Data validation to remove inconsistencies.
- Standardization to align formats across datasets.
- Business rule application to refine data for operational use.

3. Loading
The transformed data is then loaded into the target S4 Hana system.

Data Privacy and Sensitivity

N/A

Extraction

Extract data from a source into . There are 2 possibilities:

The data exists. connects to the source and loads the data into . There are 3 methods:
1. Perform full data extraction from relevant tables in the source system(s).
2. Perform extraction through the application layer.
3. Only if ; cannot connect to the source, data is loaded to the repository from the provided source system extract/report.
The data does not exist (or cannot be converted from its current state). The data is manually collected by the business directly in . This is to be conducted using DCT (Data Collection Template) in

The agreed Relevancy criteria is applied to the extracted records to identify the records that are applicable for the Target loads

Extraction Run Sheet

Req#	Requirement Description	Team Responsible
Extraction Scope Definition	- Identify the source systems and databases involved. - Define the data objects (tables, fields, records) to be extracted. - Establish business rules for data selection.	Syniti Syniti
Extraction Methodology	- Specify the extraction approach (full, incremental, or delta extraction). - Determine the tools and technologies used. - Define data filtering criteria to exclude irrelevant records.	Syniti
Extraction Execution Plan	- Establish execution timelines and batch processing schedules. - Assign responsibilities for extraction monitoring. - Document dependencies on other migration tasks.	Syniti
Data Quality and Validation	- Define error handling mechanisms for extraction failures.	Syniti

Selection Screen

Selection Ref Screen	Parameter Name	Selection Type	Requirement	Value to be entered/set
N/A

Data Collection Template (DCT)

Data Collection Template is required for enrichment purposes eg. legacy fields are missing data which is mandatory in target S4. The DCT fields are target values requiring no transformation.

Field Name	Field Description	Rule
KNB1- KUNNR	CUSTOMER NUMBER
KNB1 - BUKRS	COMPANY CODE
KNB1-AKONT	RECONCILIATION ACCOUNT
KNB1- ZUAWA	SORT KEY
KNB1- ZTERM	PAYMENT TERMS
KNB1- XZVER	RECORD PAYMENT HISTORY
KNB1- ZWELS	PAYMENT METHODS
KNB5-MABER	DUNNING AREA

Extraction Dependencies

1	Source System Availability Ensure that the source database or application is accessible. Confirm that necessary credentials and permissions are granted	Syensqo IT
2	Data Structure Identify relationships between tables, views, and stored procedures.	Syniti
3	Referential Integrity Ensure dependent records are extracted together.	Syniti
4	Extraction Methodology Define whether extraction is full, incremental, or delta-based. Establish batch processing schedules for large datasets.	Syniti
5	Performance and Scalability Considerations Optimize extraction queries to prevent system overload. Ensure network bandwidth supports data transfer volumes.	Syniti
6	Security and Compliance Adhere to regulatory standards for sensitive information if applicable	Syniti

Transformation

The Target fields are mapped to the applicable Legacy field that will be its source, this is a 3-way activity involving the Business, Functional team and Data team. This identifies the transformation activity required to allow to make the data Target ready:

Perform value mapping and data transformation rules.
1. Legacy values are mapped to the to-be values (this could include a default value)
2. Values are transformed according to the rules defined in
Prepare target-ready data in the structure and format that is required for loading via prescribed Load Tool. This step also produces the load data ready for business to perform Pre-load Data Validation

Transformation Run Sheet

N/A

Transformation Rules

Rule	Source system	Source Table	Source Field	Field Description	Target System	Target Table	Target Field	Target Description	Transformation logic
1	PF2/WP2	KNB1	KUNNR	Customer Number	S/4HANA	KNB1	KUNNR	Business Partner Number	Map from source to target using Business Partner mapping table
2	PF2/WP2	KNB1	BUKRS	COMPANY CODE	S/4HANA	KNB1	BUKRS	COMPANY CODE	Derive via Company Code mapping
3	PF2/WP2	KNB1	AKONT	RECONCILIATION ACCOUNT	S/4HANA	KNB1	AKONT	RECONCILIATION ACCOUNT	Derive via GL account mapping
4	PF2/WP2	KNB1	KNRZE	HEAD OFFICE	S/4HANA	KNB1	KNRZE	HEAD OFFICE	Copy As is
5	PF2/WP2	KNB1	ZUAWA	SORT KEY	S/4HANA	KNB1	ZUAWA	SORT KEY	Derive via Sort key mapping- Default to 009 if blank.
6	PF2/WP2	KNB1	FDGRV	PLANNING GROUP	S/4HANA	KNB1	FDGRV	PLANNING GROUP	Derive via planning group mapping
7	PF2/WP2	KNB1	ALTKN	PREVIOUS ACCOUNT NUMBER	S/4HANA	KNB1	ALTKN	PREVIOUS ACCOUNT NUMBER	Legacy customer number (KNB1 - KUNNR)
8	PF2/WP2	KNB1	GRICD	ACTIVITY CODE	S/4HANA	KNB1	GRICD	ACTIVITY CODE	Derive via activity code mapping
9	PF2/WP2	KNB1	ZTERM	PAYMENT TERMS	S/4HANA	KNB1	ZTERM	PAYMENT TERMS	Derive via Payment Terms mapping
10	PF2/WP2	KNB1	GUZTE	CREDIT MEMO PAYMENT TERMS	S/4HANA	KNB1	GUZTE	CREDIT MEMO PAYMENT TERMS	Derive via Payment Terms mapping
11	PF2/WP2	KNB1	TOGRU	TOLERANCE GROUP	S/4HANA	KNB1	TOGRU	TOLERANCE GROUP	Derive via tolerance group mapping
12	PF2/WP2	KNB1	KULTG	CHECK CASHING TIME	S/4HANA	KNB1	KULTG	CHECK CASHING TIME	Copy As is
13	PF2/WP2	KNB1	XZVER	RECORD PAYMENT HISTORY	S/4HANA	KNB1	XZVER	RECORD PAYMENT HISTORY	Copy As is
14	PF2/WP2	KNB1	ZWELS	PAYMENT METHODS	S/4HANA	KNB1	ZWELS	PAYMENT METHODS	Derive via Payment Methods mapping
15	PF2/WP2	KNB1	ZAHLS	PAYMENT BLOCK	S/4HANA	KNB1	ZAHLS	PAYMENT BLOCK	Copy As is
16	PF2/WP2	KNB1	XVERR	CLEARING WITH VENDOR	S/4HANA	KNB1	XVERR	CLEARING WITH VENDOR	Copy As is
17	PF2/WP2	KNB1	XPORE	SINGLE PAYMENT	S/4HANA	KNB1	XPORE	SINGLE PAYMENT	Copy As is
18	PF2/WP2	KNB1	WEBTR	BILL/EX. LIMIT	S/4HANA	KNB1	WEBTR	BILL/EX. LIMIT	Copy As is
19	PF2/WP2	KNB1	LOCKB	LOCKBOX	S/4HANA	KNB1	LOCKB	LOCKBOX	Copy As is
20	PF2/WP2	KNB1	BUSAB	ACCOUNTING CLERK	S/4HANA	KNB1	BUSAB	ACCOUNTING CLERK	Copy As is
21	PF2/WP2	KNB1	EIKTO	ACCOUNT AT CUSTOMER	S/4HANA	KNB1	EIKTO	ACCOUNT AT CUSTOMER	Derive via Account at customer mapping
22	PF2/WP2	KNB1	ZSABE	USER AT CUSTOMER	S/4HANA	KNB1	ZSABE	USER AT CUSTOMER	Copy As is
23	PF2/WP2	KNB1	TLFNS	ACCOUNTING CLERKS TELEPHONE NUMBER	S/4HANA	KNB1	TLFNS	ACCOUNTING CLERKS TELEPHONE NUMBER	Copy As is
24	PF2/WP2	KNB1	TLFXS	ACCOUNTING CLERKS FAX NUMBER	S/4HANA	KNB1	TLFXS	ACCOUNTING CLERKS FAX NUMBER	Copy As is
25	PF2/WP2	KNB1	INTAD	CLERKS INTERNET ADDRESS	S/4HANA	KNB1	INTAD	CLERKS INTERNET ADDRESS	Copy As is
26	PF2/WP2	KNB1	XDEZV	LOCAL PROCESSING	S/4HANA	KNB1	XDEZV	LOCAL PROCESSING	Copy As is
27	PF2/WP2	KNB1	KVERM	ACCOUNT MEMO	S/4HANA	KNB1	KVERM	ACCOUNT MEMO	Copy As is
28	PF2/WP2	KNB1	SPERR	COMPANY CODE POSTING BLOCK	S/4HANA	KNB1	SPERR	COMPANY CODE POSTING BLOCK	Copy As is
29	PF2/WP2	KNB1	LOEVM	COMPANY CODE DELETION FLAG	S/4HANA	KNB1	LOEVM	COMPANY CODE DELETION FLAG	Copy As is
30	PF2/WP2	KNB1	EKVBD	Account Number Buying Group	S/4HANA	KNB1	EKVBD	Account Number Buying Group	Derive via Account at customer/Vendor mapping
31	PF2/WP2	KNB5	MAHNA	DUNNING PROCEDURE	S/4HANA	KNB5	MAHNA	DUNNING PROCEDURE	Derive from Dunning procedure mapping
32	PF2/WP2	KNB5	KNRMA	DUNNING RECIPIENT	S/4HANA	KNB5	KNRMA	DUNNING RECIPIENT	Derive via Account at customer mapping
33	PF2/WP2	KNB5	BUSAB	DUNNING CLERK	S/4HANA	KNB5	BUSAB	DUNNING CLERK	Copy As is
34	PF2/WP2	KNB5	MABER	DUNNING AREA	S/4HANA	KNB5	MABER	DUNNING AREA	Copy As is
35	PF2/WP2	KNBW	WITHT	WITHHOLDING TAX TYPE	S/4HANA	KNBW	WITHT	WITHHOLDING TAX TYPE	Derive from Withholding tax mapping
36	PF2/WP2	KNBW	WT_WITHCD	WITHHOLDINGTAX CODE	S/4HANA	KNBW	WT_WITHCD	WITHHOLDINGTAX CODE	Derive from Withholding tax mapping
37	PF2/WP2	KNBW	WT_AGENT	WITHHOLDING AGENT	S/4HANA	KNBW	WT_AGENT	WITHHOLDING AGENT	Copy As is
38	PF2/WP2	KNBW	WT_AGTDF	WITHHOLDING OBLIGATION FROM	S/4HANA	KNBW	WT_AGTDF	WITHHOLDING OBLIGATION FROM	Copy As is
39	PF2/WP2	KNBW	WT_AGTDT	WITHHOLDING OBLIGATION TO	S/4HANA	KNBW	WT_AGTDT	WITHHOLDING OBLIGATION TO	Copy As is
40	PF2/WP2	KNBW	WT_WTSTCD	WITHHOLDING TAX ID NUMBER	S/4HANA	KNBW	WT_WTSTCD	WITHHOLDING TAX ID NUMBER	Copy As is
41	PF2/WP2	KNBW	WT_EXNR	Exemption Certificate Number	S/4HANA	KNBW	WT_EXNR	Exemption Certificate Number	Copy As is
42	PF2/WP2	KNBW	WT_EXRT	Exemption Rate	S/4HANA	KNBW	WT_EXRT	Exemption Rate	Copy As is
43	PF2/WP2	KNBW	WT_EXDF	Date on Which Exemption Begins	S/4HANA	KNBW	WT_EXDF	Date on Which Exemption Begins	Copy As is
44	PF2/WP2	KNBW	WT_EXDT	Date on Which Exemption Ends	S/4HANA	KNBW	WT_EXDT	Date on Which Exemption Ends	Copy As is
45	PF2/WP2	KNBW	WT_WTEXRS	Reason for Exemption	S/4HANA	KNBW	WT_WTEXRS	Reason for Exemption	Copy As is
46	PF2/WP2	N/A	N/A	N/A	S4HANA	BUT100	PARTNER	Business Partner Number	Refer to XREF of Business Partner
47	PF2/WP2	N/A	N/A	N/A	S4HANA	BUT100	RLTYP	BP Role	Default to FLCU00

Transformation Mapping

Mapping Table Name	Description
Legacy Customer-BP Master Mapping	Legacy to S4 Business Partner customer mapping
Business Partner deDupe mapping (Global Data)	dedupe Golden-child (Global) mapping
Company Code Mapping	Legacy to S4 Company Code Mapping
Payment Terms Mapping	Legacy to S4 Payment Terms Mapping
Payment Method Mapping	Payment Method Mapping
Tax Category Mapping	Legacy to S4 Tax Category Mapping
Reconciliation Account Mapping	Legacy to S4 Reconciliation Account Mapping
Sort Key Mapping	Legacy to S4 Sort Key Mapping
Planning Group Mapping	Legacy to S4 Planning Group Mapping
Withholding tax type / code Mapping	Legacy to S4 Withholding tax type / code Mapping
Tolerance Group Mapping	Legacy to S4Tolerance Group Mapping
Payment block Mapping	Legacy to S4Payment block Mapping
Authorization Group Mapping	Legacy to S4Authorization Group Mapping
Planning Group Mapping	Legacy to S4Planning Group Mapping
House bank mapping	Legacy to S4House bank mapping
Tolerance Group mapping	Legacy to S4Tolerance Group mapping
Payment Method Supplement mapping	Legacy to S4 Payment Method Supplement mapping
Recipient type mapping	Legacy to S4 Recipient type mapping
Activity code mapping	Legacy to S4 Activity code mapping

Transformation Dependencies

List the steps that need to occur before transformation can commence

1	Source Data Integrity - Ensure extracted data is complete, accurate, and consistent. - Validate that data types and formats align with transformation requirements.	Syniti
2	Referential Integrity - Ensure dependent records are transformed together or in advance	Syniti
3	Transformation Logic and Mapping - Define data mapping rules between source and target schemas.	Data Team
4	Performance and Scalability Considerations - Optimize transformation processes for large datasets. - Ensure system resources can handle transformation workloads	Syniti
5	Logging and Error Handling - Maintain detailed logs of transformation activities. - Define error-handling procedures for failed transformations	Syniti

Pre-Load Validation

Project Team

Completeness

Verify count	Verify counts between source and target databases. Identify missing or duplicated records.
Validate the mandatory fields	Validate there is value for all the mandatory fields

Accuracy

Validate the transformation	Validate the fields which require transformation have the value after transformation instead of the original field value
Check Data Consistency	Compare field values across systems Validate data formats and structures

Business

Completeness

Verify Count for all customers	Verify that the record count in the pre-load file is the same as the record count based on the relevancy (including deduplication) results
Verify Relevancy Rules	Verify that the relevancy rules were correctly applied

Accuracy

Verify Data Accuracy	Verify that all the data in the load table/file is accurate as per signed-off transformation rules
Review Error Reports	Verify that all necessary error reports have been validated, and that errors have been addressed.
Verify Transformation Rules	Verify that the transformation rules are correct and have been carried out correctly

Load

The load process includes:

Execute the automated data load into target system using load tool or product the load file if the load must be done manually
Once the data is loaded to the target system, it will be extracted and prepared for Post Load Data Validation

Load Run Sheet

Item #	Step description	Team responsible
1	Load Sample Business Partners	Data
2	Validate sample Business Partners	Data
3	Load remaining Business Partners	Data
4	Validate data loaded for Business Partners	Data
5	Load Sample BP Type – Customer Contact Persons	Data
6	Validate sample BP Type – Customer Contact Persons	Data
7	Load remaining BP Type – Customer Contact Persons	Data
8	Validate data loaded for BP Type – Customer Contact Persons	Data
9	Load Sample BP Type – Vendor Contact Persons	Data
10	Validate sample BP Type – Vendor Contact Persons	Data
11	Load remaining BP Type – Vendor Contact Persons	Data
12	Validate data loaded for BP Type – Vendor Contact Persons	Data
13	Load Sample BP Type - Bank Contacts (First Name, Last Name)	Data
14	Validate sample BP Type - Bank Contacts (First Name, Last Name)	Data
15	Load remaining BP Type - Bank Contacts (First Name, Last Name)	Data
16	Validate data loaded for BP Type - Bank Contacts (First Name, Last Name)	Data
17	Load Sample BP Type – BP General, FI Customer, FI Vendor	Data
18	Validate sample BP Type – BP General, FI Customer, FI Vendor	Data
19	Load remaining BP Type – BP General, FI Customer, FI Vendor	Data
20	Validate data loaded for BP Type – BP General, FI Customer, FI Vendor	Data
21	Load Sample Vendors Default Partner	Data
22	Validate sample Vendors Default Partner	Data
23	Load remaining Vendors Default Partner	Data
24	Validate data loaded for Vendors Default Partner	Data
25	Load Sample BP - General for remaining customer roles	Data
26	Validate sample BP - General for remaining customer roles	Data
27	Load remaining BP - General for remaining customer roles	Data
28	Validate data loaded for BP - General for remaining customer roles	Data
29	Load Sample BP – Customers with Default Partner	Data
30	Validate sample BP – Customers with Default Partner	Data
31	Load remaining BP – Customers with Default Partner	Data
32	Validate data loaded BP – Customers with Default Partner	Data
33	Load Sample BP - Bank Role	Data
34	Validate sample BP - Bank Role	Data
35	Load remaining BP - Bank Role	Data
36	Validate data loaded BP - Bank Role	Data
37	Load Sample BP Relationship Contact Person to Organisation (Will create KNVK records)	Data
38	Validate sample BP Relationship Contact Person to Organisation (Will create KNVK records)	Data
39	Load remaining BP Relationship Contact Person to Organisation (Will create KNVK records)	Data
40	Validate data loaded for BP Relationship Contact Person to Organisation (Will create KNVK records)	Data
41	Load Sample BP - Carrier	Data
42	Validate sample BP - Carrier	Data
43	Load remaining BP - Carrier	Data
44	Validate data loaded BP - Carrier	Data
45	Load Sample BP - Credit Management	Data
46	Validate sample BP - Credit Management	Data
47	Load remaining BP - Credit Management	Data
48	Validate data loaded BP - Credit Management	Data
49	Load Sample BP Collections Management	Data
50	Validate sample BP Collections Management	Data
51	Load remaining BP Collections Management	Data
52	Validate data loaded BP Collections Management	Data

Load Phase and Dependencies

Configuration

1	Obtain the approved upload USER ID’s to be used (e.g. Firefighter ID)
2	SAP USER profile (SU3) Date and Decimal Notation Formats are in sync with the load format
3	Company Code Configuration
4	BP Grouping
5	Customer Account Group
6	BP Number Range
7	Payment Terms Configuration
8	Payment Method Configuration
9	Reconciliation Account Configuration
10	Withholding Tax Types Configuration
11	Sort Key configuration
12	Planning Group configuration
13	Tolerance Group configuration
14	Authorization Group configuration

Conversion Objects

N/A

Error Handling

Configuration

<configuration> is not valid/missing

If it is a missing configuration item then engage Functional team to expedite and fix the error in the system.

Invalid Data

<parameter> is not valid.

The parameter entry needs to be reviewed (ex. invalid payment terms).

If it is an invalid data, business needs to review and correct the source of the data either in PF2/PI2/WP2

Technical Setup

Interface / Connection issue within target system’s landscape

N/A – the data will be loaded directly to S/4HANA environment

Post-Load Validation

Project Team

Completeness

Perform Data Count	Validate that migrated data matches source records.
Perform Source-to-Target Comparisons	Validate all the mandatory fields are populated as per the loading file

Accuracy

Data Accuracy	Data team to verify that all the data in the load table/file is accurate as per signed-off transformation rules
Error Reports	Verify that all necessary error reports have been validated, and that errors have been addressed.

Business

Completeness

Perform Source-to-Target Comparisons	Validate that migrated data matches source records counts.
Conduct Post-Migration Reconciliation	Go through reports comparing pre- and post-migration data provided by Syniti.

Accuracy

Verify Data Accuracy	Data team to verify that all the data in the load table/file is accurate as per signed-off transformation rules
Review Error Reports	Verify that all necessary error reports have been validated, and that errors have been addressed.
Validate Loaded Data	Validate, as per the loads files signed-off, that all records were created

Key Assumptions

Master Data Standard is up to date as on the date of documenting this conversion approach and data load.
is in scope based on data design and any exception requested by business.

Change log

Change History

limit	10

Workflow history

Workflow Report

parent	@self
hideheader	true
type	approvals

Apr 10, 2026	Actor	Type	Activity	Version
Lead Approval	JAIN-ext, Gaurav	State	changed expiry date to '17 Apr, 2026 02:35 pm' at 2:35 pm
Lead Approval	JAIN-ext, Gaurav	State	changed state to Lead Approval at 2:35 pm	v37
Tech Review	JAIN-ext, Gaurav	State	gave Syniti Team Review approval at 2:35 pm
		State	changed expiry date to '15 Apr, 2026 02:34 pm' at 2:34 pm
		State	changed state to Tech Review at 2:34 pm Approved	v37
Pending adjustment	JAIN-ext, Gaurav	State	changed state to Pending adjustment at 2:34 pm	v37
Revision under Review	JAIN-ext, Gaurav	State	gave Minor change rejection at 2:34 pm
Revision under Review	JAIN-ext, Gaurav	State	changed state to Revision under Review at 2:34 pm Approved	v37
From Apr 07, 2026 to Apr 10, 2026
Revision in Progress	NAIDU-ext, Prasad	Edit	updated the page at 10:23 am

Workflow history

Space shortcuts

Page tree

Page History

Versions Compared

Old Version 35

New Version 36

Key

Purpose

Conversion Scope

Additional Information

Multi-language Requirement

Document Management

Legal Requirement

Special Requirements

Target Design

Data Cleansing

Conversion Process

Data Privacy and Sensitivity

Extraction

Extraction Run Sheet

Selection Screen

Data Collection Template (DCT)

Extraction Dependencies

Extraction Dependencies

Transformation

Transformation Run Sheet

Transformation Mapping

Transformation Dependencies

Pre-Load Validation

Project Team

Completeness

Completeness

Load

Load Run Sheet

Configuration

Conversion Objects

Error Handling

Post-Load Validation

Project Team

Completeness

Accuracy

Business

Completeness

Accuracy

Key Assumptions

See also

Change log

Workflow history