Status
Owner	LEW-ext, Chun Ming MADHOK-ext, Jasleen CELEDONIO-ext, Arnold
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 for loading Business Partner – Contact Person Relationships in SAP S/4HANA. In ECC, contact persons are linked to customers using contact-specific tables. In S/4HANA, contact persons are modeled as Business Partners with a relationship type (e.g., BUR001) established between them and the related organization.

Conversion Scope

Customer Contact Person

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

The data from legacy system includes:

An individual is created with mandatory information : Name, Last Name, telephone, email address etc.
An individual is assigned as a contact person OR assigned with partner functions under partner type "AP - Contact Person.
There is no Deletion flag for the contact person (sales level) (KNVK-LOEVM)

The data from legacy system excludes:

Contacts without mandatory contact details : Last Name, Telephone, Email
Contacts not linked to any customers within scope.

List of source systems and approximate number of records

Source	Scope	Source Approx No. of Records	Target System	Target Approx No. of Records
WP2	Customer Contact Person	150,000	S4 Hana ROW	150,000
PF2	Customer Contact Person	150,000	S4 Hana ROW	150,000
WP2	Customer Contact Person	150,000	S4 Hana China	150,000
PF2	Customer Contact Person	150,000	S4 Hana China	150,000
WP2	Customer Contact Person	150,000	S4 Hana CUI	150,000
PF2	Customer Contact Person	150,000	S4 Hana CUI	150,000

Vendor Contact Person Relationship

The data from legacy system includes:

Vendors found in KNVK-LIFNR which pass Relevancy Rules under Data Object (3007-Business Partners - General (Role 000000)) will be assigned with Contacts available from Legacy.

The data from legacy system excludes:

Contacts marked as deleted or obsolete (Inactive in HR) in the legacy system.
Contacts that are not uniquely identifiable, with missing mandatory information such as names or email or contact information.

List of source systems and approximate number of records

Source	Scope	Source Approx No. of Records	Target System	Target Approx No. of Records
WP2	Vendor Contact Person	50,000	S4 Hana ROW	50,000
PF2	Vendor Contact Person	50,000	S4 Hana ROW	50,000
WP2	Vendor Contact Person	50,000	S4 Hana China	50,000
PF2	Vendor Contact Person	50,000	S4 Hana China	50,000

Additional Information

Multi-language Requirement

N/A

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.

Therefore, there will be one SAP instance specifically for CUI related entities. The migration for CUI related entities will be covered by US based data consultant using separate tools.

Special Requirements

A. Different SAP Instance Migration Approach

Due to compliance requirement, there will be one SAP instance for Rest of the World (ROW), one for China and one for CUI. For Contact Person Relationship, the same data will be created in all 3 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
BUT050	PARTNER1	BU_PARTNER	Business Partner	CHAR	10	Mandatory
BUT050	PARTNER2	BU_PARTNER	Business Partner	CHAR	10	Mandatory
BUT050	DATE_TO	BU_DATTO	Valid From	DATS	16	Mandatory
BUT050	DATE_FROM	BU_DATFROM	Valid To	DATS	16	Mandatory
BUT050	RELTYP	BU_RELTYP	Relationship Category	CHAR	12	Mandatory
BUT050	XDFREL	BU_XDFREL	Standard Relationship	CHAR	2	Optional
BUT050	RELKIND	BU_RELKIND	Business partner relationship type	CHAR	8	Optional
BUT051	PAVIP	BU_PAVIP	VIP	CHAR	1	Optional
BUT051	ABTNR	BU_ABTNR	Department	CHAR	4	Optional
BUT051	PAFKT	BU_PAFKT	Function	CHAR	4	Optional
BUT051	PAAUTH	BU_PAAUTH	Partner's Authority	CHAR	1	Optional
BUT051	PAREM	BU_PAREM	Notes for Partner	CHAR	40	Optional
BUT051	FNCTN	BU_FNCTN	Address - Function	CHAR	40	Optional
BUT051	DPRTMNT	BU_DPRTMNT	Address - Department	CHAR	40	Optional
ADCP	DEFLT_COMM	AD_COMM	Communication Method (Key) (Business Address Services)	CHAR	3	Optional
ADCP	ROOMNUMBER	AD_ROOMNUM	Address - Room Number	CHAR	20	Optional
ADCP	FLOOR	AD_FLOOR	Address - Floor Number	CHAR	20	Optional
ADCP	BUILDING	AD_BLDNG_P	Address - Building	CHAR	20	Optional
ADRC	LANGU	SPRAS	LANGUAGE	LANG	2	Optional
ADR2	CONSNUMBER	AD_CONSNUM	Sequence Number	NUMC	3	Mandatory
ADR2	TEL_NUMBER	AD_TLNMBR	TELEPHONE	CHAR	60	Optional
ADR2	TEL_EXTENS	AD_TLXTNS	EXTENSION	CHAR	20	Optional
ADR2	FLGDEFAULT	AD_FLGDFNR	Standard Sender Address in this Communication Type	CHAR	1	Optional
ADR2	FLG_NOUSE	AD_FLNOUSE	Flag: This Communication Number is Not Used	CHAR	1	Optional
ADR2	HOME_FLAG	AD_FLGHOME	Recipient address in this communication type (mail sys.grp)	CHAR	1	Optional
ADR3	CONSNUMBER	AD_CONSNUM	Sequence Number	NUMC	3	Mandatory
ADR3	FAX_NUMBER	AD_FXNMBR1	FAX	CHAR	60	Optional
ADR3	FAX_EXTENS	AD_FXXTNS1	EXTENSION	CHAR	20	Optional
ADR3	FLGDEFAULT	AD_FLGDFNR	Standard Sender Address in this Communication Type	CHAR	1	Optional
ADR3	FLG_NOUSE	AD_FLNOUSE	Flag: This Communication Number is Not Used	CHAR	1	Optional
ADR3	HOME_FLAG	AD_FLGHOME	Recipient address in this communication type (mail sys.grp)	CHAR	1	Optional
ADR6	CONSNUMBER	AD_CONSNUM	Sequence Number	NUMC	3	Mandatory
ADR6	SMTP_ADDR	AD_SMTPADR	E-MAIL	CHAR	482	Optional
ADR6	FLGDEFAULT	AD_FLGDFAD	Flag: this address is the default address	CHAR	1	Optional
ADR6	FLG_NOUSE	AD_FLNOUSE	Flag: This Communication Number is Not Used	CHAR	1	Optional
ADR6	HOME_FLAG	AD_FLGHOME	Recipient address in this communication type (mail sys.grp)	CHAR	1	Optional
ADRC	REMARK	AD_REMARK1	COMMENTS	CHAR	100	Optional
ADRU	COMM_TYPE	AD_COMM	Communtication Method	CHAR	6	Optional
BUT051	CALL_RULEID	BU_RULEID_C	Rule ID / Call	CHAR	25	Optional
BUT051	VISIT_RULEID	BU_RULEID_V	Rule ID / Visit	CHAR	25	Optional
KNVK	MOAB1	BEMOAB1	Contact person's visiting hours: Monday morning from ...	TIMS	8	Optional
KNVK	MOAB2	BEMOAB2	Contact person's visiting hours: Monday afternoon from ...	TIMS	8	Optional
KNVK	MOBI1	BEMOBI1	Contact person's visiting hours: Monday morning until ...	TIMS	8	Optional
KNVK	MOBI2	BEMOBI2	Contact person's visiting hours: Monday afternoon until ...	TIMS	8	Optional
KNVK	DIAB1	BEDIAB1	Contact person's visiting hours: Tuesday morning from...	TIMS	8	Optional
KNVK	DIAB2	BEDIAB2	Contact person's visiting hours: Tuesday afternoon from..	TIMS	8	Optional
KNVK	DIBI1	BEDIBI1	Contact person's visiting hours: Tuesday morning until ...	TIMS	8	Optional
KNVK	DIBI2	BEDIBI2	Contact person's visiting hours: Tuesday afternoon until ...	TIMS	8	Optional
KNVK	MIAB1	BEMIAB1	Contact person's visiting hours: Wednesday morning from...	TIMS	8	Optional
KNVK	MIAB2	BEMIAB2	Contact person's visiting hours: Wednesday afternoon from ..	TIMS	8	Optional
KNVK	MIBI1	BEMIBI1	Contact person's visiting hours: Wednesday morning until ...	TIMS	8	Optional
KNVK	MIBI2	BEMIBI2	Contact person's visiting hours: Wednesday afternoon until..	TIMS	8	Optional
KNVK	DOAB1	BEDOAB1	Contact person's visiting hours: Thursday morning from ....	TIMS	8	Optional
KNVK	DOAB2	BEDOAB2	Contact person's visiting hours: Thursday afternoon from...	TIMS	8	Optional
KNVK	DOBI1	BEDOBI1	Contact person's visiting hours: Thursday morning until ....	TIMS	8	Optional
KNVK	DOBI2	BEDOBI2	Contact person's visiting hours: Thursday afternoon until ..	TIMS	8	Optional
KNVK	FRAB1	BEFRAB1	Contact person's visiting hours: Friday morning from ...	TIMS	8	Optional
KNVK	FRAB2	BEFRAB2	Contact person's visiting hours: Friday afternoon from ...	TIMS	8	Optional
KNVK	FRBI1	BEFRBI1	Contact person's visiting hours: Friday morning until ...	TIMS	8	Optional
KNVK	FRBI2	BEFRBI2	Contact person's visiting hours: Friday afternoon until ...	TIMS	8	Optional
KNVK	SAAB1	BESAAB1	Contact person's visiting hours: Saturday morning from ...	TIMS	8	Optional
KNVK	SAAB2	BESAAB2	Contact person's visiting hours: Saturday afternoon from ...	TIMS	8	Optional
KNVK	SABI1	BESABI1	Contact person's visiting hours: Saturday morning until ...	TIMS	8	Optional
KNVK	SABI2	BESABI2	Contact person's visiting hours: Saturday afternoon until ..	TIMS	8	Optional
KNVK	SOAB1	BESOAB1	Contact person's visiting hours: Sunday morning from ...	TIMS	8	Optional
KNVK	SOAB2	BESOAB2	Contact person's visiting hours: Sunday afternoon from ...	TIMS	8	Optional
KNVK	SOBI1	BESOBI1	Contact person's visiting hours: Sunday morning until ...	TIMS	8	Optional
KNVK	SOBI2	BESOBI2	Contact person's visiting hours: Sunday afternoon until ...	TIMS	8	Optional

Data Cleansing

ID	Error Message/Report Description	Rule	Source System
3010-001	Contact person is not in scope	For contact person which customer is not in 3011 migration scope.	PF2/WP2

Conversion Process

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

1. Extraction
The process begins with extracting metadata and raw data from source systems, such as Syensqo ECC system (i.e., WP2/PF2) 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.

SyWay Project > CNV-3010 Business Partners - Relationship for contact person > image-2025-10-7_18-6-49.png

Data Privacy and Sensitivity

The object contains the exact contact information of a specific individual. This data must be handled with great care.

Extraction

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

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.
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

Extraction Run Sheet

Req #	Requirement Description	Team Responsible
1	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 / LTC Data team
2	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
3	Extraction Execution Plan - Establish execution timelines and batch processing schedules. - Assign responsibilities for extraction monitoring. - Document dependencies on other migration tasks.	Syniti
4	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	Value to be entered/set
SE16N	Contact person for in-scope customers	To select all contact person assigned to in-scope customers	Select all contact person from table KNVK Where KNVK-KUNNR is in object 3011 migration list.

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.

Field Name	Field Description	Rule

Extraction Dependencies

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:

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
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	Transformation Scope Definition - Identify the source and target data structures. - Define business rules for data standardization. - Establish data cleansing requirements to remove inconsistencies.	Data Team, Functional Team
2	Data Mapping and Standardization - Align source fields with target fields. - Ensure unit consistency (e.g., currency, measurement units)	Data Team, Functional Team
3	Business Rule Application - Implement data enrichment/collection if applicable - Apply conditional transformations based on predefined logic/business rules	Data Team, Functional Team
4	Transformation Execution Plan - Define batch processing schedules. - Assign responsibilities for monitoring execution. - Establish error-handling mechanisms	Synithi
5	Configure transformation rules in Syniti Migrate (including calculated fields, formatting rules, etc.)	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	PF2 WP2	KNVK	PARNR	Business Partner	CUI ROW China	BUT050	PARTNER1	Business Partner	Copy 1:1
2	PF2 WP2	KNVK	KUNNR	Business Partner	CUI ROW China	BUT050	PARTNER2	Business Partner	Customer_XREF
3	PF2 WP2	ADCP	DATE_FROM	Valid From	CUI ROW China	BUT050	DATE_TO	Valid From	Copy 1:1
4	PF2 WP2	ADCP	DATE_TO	Valid To	CUI ROW China	BUT050	DATE_FROM	Valid To	Copy 1:1
5	PF2 WP2	N/A	N/A	Relationship Category	CUI ROW China	BUT050	RELTYP	Relationship Category	Default : BUR001
6	PF2 WP2	N/A	N/A	Standard Relationship	CUI ROW China	BUT050	XDFREL	Standard Relationship	Default : Blank
7	PF2 WP2	N/A	N/A	Business partner relationship type	CUI ROW China	BUT050	RELKIND	Business partner relationship type	Default : Blank
8	PF2 WP2	KNVK	PAVIP	VIP	CUI ROW China	BUT051	PAVIP	VIP	Copy 1:1
9	PF2 WP2	KNVK	ABTNR	Department	CUI ROW China	BUT051	ABTNR	Department	Mapping
10	PF2 WP2	KNVK	PAFKT	Function	CUI ROW China	BUT051	PAFKT	Function	Mapping
11	PF2 WP2	KNVK	PARVO	Partner's Authority	CUI ROW China	BUT051	PAAUTH	Partner's Authority	Copy 1:1
12	PF2 WP2	KNVK	PARAU	Notes for Partner	CUI ROW China	BUT051	PAREM	Notes for Partner	Copy 1:1
13	PF2 WP2	DEFLT_COMM	AD_COMM	Communication Method (Key) (Business Address Services)	CUI ROW China	DEFLT_COMM	AD_COMM	Communication Method (Key) (Business Address Services)	Copy 1:1
14	PF2 WP2	ADCP	FUNCTION	Address - Function	CUI ROW China	BUT051	FNCTN	Address - Function	Copy 1:1
15	PF2 WP2	ADCP	DEPARTMENT	Address - Department	CUI ROW China	BUT051	DPRTMNT	Address - Department	Copy 1:1
16	PF2 WP2	ADCP	ROOMNUMBER	Address - Room Number	CUI ROW China	ADCP	ROOMNUMBER	Address - Room Number	Copy 1:1
17	PF2 WP2	ADCP	FLOOR	Address - Floor Number	CUI ROW China	ADCP	FLOOR	Address - Floor Number	Copy 1:1
18	PF2 WP2	ADCP	BUILDING	Address - Building	CUI ROW China	ADCP	BUILDING	Address - Building	Copy 1:1
19	PF2 WP2	ADRC	LANGU	LANGUAGE	CUI ROW China	ADRC	LANGU	LANGUAGE	Copy 1:1
20	PF2 WP2	ADR2	CONSNUMBER	Sequence Number	CUI ROW China	ADR2	CONSNUMBER	Sequence Number	Copy 1:1
21	PF2 WP2	ADR2	TEL_NUMBER	TELEPHONE	CUI ROW China	ADR2	TEL_NUMBER	TELEPHONE	Copy 1:1
22	PF2 WP2	ADR2	TEL_EXTENS	EXTENSION	CUI ROW China	ADR2	TEL_EXTENS	EXTENSION	Copy 1:1
23	PF2 WP2	ADR2	FLGDEFAULT	Standard Sender Address in this Communication Type	CUI ROW China	ADR2	FLGDEFAULT	Standard Sender Address in this Communication Type	Copy 1:1
24	PF2 WP2	ADR2	FLG_NOUSE	Flag: This Communication Number is Not Used	CUI ROW China	ADR2	FLG_NOUSE	Flag: This Communication Number is Not Used	Copy 1:1
25	PF2 WP2	ADR2	HOME_FLAG	Recipient address in this communication type (mail sys.grp)	CUI ROW China	ADR2	HOME_FLAG	Recipient address in this communication type (mail sys.grp)	Copy 1:1
26	PF2 WP2	ADR3	CONSNUMBER	Sequence Number	CUI ROW China	ADR3	CONSNUMBER	Sequence Number	Copy 1:1
27	PF2 WP2	ADR3	FAX_NUMBER	FAX	CUI ROW China	ADR3	FAX_NUMBER	FAX	Copy 1:1
28	PF2 WP2	ADR3	FAX_EXTENS	EXTENSION	CUI ROW China	ADR3	FAX_EXTENS	EXTENSION	Copy 1:1
29	PF2 WP2	ADR3	FLGDEFAULT	Standard Sender Address in this Communication Type	CUI ROW China	ADR3	FLGDEFAULT	Standard Sender Address in this Communication Type	Copy 1:1
30	PF2 WP2	ADR3	FLG_NOUSE	Flag: This Communication Number is Not Used	CUI ROW China	ADR3	FLG_NOUSE	Flag: This Communication Number is Not Used	Copy 1:1
31	PF2 WP2	ADR3	HOME_FLAG	Recipient address in this communication type (mail sys.grp)	CUI ROW China	ADR3	HOME_FLAG	Recipient address in this communication type (mail sys.grp)	Copy 1:1
32	PF2 WP2	ADR6	CONSNUMBER	Sequence Number	CUI ROW China	ADR6	CONSNUMBER	Sequence Number	Copy 1:1
33	PF2 WP2	ADR6	SMTP_ADDR	E-MAIL	CUI ROW China	ADR6	SMTP_ADDR	E-MAIL	Copy 1:1
34	PF2 WP2	ADR6	FLGDEFAULT	Flag: this address is the default address	CUI ROW China	ADR6	FLGDEFAULT	Flag: this address is the default address	Copy 1:1
35	PF2 WP2	ADR6	FLG_NOUSE	Flag: This Communication Number is Not Used	CUI ROW China	ADR6	FLG_NOUSE	Flag: This Communication Number is Not Used	Copy 1:1
36	PF2 WP2	ADR6	HOME_FLAG	Recipient address in this communication type (mail sys.grp)	CUI ROW China	ADR6	HOME_FLAG	Recipient address in this communication type (mail sys.grp)	Copy 1:1
37	PF2 WP2	ADRCT	REMARK	COMMENTS	CUI ROW China	ADRCT	REMARK	COMMENTS	Copy 1:1
38	PF2 WP2	ADRU	COMM_TYPE	Communtication Method	CUI ROW China	ADRU	COMM_TYPE	Communtication Method	Copy 1:1
39	PF2 WP2	N/A	N/A		CUI ROW China	BUT051	CALL_RULEID	Rule ID / Call	Not used for L2C
40	PF2 WP2	KNVK	MOAB1	Contact person's visiting hours: Monday morning from ...	CUI ROW China	BUT051	VISIT_RULEID	Rule ID / Visit	Copy 1:1
41	PF2 WP2	KNVK	MOAB2	Contact person's visiting hours: Monday afternoon from ...	CUI ROW China	BUT051	VISIT_RULEID	Rule ID / Visit	Copy 1:1
42	PF2 WP2	KNVK	MOBI1	Contact person's visiting hours: Monday morning until ...	CUI ROW China	BUT051	VISIT_RULEID	Rule ID / Visit	Copy 1:1
43	PF2 WP2	KNVK	MOBI2	Contact person's visiting hours: Monday afternoon until ...	CUI ROW China	BUT051	VISIT_RULEID	Rule ID / Visit	Copy 1:1
44	PF2 WP2	KNVK	DIAB1	Contact person's visiting hours: Tuesday morning from...	CUI ROW China	BUT051	VISIT_RULEID	Rule ID / Visit	Copy 1:1
45	PF2 WP2	KNVK	DIAB2	Contact person's visiting hours: Tuesday afternoon from..	CUI ROW China	BUT051	VISIT_RULEID	Rule ID / Visit	Copy 1:1
46	PF2 WP2	KNVK	DIBI1	Contact person's visiting hours: Tuesday morning until ...	CUI ROW China	BUT051	VISIT_RULEID	Rule ID / Visit	Copy 1:1
47	PF2 WP2	KNVK	DIBI2	Contact person's visiting hours: Tuesday afternoon until ...	CUI ROW China	BUT051	VISIT_RULEID	Rule ID / Visit	Copy 1:1
48	PF2 WP2	KNVK	MIAB1	Contact person's visiting hours: Wednesday morning from...	CUI ROW China	BUT051	VISIT_RULEID	Rule ID / Visit	Copy 1:1
49	PF2 WP2	KNVK	MIAB2	Contact person's visiting hours: Wednesday afternoon from ..	CUI ROW China	BUT051	VISIT_RULEID	Rule ID / Visit	Copy 1:1
50	PF2 WP2	KNVK	MIBI1	Contact person's visiting hours: Wednesday morning until ...	CUI ROW China	BUT051	VISIT_RULEID	Rule ID / Visit	Copy 1:1
51	PF2 WP2	KNVK	MIBI2	Contact person's visiting hours: Wednesday afternoon until..	CUI ROW China	BUT051	VISIT_RULEID	Rule ID / Visit	Copy 1:1
52	PF2 WP2	KNVK	DOAB1	Contact person's visiting hours: Thursday morning from ....	CUI ROW China	BUT051	VISIT_RULEID	Rule ID / Visit	Copy 1:1
53	PF2 WP2	KNVK	DOAB2	Contact person's visiting hours: Thursday afternoon from...	CUI ROW China	BUT051	VISIT_RULEID	Rule ID / Visit	Copy 1:1
54	PF2 WP2	KNVK	DOBI1	Contact person's visiting hours: Thursday morning until ....	CUI ROW China	BUT051	VISIT_RULEID	Rule ID / Visit	Copy 1:1
55	PF2 WP2	KNVK	DOBI2	Contact person's visiting hours: Thursday afternoon until ..	CUI ROW China	BUT051	VISIT_RULEID	Rule ID / Visit	Copy 1:1
56	PF2 WP2	KNVK	FRAB1	Contact person's visiting hours: Friday morning from ...	CUI ROW China	BUT051	VISIT_RULEID	Rule ID / Visit	Copy 1:1
57	PF2 WP2	KNVK	FRAB2	Contact person's visiting hours: Friday afternoon from ...	CUI ROW China	BUT051	VISIT_RULEID	Rule ID / Visit	Copy 1:1
58	PF2 WP2	KNVK	FRBI1	Contact person's visiting hours: Friday morning until ...	CUI ROW China	BUT051	VISIT_RULEID	Rule ID / Visit	Copy 1:1
59	PF2 WP2	KNVK	FRBI2	Contact person's visiting hours: Friday afternoon until ...	CUI ROW China	BUT051	VISIT_RULEID	Rule ID / Visit	Copy 1:1
60	PF2 WP2	KNVK	SAAB1	Contact person's visiting hours: Saturday morning from ...	CUI ROW China	BUT051	VISIT_RULEID	Rule ID / Visit	Copy 1:1
61	PF2 WP2	KNVK	SAAB2	Contact person's visiting hours: Saturday afternoon from ...	CUI ROW China	BUT051	VISIT_RULEID	Rule ID / Visit	Copy 1:1
62	PF2 WP2	KNVK	SABI1	Contact person's visiting hours: Saturday morning until ...	CUI ROW China	BUT051	VISIT_RULEID	Rule ID / Visit	Copy 1:1
63	PF2 WP2	KNVK	SABI2	Contact person's visiting hours: Saturday afternoon until ..	CUI ROW China	BUT051	VISIT_RULEID	Rule ID / Visit	Copy 1:1
64	PF2 WP2	KNVK	SOAB1	Contact person's visiting hours: Sunday morning from ...	CUI ROW China	BUT051	VISIT_RULEID	Rule ID / Visit	Copy 1:1
65	PF2 WP2	KNVK	SOAB2	Contact person's visiting hours: Sunday afternoon from ...	CUI ROW China	BUT051	VISIT_RULEID	Rule ID / Visit	Copy 1:1
66	PF2 WP2	KNVK	SOBI1	Contact person's visiting hours: Sunday morning until ...	CUI ROW China	BUT051	VISIT_RULEID	Rule ID / Visit	Copy 1:1
67	PF2 WP2	KNVK	SOBI2	Contact person's visiting hours: Sunday afternoon until ...	CUI ROW China	BUT051	VISIT_RULEID	Rule ID / Visit	Copy 1:1

Transformation Rules (S2P Vendor)

Rule #	Source system	Source Table	Source Field	Source Description	Target System	Target Table	Target Field	Target Description	Transformation Logic

Transformation Mapping

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

Mapping Table Name	Mapping Table Description

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.	Synithi
2	Referential Integrity - Ensure dependent records are transformed together or in advance	Synithi
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	Synithi
5	Logging and Error Handling - Maintain detailed logs of transformation activities. - Define error-handling procedures for failed transformations	Synithi

Pre-Load Validation

Project Team

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

Completeness

Task	Action
Validate the record count	Verify that the data extracted from the legacy system is complete and accurate by comparing record counts and contact person against the source system
Validate the mandatory fields	Validate there is value for all the mandatory fields

Accuracy

Task	Action
Validate the transformation	Verify that all transformation rules have been correctly applied and that transformed fields display the expected target values
Validate the extraction	Verify that all copied fields accurately reflect the source system values to ensure the extraction process has correctly transferred the data.

Business

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

Completeness

Task	Action
Validate the record count	Verify that the data extracted from the legacy system is complete and accurate by comparing record counts and contact person against the source system
Validate the mandatory fields	Validate there is value for all the mandatory fields

Accuracy

Task	Action
Validate the transformation	Validate the fields which require transformation have the value after transformation instead of the original field value
Validate the extraction	Verify that all copied fields accurately reflect the source system values to ensure the extraction process has correctly transferred the data.

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 Scope Definition - Identify the target system and database structure. - Define data objects (tables, fields, records) to be loaded. - Establish business rules for data validation.	Data team
2	Load Methodology - Specify the loading tools and technologies (Migration Cockpit, LSMW, custom loading program).	Syniti
3	Data Quality and Validation - Ensure data integrity checks (null values, duplicates, format validation). - Perform pre-load validations to verify completeness. - Define error handling mechanisms for load failures	Syniti
4	Load Execution Plan - Establish execution timelines and batch processing schedules. - Assign responsibilities for monitoring execution. - Document dependencies on other migration tasks	Syniti
5	Logging and Reporting - Maintain detailed logs of loading activities. - Generate summary reports on loaded data volume and quality. - Define escalation procedures for errors	Syniti

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	BUT050-RELTYP Relationship Category is configured and valid in the target system

Conversion Objects

Object #	Preceding Object Conversion Approach
3011	list the exact title of the conversion object of only the immediate predecessor – this will then confirm the DDD (Data Dependency Diagram)

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
1	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
2	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

Post-Load Validation

Project Team

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

Completeness

Task	Action
Validate Record count in the backend	Validate the main tables BUT100 is loaded.
Display Records	Pick up few random BP numbers, and Run the BP Report to validate the BUP001 information can be displayed without any error

Accuracy

Task

Action

Check values in key fields for accuracy

Post-load reports will have the same structure as the load file and some additional columns as required to facilitate the post load validation.

Leverage on tool to create a Post Load report that reports S/4HANA loaded records along with the legacy values side-by-side to allow for 100% check of all these fields in the shortest possible time.

Any mismatch will be reported under the Post Load - Error report.

Business

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

Completeness

Task	Action
Record Count Check	Review the record count report from the Data Team and ensure it is correct by cross-checking with the record count confirmed during Pre-load Business Validations

Accuracy

Task	Action
Spot check	Business should choose some business partners, display the contact person with transaction code "BP" and perform comprehensive check on all loaded details and relationship

Key Assumptions

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

Any additional key assumptions.

Purpose

Conversion Scope

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

Transformation

Transformation Run Sheet

Transformation Mapping

Transformation Dependencies

Pre-Load Validation

Project Team

Completeness

Accuracy

Business

Completeness

Accuracy

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