Status	Approved
Owner	LEW-ext, Chun Ming MADHOK-ext, Jasleen CELEDONIO-ext, Arnold
Stakeholders

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 and vendors 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:

The contact person is created in object 3011.

The data from legacy system excludes:

Contacts without mandatory contact details : Last Name, 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

MDS Link

The data from legacy system includes:

Vendors found in KNVK-LIFNR which pass Relevancy Rules under Data Objects (3007-Business Partners - General (Role 000000)) and (3011 Business Partners - Contact Persons (BUP001)) will be assigned with Contacts available from Legacy.
Contacts KNVK-PARNR listed in the Inclusion DCT table,
Business Partners which are not in legacy that may have been created via DCT under these Data Objects (3007-Business Partners - General (Role 000000)) and (3011 Business Partners - Contact Persons (BUP001) and CNV-3027 Business Partners - Plants / Intercompany Suppliers)).

The data from legacy system excludes:

Contacts marked as deleted or obsolete in the legacy system.
Contacts that are not uniquely identifiable, with missing mandatory information such as names and (email or telephone) information.
Contacts KNVK-PARNR listed in the Exclusion DCT table.

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
DCT	Data will be provided by business manually or via excel upload to DCT	TBD	S4 Hana China	TBD

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

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 To	DATS	16	Mandatory
BUT050	DATE_FROM	BU_DATFROM	Valid From	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	PERSNUMBER	AD_PERSNUM	Person Number	CHAR	10	Mandatory
ADCP	DATE_FROM	AD_DATE_FR	from	DATS	10	Mandatory
ADCP	NATION	AD_NATION	Address Version	CHAR	1	Mandatory
ADCP	DEFLT_COMM	AD_COMM	Communication Method (Key) (Business Address Services)	CHAR	3	Optional
ADCP	ROOMNUMBER	AD_ROOMNUM	Address - Room Number	CHAR	20	Not in used
ADCP	FLOOR	AD_FLOOR	Address - Floor Number	CHAR	20	Not in used
ADCP	BUILDING	AD_BLDNG_P	Address - Building	CHAR	20	Not in used
ADRC	NATION	AD_NATION	Address Version	CHAR	1	Mandatory
ADRC	LANGU	SPRAS	LANGUAGE	LANG	2	Optional
ADR2	PERSNUMBER	AD_PERSNUM	Person Number	CHAR	10	Mandatory
ADR2	DATE_FROM	AD_DATE_FR	from	DATS	10	Mandatory
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	PERSNUMBER	AD_PERSNUM	Person Number	CHAR	10	Mandatory
ADR3	DATE_FROM	AD_DATE_FR	from	DATS	10	Mandatory
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	PERSNUMBER	AD_PERSNUM	Person Number	CHAR	10	Mandatory
ADR6	DATE_FROM	AD_DATE_FR	from	DATS	10	Mandatory
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
ADRCT	REMARK	AD_REMARK1	COMMENTS	CHAR	100	Optional
ADRU	PERSNUMBER	AD_PERSNUM	Person Number	CHAR	10	Mandatory
ADRU	COMM_TYPE	AD_COMM	Communtication Method	CHAR	6	Optional
ADRU	COMM_USAGE	AD_CUSAGE	Use	CHAR	10	Mandatory
ADRU	VALID_TO	AD_VALTO	Valid To	CHAR	14	Mandatory
BUT051	CALL_RULEID	BU_RULEID_C	Rule ID / Call	CHAR	25	Optional
BUT051	VISIT_RULEID	BU_RULEID_V	Rule ID / Visit	CHAR	25	Optional

Data Cleansing

ID	Criticality	Error Message/Report Description	Rule	Output	Source System
3010-001		Department not mapped to S4	ABTNR not in S4 config table TB910		PF2/WP2
3010-002		Function not mapped to S4	PAFKT not in S4 config table TB912		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.

The high-level process, where there is no source data, is represented by the diagram below:

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/S2P) 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

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.
SE16N	Contact person for in-scope vendors	To select all contact person assigned to in-scope vendors	Select all contact person from table KNVK Where KNVK-LIFNR is in object 3011 migration list.

Data Collection Template (DCT for S2P Vendor)

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

Field Name	Field Description	Rule
PARTNER1	Business Partner	Legacy or DCT Vendor Number
PARTNER2	Business Partner	Legacy or DCT Contact Number
DATE_TO	Valid From	Must be a valid date
DATE_FROM	Valid To	Must be a valid date
RELTYP	Relationship Category	Default : BUR001
RELKIND	Business partner relationship type	Must be a valid Relationship Type
PAVIP	VIP	Must not exceed 1 char
ABTNR	Department	Must be a valid Department
PAFKT	Function	Must be a valid Function
PAAUTH	Partner's Authority	Must not exceed 1 char
PAREM	Notes for Partner	Must not exceed 40 chars
FNCTN	Address - Function	Must not exceed 40 chars
DPRTMNT	Address - Department	Must not exceed 40 chars
LANGU	LANGUAGE	Must be a valid language in T002
TEL_NUMBER	TELEPHONE	Must be numeric
TEL_EXTENS	EXTENSION	Must be numeric
FLGDEFAULT	Standard Sender Address in this Communication Type	X or blank
FLG_NOUSE	Flag: This Communication Number is Not Used	X or blank
HOME_FLAG	Recipient address in this communication type (mail sys.grp)	X or blank
FAX_NUMBER	FAX	Must be numeric
FAX_EXTENS	EXTENSION	Must be numeric
FLGDEFAULT	Standard Sender Address in this Communication Type	X or blank
FLG_NOUSE	Flag: This Communication Number is Not Used	X or blank
HOME_FLAG	Recipient address in this communication type (mail sys.grp)	X or blank
SMTP_ADDR	E-MAIL	Must be a valid email
FLGDEFAULT	Flag: this address is the default address	X or blank
FLG_NOUSE	Flag: This Communication Number is Not Used	X or blank
HOME_FLAG	Recipient address in this communication type (mail sys.grp)	X or blank
REMARK	COMMENTS	Must not exceed 50 chars
COMM_TYPE	Communtication Method	Must be a communication type

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
7	For S2P Vendors Obtain DCT Sign-off from Business	S2P Data Team

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	Syniti
5	Configure transformation rules in Syniti Migrate (including calculated fields, formatting rules, etc.)	Data Team (Syniti), Data Team (L2C/S2P)
6	Review transformation logic and mappings with Business for confirmation	Business Team + Functional Team (L2C/S2P)
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/S2P), Functional Team (L2C/S2P)
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/S2P)
11	Finalize and approve transformed data as Target Ready Load File	Business + Functional (L2C/S2P) + Data Team (L2C/S2P)
12	Handover final file to Load Team or trigger the load via Syniti Load Workbench	Data Team (Syniti)

Transformation Rules (L2C Customer)

Rule #	Source system	Source Table	Source Field	Source Description	Target System	Target Table	Target Field	Target Description	Transformation Logic
1	PF2 WP2	KNVK	KUNNR	Business Partner	CUI ROW China	BUT050	PARTNER1	Business Partner	Customer_XREF
2	PF2 WP2	KNVK	PARNR	Business Partner	CUI ROW China	BUT050	PARTNER2	Business Partner	Contact_XREF
3	PF2 WP2	ADCP	DATE_FROM	Valid From	CUI ROW China	BUT050	DATE_FROM	Valid From	Copy 1:1
4	PF2 WP2	ADCP	DATE_TO	Valid To	CUI ROW China	BUT050	DATE_TO	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	Mapping xtRELKIND
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 xtABTNR
10	PF2 WP2	KNVK	PAFKT	Function	CUI ROW China	BUT051	PAFKT	Function	Mapping xtABTNR
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	Not in used
17	PF2 WP2	ADCP	FLOOR	Address - Floor Number	CUI ROW China	ADCP	FLOOR	Address - Floor Number	Not in used
18	PF2 WP2	ADCP	BUILDING	Address - Building	CUI ROW China	ADCP	BUILDING	Address - Building	Not in used
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	System
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	System
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	System
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/S2P
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
68	PF2 WP2	ADCP	PERSNUMBER	Person Number	CUI ROW China	ADCP	PERSNUMBER	Person Number	System
69	PF2 WP2	ADR2	PERSNUMBER	Person Number	CUI ROW China	ADR2	PERSNUMBER	Person Number	System
70	PF2 WP2	ADR3	PERSNUMBER	Person Number	CUI ROW China	ADR3	PERSNUMBER	Person Number	System
71	PF2 WP2	ADR6	PERSNUMBER	Person Number	CUI ROW China	ADR6	PERSNUMBER	Person Number	System
72	PF2 WP2	ADRU	PERSNUMBER	Person Number	CUI ROW China	ADRU	PERSNUMBER	Person Number	System
73	PF2 WP2	ADCP	DATE_FROM	Valid from	CUI ROW China	ADCP	DATE_FROM	Valid from	System
74	PF2 WP2	ADR2	DATE_FROM	Valid from	CUI ROW China	ADR2	DATE_FROM	Valid from	System
75	PF2 WP2	ADR3	DATE_FROM	Valid from	CUI ROW China	ADR3	DATE_FROM	Valid from	System
76	PF2 WP2	ADR6	DATE_FROM	Valid from	CUI ROW China	ADR6	DATE_FROM	Valid from	System
77	PF2 WP2	ADRC	DATE_FROM	Valid from	CUI ROW China	ADRC	DATE_FROM	Valid from	System
78	PF2 WP2	ADCP	NATION	Address Version	CUI ROW China	ADCP	NATION	Address Version	Copy 1:1
79	PF2 WP2	ADRC	NATION	Address Version	CUI ROW China	ADRC	NATION	Address Version	Copy 1:1
80	PF2 WP2	ADRU	COMM_USAGE	Use	CUI ROW China	ADRU	COMM_USAGE	Use	System
81	PF2 WP2	ADRU	VALID_TO	Valid To	CUI ROW China	ADRU	VALID_TO	Valid To	System

Transformation Rules (S2P Vendor)

From legacy ECC source

Rule #	Source system	Source Table	Source Field	Source Description	Target System	Target Table	Target Field	Target Description	Transformation Logic
1	PF2 WP2	KNVK	LIFNR	Business Partner	CUI ROW China	BUT050	PARTNER1	Business Partner	Vendor_XREF
2	PF2 WP2	KNVK	PARNR	Business Partner	CUI ROW China	BUT050	PARTNER2	Business Partner	Contact_XREF
3	PF2 WP2	ADCP	DATE_FROM	Valid From	CUI ROW China	BUT050	DATE_FROM	Valid From	Copy
4	PF2 WP2	ADCP	DATE_TO	Valid To	CUI ROW China	BUT050	DATE_TO	Valid To	Copy
5	PF2 WP2	N/A	N/A	N/A	CUI ROW China	BUT050	RELTYP	Relationship Category	Default : BUR001
6	PF2 WP2	N/A	N/A	N/A	CUI ROW China	BUT050	RELKIND	Business partner relationship type	Mapping
7	PF2 WP2	KNVK	PAVIP	VIP	CUI ROW China	BUT051	PAVIP	VIP	Copy
8	PF2 WP2	KNVK	ABTNR	Department	CUI ROW China	BUT051	ABTNR	Department	Mapping
9	PF2 WP2	KNVK	PAFKT	Function	CUI ROW China	BUT051	PAFKT	Function	Mapping
10	PF2 WP2	KNVK	PARVO	Partner's Authority	CUI ROW China	BUT051	PAAUTH	Partner's Authority	Copy
11	PF2 WP2	KNVK	PARAU	Notes for Partner	CUI ROW China	BUT051	PAREM	Notes for Partner	Copy
12	PF2 WP2	ADCP	FUNCTION	Address - Function	CUI ROW China	BUT051	FNCTN	Address - Function	Copy
13	PF2 WP2	ADCP	DEPARTMENT	Address - Department	CUI ROW China	BUT051	DPRTMNT	Address - Department	Copy
14	PF2 WP2	ADRC	LANGU	LANGUAGE	CUI ROW China	ADRC	LANGU	LANGUAGE	Copy
15	PF2 WP2	ADR2	TEL_NUMBER	TELEPHONE	CUI ROW China	ADR2	TEL_NUMBER	TELEPHONE	Copy
16	PF2 WP2	ADR2	TEL_EXTENS	EXTENSION	CUI ROW China	ADR2	TEL_EXTENS	EXTENSION	Copy
17	PF2 WP2	ADR2	FLGDEFAULT	Standard Sender Address in this Communication Type	CUI ROW China	ADR2	FLGDEFAULT	Standard Sender Address in this Communication Type	Copy
18	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
19	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
20	PF2 WP2	ADR3	FAX_NUMBER	FAX	CUI ROW China	ADR3	FAX_NUMBER	FAX	Copy
21	PF2 WP2	ADR3	FAX_EXTENS	EXTENSION	CUI ROW China	ADR3	FAX_EXTENS	EXTENSION	Copy
22	PF2 WP2	ADR3	FLGDEFAULT	Standard Sender Address in this Communication Type	CUI ROW China	ADR3	FLGDEFAULT	Standard Sender Address in this Communication Type	Copy
23	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
24	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
25	PF2 WP2	KNVK	NAME1	E-MAIL	CUI ROW China	ADR6	SMTP_ADDR	E-MAIL	Rule: Copy if valid email, else ADR6-SMTP_ADDR
26	PF2 WP2	ADR6	FLGDEFAULT	Flag: this address is the default address	CUI ROW China	ADR6	FLGDEFAULT	Flag: this address is the default address	Copy
27	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
28	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
29	PF2 WP2	ADRCT	REMARK	COMMENTS	CUI ROW China	ADRCT	REMARK	COMMENTS	Copy
30	PF2 WP2	ADRU	COMM_TYPE	Communtication Method	CUI ROW China	ADRU	COMM_TYPE	Communtication Method	Copy
31	PF2 WP2	ADR2	CONSNUMBER	Sequence Number	CUI ROW China	ADR2	CONSNUMBER	Sequence Number	Internal
32	PF2 WP2	ADR3	CONSNUMBER	Sequence Number	CUI ROW China	ADR3	CONSNUMBER	Sequence Number	Internal
33	PF2 WP2	ADR6	CONSNUMBER	Sequence Number	CUI ROW China	ADR6	CONSNUMBER	Sequence Number	Internal

From DCT source

Rule #	Source system	Source Table	Source Field	Source Description	Target System	Target Table	Target Field	Target Description	Transformation Logic
1	DCT	BPRelationship_DCT	PARTNER1	Business Partner	CUI ROW China	BUT050	PARTNER1	Business Partner	Vendor_XREF
2	DCT	BPRelationship_DCT	PARTNER2	Business Partner	CUI ROW China	BUT050	PARTNER2	Business Partner	Contact_XREF
3	DCT	BPRelationship_DCT	DATE_FROM	Valid From	CUI ROW China	BUT050	DATE_FROM	Valid From	Copy
4	DCT	BPRelationship_DCT	DATE_TO	Valid To	CUI ROW China	BUT050	DATE_TO	Valid To	Copy
5	DCT	BPRelationship_DCT	RELTYP	Relationship Category	CUI ROW China	BUT050	RELTYP	Relationship Category	Default : BUR001
6	DCT	BPRelationship_DCT	RELKIND	Business partner relationship type	CUI ROW China	BUT050	RELKIND	Business partner relationship type	Copy
7	DCT	BPRelationship_DCT	PAVIP	VIP	CUI ROW China	BUT051	PAVIP	VIP	Copy
8	DCT	BPRelationship_DCT	ABTNR	Department	CUI ROW China	BUT051	ABTNR	Department	Copy
9	DCT	BPRelationship_DCT	PAFKT	Function	CUI ROW China	BUT051	PAFKT	Function	Copy
10	DCT	BPRelationship_DCT	PAAUTH	Partner's Authority	CUI ROW China	BUT051	PAAUTH	Partner's Authority	Copy
11	DCT	BPRelationship_DCT	PAREM	Notes for Partner	CUI ROW China	BUT051	PAREM	Notes for Partner	Copy
12	DCT	BPRelationship_DCT	FNCTN	Address - Function	CUI ROW China	BUT051	FNCTN	Address - Function	Copy
13	DCT	BPRelationship_DCT	DPRTMNT	Address - Department	CUI ROW China	BUT051	DPRTMNT	Address - Department	Copy
14	DCT	BPRelationship_DCT	LANGU	LANGUAGE	CUI ROW China	ADRC	LANGU	LANGUAGE	Copy
15	DCT	BPRelationship_DCT	TEL_NUMBER	TELEPHONE	CUI ROW China	ADR2	TEL_NUMBER	TELEPHONE	Copy
16	DCT	BPRelationship_DCT	TEL_EXTENS	EXTENSION	CUI ROW China	ADR2	TEL_EXTENS	EXTENSION	Copy
17	DCT	BPRelationship_DCT	FLGDEFAULT	Standard Sender Address in this Communication Type	CUI ROW China	ADR2	FLGDEFAULT	Standard Sender Address in this Communication Type	Copy
18	DCT	BPRelationship_DCT	FLG_NOUSE	Flag: This Communication Number is Not Used	CUI ROW China	ADR2	FLG_NOUSE	Flag: This Communication Number is Not Used	Copy
19	DCT	BPRelationship_DCT	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
20	DCT	BPRelationship_DCT	FAX_NUMBER	FAX	CUI ROW China	ADR3	FAX_NUMBER	FAX	Copy
21	DCT	BPRelationship_DCT	FAX_EXTENS	EXTENSION	CUI ROW China	ADR3	FAX_EXTENS	EXTENSION	Copy
22	DCT	BPRelationship_DCT	FLGDEFAULT	Standard Sender Address in this Communication Type	CUI ROW China	ADR3	FLGDEFAULT	Standard Sender Address in this Communication Type	Copy
23	DCT	BPRelationship_DCT	FLG_NOUSE	Flag: This Communication Number is Not Used	CUI ROW China	ADR3	FLG_NOUSE	Flag: This Communication Number is Not Used	Copy
24	DCT	BPRelationship_DCT	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
25	DCT	BPRelationship_DCT	SMTP_ADDR	E-MAIL	CUI ROW China	ADR6	SMTP_ADDR	E-MAIL	Copy
26	DCT	BPRelationship_DCT	FLGDEFAULT	Flag: this address is the default address	CUI ROW China	ADR6	FLGDEFAULT	Flag: this address is the default address	Copy
27	DCT	BPRelationship_DCT	FLG_NOUSE	Flag: This Communication Number is Not Used	CUI ROW China	ADR6	FLG_NOUSE	Flag: This Communication Number is Not Used	Copy
28	DCT	BPRelationship_DCT	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
29	DCT	BPRelationship_DCT	REMARK	COMMENTS	CUI ROW China	ADRCT	REMARK	COMMENTS	Copy
30	DCT	BPRelationship_DCT	COMM_TYPE	Communtication Method	CUI ROW China	ADRU	COMM_TYPE	Communtication Method	Copy
31	DCT	BPRelationship_DCT	CONSNUMBER	Sequence Number	CUI ROW China	ADR2	CONSNUMBER	Sequence Number	Internal
32	DCT	BPRelationship_DCT	CONSNUMBER	Sequence Number	CUI ROW China	ADR3	CONSNUMBER	Sequence Number	Internal
33	DCT	BPRelationship_DCT	CONSNUMBER	Sequence Number	CUI ROW China	ADR6	CONSNUMBER	Sequence Number	Internal

Transformation Mapping

Transformation Mapping Document Link

Mapping Table Name	Mapping Table Description
xtABTNR	Department Mapping
xtPAFKT	Function Mapping
xtRELKIND	Business partner relationship type

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 (L2C/S2P)
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
6	The following data objects should be already loaded prior to transformation. 3007-Business Partners - General (Role 000000)) 3011 Business Partners - Contact Persons (BUP001)	Syniti

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 or DCT 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 or DCT 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 produce 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

Configuration

Item #	Configuration Item
1	BUT050-RELTYP Relationship Category is configured and valid in the target system
2	TB910-ABTNR Department is configured in the target system - MM Config Values
3	TB912-PAFKT Function is configured in the target system - MM Config Values

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

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.

Change log

Version	Published	Changed By	Comment
CURRENT (v. 49)	Feb 23, 2026 13:24	LEW-ext, Chun Ming	Remove CUI portion
v. 56	Feb 11, 2026 10:17	CELEDONIO-ext, Arnold	Remouve CUI references for Vendor
v. 55	Dec 19, 2025 09:49	CELEDONIO-ext, Arnold
v. 54	Dec 17, 2025 15:35	CELEDONIO-ext, Arnold
v. 53	Dec 17, 2025 14:51	CELEDONIO-ext, Arnold
v. 52	Dec 17, 2025 12:28	CELEDONIO-ext, Arnold
v. 51	Dec 12, 2025 04:29	LEW-ext, Chun Ming
v. 50	Dec 11, 2025 13:49	LEW-ext, Chun Ming
v. 49	Dec 11, 2025 09:17	CELEDONIO-ext, Arnold
v. 48	Dec 10, 2025 12:42	CELEDONIO-ext, Arnold

Go to Page History

Workflow history

Title	Last Updated By	Updated	Status
There are no pages at the moment.

Mar 30, 2026	Actor	Type	Activity	Version
Approved	NIKULSINS-ext, Vladimirs	State	changed state to Approved at 12:52 pm	v57
Revision under Review	NIKULSINS-ext, Vladimirs	State	gave Minor change approval at 12:52 pm CUI is removed - minor/no change to the build
	LEW-ext, Chun Ming	State	changed state to Revision under Review at 10:17 am	v57
Mar 18, 2026
Revision in Progress	WENNINGER-ext, Sascha	State	changed state to Revision in Progress at 5:49 pm	v57
From Feb 11, 2026 to Feb 23, 2026
Edited following Approval	LEW-ext, Chun Ming and CELEDONIO-ext, Arnold	Edit	multiple updates from LEW-ext, Chun Ming and CELEDONIO-ext, Arnold

Workflow history

Space shortcuts

Page tree

CNV-3010 Business Partners - Relationship for contact person

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 for S2P Vendor)

Extraction Dependencies

Transformation

Transformation Run Sheet

Transformation Rules (S2P Vendor)

From legacy ECC source

From DCT source

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