Status
Owner	RUAN-ext, Eric
Stakeholders	The business stakeholders involved in making, reviewing, and endorsing this decision. Type @ to mention people by name

Purpose

The purpose of this document is to define the conversion approach to migrate Business Partners - Prospect (BUP002) in S/4 HANA.

In Salesforce, a Prospect is typically used to track potential customers who have shown interest but have not yet been qualified as quotations or sales order. They may include essential details like company information, interaction history, and engagement level.

In SAP S/4HANA, the Prospect is intended to be represented similarly. Prospects are classified as BP (Business Partners) under the Customer category, with attributes that allow future conversion into full-fledged customers. 

Conversion Scope

The scope of this document covers the approach for converting active Prospect from Legacy Source Systems into S/4HANA following the Business Partners - Prospect (BUP002) Master Data Design Standard.

The data from legacy system includes:

1. Under the Salesforce Account object, the Partner Type is Prospect and there is no deletion indicator for the account.
2. The Account Organization is SCO (Syensqo).
3. For prospect created for more than 2 years, there is usage for the prospect within the 2 years, e.g., there are visit reports, leads or sales opportunities created. 
4. For prospect created within 2 years, it is not in any blocked status
5. The prospect is for GBU within scope. 

The data from legacy system excludes:

1. The Prospect is defined exclusively for GBU out of scope, such as Oil&Gas, Aroma.
2. The Prospect has already been converted to customer.
3. Exclude Status for the Prospect is Rejected

List of source systems and approximate number of records

Source	Scope	Source Approx No. of Records	Target System	Target Approx No. of Records
iCare	Active Prospect	215	S4 Hana	215
CoreCRM	Active Prospect	1824	S4 Hana	1824

Additional Information

Multi-language Requirement

The prospect may contain local language. Therefore, the conversion will also need to support the multi-language address.  Below languages (International versions) are supported based on KDD055 - Multiple Language Support. 

It will support 4 Core Languages (English, French, Italian and Mandarin).

Document Management

N/A.

Legal Requirement

CMMC 2.0 is a mandatory DoD cybersecurity certification for contractors handling Controlled Unclassified Information (CUI) and Federal Contract Information (FCI). CUI includes sensitive technical data (e.g., design specs, system info) related to U.S. military and space applications. The Composites Business handles CUI and is therefore within CMMC scope. Without certification, the business risks disqualification from existing and future DoD programs.
It is mandatory to implement CMMC-compliant systems and processes to for all the organizations that are dealing with CUI.

Special Requirements

Due to compliance requirement, there will be three SAP instances, one for Rest of the World (ROW), one for China and one for CUI. Prospect will be migrated into all three SAP instances.

Target Design

With Functional input, document the technical design of the target fields that are in the scope of this document.

The technical design of the target for this conversion approach.

Table	Field	Data Element	Field Description	Data Type	Length	Requirement
BUT000	PARTNER	PARTNER	Business Partner	CHAR	10	Mandatory
BUT000	BU_GROUP	BU_GROUP	Grouping	CHAR	4	Mandatory
BUT000	BPEXT	BPEXT	External BP Number	CHAR	20	Mandatory
BUT000	BU_SORT1	BU_SORT1	Search Term 1	CHAR	20	Mandatory
BUT000	NAME_ORG1	NAME_ORG1	Name 1	CHAR	40	Mandatory
BUT000	NAME_ORG2	NAME_ORG2	Name 2	CHAR	40	Conditional
BUT000	IND_SECTOR	IND_SECTOR	Industry sector	CHAR	10	Conditional
ADRC	NATION	NATION	Address Version	CHAR	1	Conditional
ADRC	NAME1	NAME1	Name	CHAR	40	Mandatory
ADRC	NAME2	NAME2	Name 2	CHAR	40	Conditional
ADRC	NAME_CO	NAME_CO	c/o	CHAR	40	Conditional
ADRC	CITY1	CITY1	City	CHAR	40	Conditional
ADRC	CITY2	CITY2	District	CHAR	40	Conditional
ADRC	POST_CODE1	POST_CODE1	Postal Code	CHAR	10	Conditional
ADRC	TRANSPZONE	TRANSPZONE	Transportation Zone	CHAR	10	Conditional
ADRC	STREET	STREET	Street	CHAR	60	Conditional
ADRC	HOUSE_NUM1	HOUSE_NUM1	House Number	CHAR	10	Conditional
ADRC	HOUSE_NUM2	HOUSE_NUM2	Supplement	CHAR	10	Conditional
ADRC	STR_SUPPL1	STR_SUPPL1	Street 2	CHAR	40	Conditional
ADRC	STR_SUPPL2	STR_SUPPL2	Street 3	CHAR	40	Conditional
ADRC	STR_SUPPL3	STR_SUPPL3	Street 4	CHAR	40	Conditional
ADRC	LOCATION	LOCATION	Street 5	CHAR	40	Conditional
ADRC	COUNTRY	COUNTRY	Country/Region Key	CHAR	3	Mandatory
ADRC	LANGU	LANGU	Language Key	LANG	1	Mandatory
ADRC	REGION	REGION	Region	CHAR	3	Mandatory
ADRC	SORT1	SORT1	Search Term 1	CHAR	20	Mandatory
ADRC	TEL_NUMBER	TEL_NUMBER	Telephone	CHAR	30	Conditional
ADR6	SMTP_ADDR	SMTP_ADDR	E-Mail Address	CHAR	241	Conditional
KNA1	KTOKD	KTOKD	Account group	CHAR	4	Mandatory
BUT100	PARTNER	PARTNER	Business Partner	CHAR	10	Mandatory
BUT100	RLTYP	RLTYP	BP Role	CHAR	6	Mandatory
ADR12	URI_SRCH	URI_SRCH	URI address	CHAR	50	Conditional

Data Cleansing

All data cleansing should take place in the data source system as defined in this document, unless system limitations prevent it.

If data cleansing is managed outside of the source system (e.g. Syniti Migrate, 3rd Party Vendor, DCT), the necessary documentation must be produced and appended to this deliverable for sign-off.

ID	Criticality	Error Message/Report Description	Rule	Output	Source System
3009-001	C1	Identify inactive prospect	For prospect created for more than 2 years, there is no usage for the prospect within the 2 years, e.g., there are visit reports, leads or sales opportunities created.	Prospect Account ID/Name/Address/Last usage / Account Manager	iCare/Core
3009-001	C2	Identify Duplicate Prospect	Multiple prospects refers to the same entity, e.g., the organization name/country/address is identical or very similar	Prospect Account ID/Name/Address/Last usage / Account Manager	iCare/Core

Conversion Process

The high-level process is represented by the diagram below:

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:

1. Extraction
The process begins with extracting metadata and raw data from source systems, such as Syensqo CRM system (i.e., iCare/CoreCRM) periodically. The extracted data is then staged for transformation.

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 Syniti Migrate. There are 2 possibilities:

1. The data exists. Syniti Migrate connects to the source and loads the data into Syniti Migrate. 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 Syniti Migrate; cannot connect to the source, data is loaded to the repository from the provided source system extract/report.
2. The data does not exist (or cannot be converted from its current state). The data is manually collected by the business directly in Syniti Migrate. This is to be conducted using DCT (Data Collection Template) in Syniti Migrate

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

For SAP CUI related entities, it will be alternative extraction process and the data will be stored in approved tools.

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 / LTC Data team
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

If applicable, this section will give the details on any selection screen parameters, including the parameter type, that are required to be entered to ensure consistent data extracts.

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

Data Collection Template (DCT)

Target Ready Data Collection Template will be created for Data Object data with exception of some fields which require transformation as mentioned in the transformation rule.

<Object> DCT Rules

Field Name	Field Description	Rule
N/A

Extraction Dependencies

List the steps that need to occur before extraction can commence

Item #	Step Description	Team Responsible
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 Syniti Migrate to make the data Target ready:

1. 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 Syniti Migrate
2. 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

Item #	Step Description	Team Responsible
1	Identify target S/4HANA fields and determine applicable legacy source fields from both Salesforce systems iCare, Core CRM	Functional Team (L2C)+ Data Team (L2C)
2	Map legacy field values to S/4HANA target values (including field-level mapping and technical names)	Data Team (L2C), Data Team (Syniti)
3	Define value mapping rules for fields requiring standardization or harmonization across the two source systems iCare, Core CRM	Functional Team (L2C)+ Data Team (L2C)
4	Identify and agree on default values where legacy data is incomplete or inconsistent	Business Team + Functional Team (L2C)
5	Configure transformation rules in Syniti Migrate	Data Team (Syniti), Data Team (L2C)
6	Review transformation logic and mappings with Business for confirmation	Business Team + Functional Team (L2C)
7	Perform initial transformation run and generate draft target-ready dataset	Data Team (Syniti),
8	Review draft target-ready data for structure and completeness	Data Team (L2C), Functional Team (L2C)
9	Share transformed data with Business for Pre-load Validation	Business Team
10	Incorporate feedback from Business and refine mappings or transformation logic as needed	Data Team (L2C)
11	Finalize and approve transformed data as Target Ready Load File	Business + Functional (L2C) + Data Team (L2C)
12	Handover final file to Load Team or trigger the load via Syniti Load Workbench	Data Team (Syniti), Data Load Team

Transformation Rules

Rule #	Source system	Source Table	Source Field	Source Description	Target System	Target Table	Target Field	Target Description	Transformation Logic
1	Core CRM				S4 Hana	BUT000	PARTNER	Business Partner	Rule - Apply external number range from 1000000 to 99999999, use the running number from 1000000
2	Core CRM				S4 Hana	BUT000	BU_GROUP	Grouping	Default - BP02
3	Core CRM		SLV10_Acc_Id__c	Account Id	S4 Hana	BUT000	BPEXT	External BP Number	Copy
4	Core CRM		SLV41_Customer_Name__c	Customer Name	S4 Hana	BUT000	BU_SORT1	Search Term 1	Rule - Copy first 20 char
5	Core CRM		SLV41_Customer_Name__c	Customer Name	S4 Hana	BUT000	NAME_ORG1	Name 1	Rule - If the field length is less than 40 char, then copy. If the field length is more than 40 char, copy the first part in NAME_ORG1 rest in NAME_ORG2. Use Space as delimiter to separate the entire name
6	Core CRM		SLV41_Customer_Name__c	Customer Name	S4 Hana	BUT000	NAME_ORG2	Name 2	Rule - If the field length is less than 40 char, then copy. If the field length is more than 40 char, copy the first part in NAME_ORG1 rest in NAME_ORG2. Use Space as delimiter to separate the entire name
7	Core CRM				S4 Hana	BUT000	IND_SECTOR	Industry sector	TBD
8	Core CRM				S4 Hana	ADRC	NATION	Address Version	Rule - If there is value in field SLV41_Customer_Name_INT__c then international version will be used. Following international version will be used based on country/region C – Chinese → Simplified Chinese (used for Mandarin). M – Chinese trad. → Traditional Chinese (Mandarin/Taiwan/HK use).
9	Core CRM		For std version - SLV41_Customer_Name__c For international version - SLV41_Customer_Name_INT__c		S4 Hana	ADRC	NAME1	Name	Rule - If the field length is less than 40 char, then copy. If the field length is more than 40 char, copy the first part in NAME_ORG1 rest in NAME_ORG2. Use Space as delimiter to separate the entire name
10	Core CRM		For std version - SLV41_Customer_Name__c For international version - SLV41_Customer_Name_INT__c		S4 Hana	ADRC	NAME2	Name 2	Rule - If the field length is less than 40 char, then copy. If the field length is more than 40 char, copy the first part in NAME_ORG1 rest in NAME_ORG2. Use Space as delimiter to separate the entire name
11	Core CRM		For std version, SLV41_C_O_Name__c For International version SLV41_C_O_Name_INT__c		S4 Hana	ADRC	NAME_CO	c/o	Copy -
12	Core CRM		For std version, SLV7_ACC_Country__c For international version SLV_City_local_language__c		S4 Hana	ADRC	CITY1	City	Copy -
13	Core CRM		SLV20_District__c	District	S4 Hana	ADRC	CITY2	District	Copy -
14	Core CRM		SLV_Address__c	Address	S4 Hana	ADRC	POST_CODE1	Postal Code	Rule -
15	Core CRM				S4 Hana	ADRC	TRANSPZONE	Transportation Zone	Rule -
16	Core CRM		Std version - SLV_Address__c International Version - SLV_Street_local_language__c		S4 Hana	ADRC	STREET	Street	Rule - If the field length is less than 40 char, then copy. If the field length is more than 40 char, copy the first part in STREET rest in STR_SUPPL1 / STR_SUPPL2/3/4. Use Space as delimiter to separate the entire name
17	Core CRM		SLV_Address__c	Address	S4 Hana	ADRC	HOUSE_NUM1	House Number	Rule -
18	Core CRM		SLV_Address__c	Address	S4 Hana	ADRC	HOUSE_NUM2	Supplement	Rule -
19	Core CRM		Std version - SLV_Address__c International Version - SLV_Street_local_language__c		S4 Hana	ADRC	STR_SUPPL1	Street 2	Rule - If the field length is less than 40 char, then copy. If the field length is more than 40 char, copy the first part in STREET rest in STR_SUPPL1 / STR_SUPPL2/3/4. Use Space as delimiter to separate the entire name
20	Core CRM		Std version - SLV_Address__c International Version - SLV_Street_local_language__c		S4 Hana	ADRC	STR_SUPPL2	Street 3	Rule - If the field length is less than 40 char, then copy. If the field length is more than 40 char, copy the first part in STREET rest in STR_SUPPL1 / STR_SUPPL2/3/4. Use Space as delimiter to separate the entire name
21	Core CRM		Std version - SLV_Address__c International Version - SLV_Street_local_language__c		S4 Hana	ADRC	STR_SUPPL3	Street 4	Rule - If the field length is less than 40 char, then copy. If the field length is more than 40 char, copy the first part in STREET rest in STR_SUPPL1 / STR_SUPPL2/3/4. Use Space as delimiter to separate the entire name
22	Core CRM		International Version - SLV_State_local_language__c		S4 Hana	ADRC	LOCATION	Street 5	Copy -
23	Core CRM		SLV7_ACC_Country__c	Country / City	S4 Hana	ADRC	COUNTRY	Country/Region Key	Rule -
24	Core CRM		SLV2_ACC_Language__c	Language	S4 Hana	ADRC	LANGU	Language Key	Mapping -
25	Core CRM		SLV_Address__c	Address	S4 Hana	ADRC	REGION	Region	Rule -
26	Core CRM		SLV41_Customer_Name__c	Customer Name	S4 Hana	ADRC	SORT1	Search Term 1	Rule - Copy first 20 char
27	Core CRM		Phone	Phone	S4 Hana	ADRC	TEL_NUMBER	Telephone	Copy -
28	Core CRM		SLV20_HeadQuarter_Email__c	HeadQuarter Email	S4 Hana	ADR6	SMTP_ADDR	E-Mail Address	Copy -
29	Core CRM				S4 Hana	KNA1	KTOKD	Account group	Default - DEBI
30	Core CRM				S4 Hana	BUT100	PARTNER	Business Partner	Rule - Follow BUT000,
31	Core CRM				S4 Hana	BUT100	RLTYP	BP Role	Default - BUP002 & FLCU01
32	Core CRM		Website	Website	S4 Hana	ADR12	URI_SRCH	URI address	Copy -

Rule #	Source system	Source Table	Source Field	Source Description	Target System	Target Table	Target Field	Target Description	Transformation Logic
33	iCare				S4 Hana	BUT000	PARTNER	Business Partner	Rule - Apply external number range from 1000000 to 99999999, use the running number from 1000000
34	iCare				S4 Hana	BUT000	BU_GROUP	Grouping	Default - BP02
35	iCare		X18D_Account_ID__c	18D Account ID	S4 Hana	BUT000	BPEXT	External BP Number	Copy -
36	iCare		Name	Account Name	S4 Hana	BUT000	BU_SORT1	Search Term 1	Rule - Copy first 20 char
37	iCare		Name	Account Name	S4 Hana	BUT000	NAME_ORG1	Name 1	Rule - If the field length is less than 40 char, then copy. If the field length is more than 40 char, copy the first part in NAME_ORG1 rest in NAME_ORG2. Use Space as delimitor to separate the entire name
38	iCare		Name	Account Name	S4 Hana	BUT000	NAME_ORG2	Name 2	Rule - If the field length is less than 40 char, then copy. If the field length is more than 40 char, copy the first part in NAME_ORG1 rest in NAME_ORG2. Use Space as delimitor to separate the entire name
39	iCare				S4 Hana	BUT000	IND_SECTOR	Industry sector	TBD
40	iCare				S4 Hana	BUT020	PARTNER	Business Partner	Rule - Follow BUT000,
41	iCare				S4 Hana	ADRC	NATION	Address Version	Rule - If there is value in field SLV41_Customer_Name_INT__c then international version will be used. Following international version will be used based on country/region C – Chinese → Simplified Chinese (used for Mandarin). M – Chinese trad. → Traditional Chinese (Mandarin/Taiwan/HK use).
42	iCare		For std version - Name For international version - Account_Name_Local_Language__c		S4 Hana	ADRC	NAME1	Name	Rule -
43	iCare		For std version - Name For international version - Account_Name_Local_Language__c		S4 Hana	ADRC	NAME2	Name 2	Rule - If the field length is less than 40 char, then copy. If the field length is more than 40 char, copy the first part in NAME_ORG1 rest in NAME_ORG2. Use Space as delimitor to separate the entire name
44	iCare				S4 Hana	ADRC	NAME_CO	c/o	Not in use
45	iCare		For std version, BillingAddress For international version Billing_City_Local_Language__c		S4 Hana	ADRC	CITY1	City	Copy -
46	iCare				S4 Hana	ADRC	CITY2	District	Not in use
47	iCare		BillingAddress	Sold-to Address	S4 Hana	ADRC	POST_CODE1	Postal Code	Rule -
48	iCare				S4 Hana	ADRC	TRANSPZONE	Transportation Zone	Rule -
49	iCare		Std version - BillingAddress International Version - Billing_Street_Local_Language__c		S4 Hana	ADRC	STREET	Street	Rule - If the field length is less than 40 char, then copy. If the field length is more than 40 char, copy the first part in STREET rest in STR_SUPPL1. Use Space as delimitor to separate the entire name
50	iCare		BillingAddress	Sold-to Address	S4 Hana	ADRC	HOUSE_NUM1	House Number	Rule -
51	iCare		BillingAddress	Sold-to Address	S4 Hana	ADRC	HOUSE_NUM2	Supplement	Rule -
52	iCare		Std version - BillingAddress International Version - Billing_Street_Local_Language__c		S4 Hana	ADRC	STR_SUPPL1	Street 2	Rule -
53	iCare		Std version - BillingAddress International Version - Billing_Street_Local_Language__c		S4 Hana	ADRC	STR_SUPPL2	Street 3	Rule -
54	iCare		Std version - BillingAddress International Version - Billing_Street_Local_Language__c		S4 Hana	ADRC	STR_SUPPL3	Street 4	Rule -
55	iCare		International Version - Billing_State_Province_Local_Language__c		S4 Hana	ADRC	LOCATION	Street 5	Copy -
56	iCare		BillingAddress	Sold-to Address	S4 Hana	ADRC	COUNTRY	Country/Region Key	Rule -
57	iCare				S4 Hana	ADRC	LANGU	Language Key	Mapping -
58	iCare		BillingAddress		S4 Hana	ADRC	REGION	Region	Rule -
59	iCare		Name	Account Name	S4 Hana	ADRC	SORT1	Search Term 1	Rule - Copy first 20 char
60	iCare		Phone	Phone	S4 Hana	ADRC	TEL_NUMBER	Telephone	Copy -
61	iCare		Email_update__c	General Customer Email	S4 Hana	ADR6	SMTP_ADDR	E-Mail Address	Copy -
62	iCare				S4 Hana	KNA1	KTOKD	Account group	Default -
63	iCare				S4 Hana	BUT100	PARTNER	Business Partner	Rule - Follow BUT000,
64	iCare				S4 Hana	BUT100	RLTYP	BP Role	Default - BUP002 & FLCU01
65	iCare		Website	Website		ADR12	URI_SRCH	URI address	Copy -

Transformation Mapping

Use the exact name and reference this section in the “Transformation rules” above

Mapping Table Name	Mapping Table Description
MAP_REGION_CX	Country/Region Code Mapping Table for SalesForce

Transformation Dependencies

List the steps that need to occur before transformation can commence

Item #	Step Description	Team Responsible
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

The following pre-load validations will be performed by the Project Team.

Completeness

Task	Action
Compare Data Counts	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
Validate Primary Keys and Unique Constraints	Check for duplicate or missing primary key values, i.e., if there is same BP number. Ensure unique constraints are maintained.
Test Referential Integrity	Confirm dependent records exist in related tables

Accuracy

Task	Action
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

The following pre-load validations will be performed by the business.

Completeness

Task	Action
Compare Data Counts	Verify counts between source and target databases. Identify missing or duplicated records.

Accuracy

Task	Action
Check Data Consistency	Compare field values across systems Validate data formats and structures

Load

The load process includes:

1. Execute the automated data load into target system using load tool or product the load file if the load must be done manually
2. 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	Confirm readiness of final approved data sets for each ECC source system WP2 and PF2	Business / Functional Team
2	Validate transformation rules and mappings in Syniti tool	Data Team (L2C-Data)
3	Generate target-ready load files based on S/4HANA condition table format	Data Team (Syniti)
4	Review and approve load files before execution	Business / Functional Team
5	Execute the custom loading program in the S/4HANA system	Data Load Team
6	Monitor load progress and capture load statistics (records loaded, errors, duplicates, etc.)	Data Team (Syniti) / Technical Team
7	Extract loaded data from S/4HANA for post-load validation	Data Team (Syniti)
8	Perform post-load data validation (compare target data with source/approved files) for all loaded pricing condition types	Data Team (L2C-Data)
9	Log and resolve any data load errors or mismatches identified during validation	Data Team (L2C-Data) + Functional Team
10	Obtain business sign-off on successful load and validation	Business Team
11	Archive load logs, error reports, and validation results for audit/compliance	Data Team (L2C-Data) / Data Team (Syniti) / PMO

Load Phase and Dependencies

Identify the phase as to “when” the load for this object will occur. <Pre-Cutover, Cutover, Post Cutover> and list the steps that need to occur before the load can commence

Configuration

List the Configurations required before loading can commence

Item #	Configuration Item
1	BP Grouping
2	Customer Account Group
3	BP Number Range

Conversion Objects

Object #	Preceding Object Conversion Approach
N/A

Error Handling

The table below depicts some possible system errors for this data object during data load. All data load error is to be logged as defect and managed within the Defect Management

Error Type	Error Description	Action Taken
Configuration / Data Transformation	The value XXX for field XXX doesn't exist	Check the mapping/conversion is done properly in the loading file Validate the target value is configured/transported in the target system Reach out to function team to validate the configuration
Configuration	There is mandatory field XXX missing	Validate MDS if the fields are set as mandatory Validate if there is value in the pre-loading file Validate if the configuration for the mandatory fields are done properly
Configuration	The BP grouping is External or Internal Number range	Validate the number range set up if this is External or Internal number range

Post-Load Validation

Project Team

The following post-load validations will be performed by the Project Team.

Completeness

Task	Action
Perform Source-to-Target Comparisons	Validate that migrated data matches source records. Check for discrepancies in numerical values, text fields, and timestamps

Accuracy

Task	Action
Execute Sample Queries and Reports	Run queries to validate business logic. Generate reports to compare expected vs. actual results
Conduct Post-Migration Reconciliation	Generate reports comparing pre- and post-migration data.

Business

The following post-load validations will be performed by the business.

Completeness

Task	Action
Perform Source-to-Target Comparisons	Validate that migrated data matches source records. Check for discrepancies in numerical values, text fields, and timestamps
Conduct Post-Migration Reconciliation	Go through reports comparing pre- and post-migration data.

Accuracy

Task	Action
Perform Manual Testing	Conduct manual spot-checks for additional assurance.

Key Assumptions

• Master Data Standard is up to date as on the date of documenting this conversion approach and data load.
• Prospect is in scope based on data design and any exception requested by business.
• There will be 3 SAP instances, one for ROW, one for China and one for CUI only.
• Prospect will be maintained in 3 SAP instances

See also

Insert links and references to other documents which are relevant when trying to understand this decision and its implications. Other decisions are often impacted, so it's good to list them here with links. Attachments are also possible but dangerous as they are static documents and not updated by their authors.

Change log

Workflow history