You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 56 Next »

Status

  Revision in Progress

Owner

LEW-ext, Chun MingMADHOK-ext, Jasleen CELEDONIO-ext, Arnold 

Stakeholders

Purpose

The purpose of this document is to define the conversion approach for assigning the Business Partner role BUP001 (Contact) in SAP S/4HANA. In S/4HANA, Business Partner roles define the context in which a BP can be used. The BUP001 role is essential for identifying individuals as contact persons within customer and vendor relationships.


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:

  1. An individual is created with minimal information such as Name, Last Name, email address and assigned as a contact person for a customer. 
  2. An individual is assigned in the customer master, partner functions in scope under partner type (TPAR-NPART) "AP - Contact Person". For Example, partner function CP - Contact Person (PF2), Q1 - 

    QM Cert. Recipient 1 (PF2), Z6 - Z6 SDS Receiver - Sales (WP2), ZY - Z6 SDS Receiver - Sales (WP2) and etc. 

  3. The contact person created for the Customers object 3007 in scope.

The data from legacy system excludes:

  1. Contacts marked as deleted or obsolete in the legacy system.
  2. Contacts not linked to any customers within scope.


List of source systems and approximate number of records
SourceScope

Source Approx No. of Records

Target SystemTarget Approx

No. of Records

WP2Customer Contact Person150,000S4 Hana ROW150,000
PF2Customer Contact Person150,000S4 Hana ROW150,000
WP2Customer Contact Person150,000S4 Hana China150,000
PF2Customer Contact Person150,000S4 Hana China150,000
WP2Customer Contact Person150,000S4 Hana CUI150,000
PF2Customer Contact Person150,000S4 Hana CUI150,000

Vendor Contact Person

The data from legacy system includes:

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

  1.  Contacts marked as deleted or obsolete (Inactive in HR) in the legacy system.
  2. 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

SourceScope

Source Approx No. of Records

Target SystemTarget Approx

No. of Records

WP2Vendor Contact Person50,000S4 Hana ROW50,000
PF2Vendor Contact Person50,000S4 Hana ROW50,000
WP2Vendor Contact Person50,000S4 Hana China50,000
PF2Vendor Contact Person50,000S4 Hana China50,000
DCTData will be provided by business manually or via excel upload to DCTTBDS4 Hana ChinaTBD


Additional Information

Multi-language Requirement

The customer and vendor contact person may contain international address. Therefore, the conversion will also need to support the multi-language address.  Below languages (International versions) are supported. 

CSimplified Chinese
RCyrillic
KKanji (Japanese)
AArabic
3Korean
TThai
HHangul

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

Customer Contact Person

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 BP general data, the same data will be created in all 3 SAP instances.

Target Design

MDS Link:

The technical design of the target for this conversion approach.


TableFieldData ElementField DescriptionData TypeLengthRequirement
BUT000PARTNERBU_PARTNERBUSINESS PARTNERCHAR20System
BUT000BU_GROUPBU_GROUPGROUPINGCHAR8Mandatory
BUT000TITLEAD_TITLETITLECHAR8Optional
BUT000NAME_FIRSTBU_NAMEP_FFirst NameCHAR80Optional
BUT000NAME_LASTBU_NAMEP_LLast NameCHAR80Mandatory
BUT000NICKNAMEBU_NICKNAMKNOWN ASCHAR80Not Used
BUT000NAME_LAST2BU_BIRTHNMNAME AT BIRTHCHAR80Not Used
BUT000NAMEMIDDLEBU_NAMEMIDMIDDLE NAMECHAR80Not Used
BUT000NAME_LST2BU_NAMEPL2SECOND FAMILY NAMECHAR80Not Used
BUT000PREFIX1AD_PREFIXNAME AFFIX 1/2CHAR8Not Used
BUT000PREFIX2AD_PREFIX2NAME AFFIX 2/2CHAR8Not Used
BUT000TITLE_ACA1AD_TITLE1ACADEMIC TITLE 1/2CHAR8Not Used
BUT000TITLE_ACA2AD_TITLE2ACADEMIC TITLE 2/2CHAR8Not Used
BUT000TITLE_ROYLAD_TITLESNAME SUPPLEMENTCHAR8Not Used
BUT000INITIALSAD_INITSINITIALSCHAR20Not Used
BUT000NAME1_TEXTBU_NAME1TXFULL NAMECHAR160Not Used
BUT000NAMCOUNTRYAD_NAMCTRYCOUNTRY FOR FORMATCHAR6Not Used
BUT000NAMEFORMATAD_FORMATSPECIAL FORMATCHAR4Not Used
BUT000LANGU_CORRBU_LANGU_CORRCORRESPONDENCE LANGUAGELANG2Mandatory
BUS000FLDSLANGUBU_LANGUSTRLANGUAGECHAR4Optional
BUT000TITLE_LETBU_TITLE_LETSALUTATIONCHAR100Optional
BUT000BU_SORT1BU_SORT1SEARCH TERM 1CHAR40Optional
BUT000BU_SORT2BU_SORT2SEARCH TERM 2CHAR40Optional
ADRCADDRNUMBERAD_ADDRNUMAddress NumberCHAR10Mandatory
ADRCNATIONAD_NATIONVersion ID for International AddressesCHAR1Optional
ADRCBUILDINGAD_BLDNGBUILDING CODECHAR40Not Used
ADRCROOMNUMBERAD_ROOMNUMROOMCHAR20Not Used
ADRCFLOORAD_FLOORFLOORCHAR20Not Used
ADRCNAME_COAD_NAME_COC/OCHAR80Optional
ADRCSTR_SUPPL1AD_STRSPP1STREET 2CHAR80Optional
ADRCSTR_SUPPL2AD_STRSPP2STREET 3CHAR80Optional
ADRCSTREETAD_STREETSTREET NAMECHAR120Optional
ADRCHOUSE_NUM1AD_HSNM1HOUSE NUMBERCHAR20Optional
ADRCHOUSE_NUM2AD_HSNM2SUPPLCHAR20Optional
ADRCSTR_SUPPL3AD_STRSPP3STREET 4CHAR80Optional
ADRCLOCATIONAD_LCTNSTREET 5CHAR80Optional
ADRCCITY2AD_CITY2DISTRICTCHAR80Optional
ADRCHOME_CITYAD_CITY3DIFFERENT CITYCHAR80Optional
ADRCPOST_CODE1AD_PSTCD1POSTAL CODECHAR20Optional
ADRCCITY1AD_CITY1CITYCHAR80Optional
ADRCCOUNTRYLAND1COUNTRYCHAR6Mandatory
ADRCREGIONREGIOREGIONCHAR6Optional
ADRCTIME_ZONEAD_TZONETIME ZONECHAR12System
ADRCTAXJURCODEAD_TXJCDTAX JURISDICTIONCHAR30Optional
ADRCTRANSPZONELZONETRANSPORTATION ZONECHAR20Optional
ADRCREGIOGROUPREGIOGROUPSTRUCTURE GROUPCHAR16Not Used
ADRCDONT_USE_SAD_NO_USESUNDELIVERABLECHAR8Not Used
ADRCPO_BOXAD_POBXPO BOXCHAR20Optional
ADRCPO_BOX_NUMAD_POBXNUMPO BOX W/O NO.CHAR2Not Used
ADRCDELI_SERV_TYPEAD_DELIVERY_SERVICE_TYPEDELIVERY SERVICECHAR8Not Used
ADRCDELI_SERV_NUMBERAD_DELIVERY_SERVICE_NUMBERDELIVERY SERVICE NUMBERCHAR20Not Used
ADRCPO_BOX_LOBBYAD_PO_BOX_LBYPO BOX LOBBYCHAR80Not Used
ADRCPOST_CODE2AD_PSTCD2POSTAL CODECHAR20Optional
ADRCPO_BOX_LOCAD_POBXLOCOTHER CITYCHAR80Not Used
ADRCPO_BOX_CTYAD_POBXCTYOTHER COUNTRYCHAR6Not Used
ADRCPO_BOX_REGAD_POBXREGOTHER REGIONCHAR6Not Used
ADRCPOST_CODE3AD_PSTCD3COMPANY POSTAL CODECHAR20Not Used
ADRCLANGUSPRASLANGUAGELANG2Optional
ADR2ADDRNUMBERAD_ADDRNUMAddress NumberCHAR10Mandatory
ADR2CONSNUMBERAD_CONSNUMSequence NumberNUMC3Mandatory
ADR2FLGDEFAULTAD_FLGDFNRStandard Sender Address in this Communication TypeCHAR1System
ADR2FLG_NOUSEAD_FLNOUSEFlag: This Communication Number is Not UsedCHAR1Optional
ADR2HOME_FLAGAD_FLGHOMERecipient address in this communication type (mail sys.grp)CHAR1Optional
ADR2TEL_NUMBERAD_TLNMBRTELEPHONECHAR60Mandatory
ADR2TEL_EXTENSAD_TLXTNSEXTENSIONCHAR20Mandatory
ADR3ADDRNUMBERAD_ADDRNUMAddress NumberCHAR10Mandatory
ADR3CONSNUMBERAD_CONSNUMSequence NumberNUMC3Mandatory
ADR3FLGDEFAULTAD_FLGDFNRStandard Sender Address in this Communication TypeCHAR1FLGDEFAULT
ADR3FLG_NOUSEAD_FLNOUSEFlag: This Communication Number is Not UsedCHAR1Optional
ADR3HOME_FLAGAD_FLGHOMERecipient address in this communication type (mail sys.grp)CHAR1Optional
ADR3FAX_NUMBERAD_FXNMBR1FAXCHAR60Optional
ADR3FAX_EXTENSAD_FXXTNS1EXTENSIONCHAR20Optional
ADR6ADDRNUMBERAD_ADDRNUMAddress NumberCHAR10Mandatory
ADR6CONSNUMBERAD_CONSNUMSequence NumberNUMC3Mandatory
ADR6FLGDEFAULTAD_FLGDFADFlag: this address is the default addressCHAR1FLGDEFAULT
ADR6FLG_NOUSEAD_FLNOUSEFlag: This Communication Number is Not UsedCHAR1Optional
ADR6HOME_FLAGAD_FLGHOMERecipient address in this communication type (mail sys.grp)CHAR1Optional
ADR6SMTP_ADDRAD_SMTPADRE-MAILCHAR482Mandatory
ADRCTREMARKAD_REMARK1COMMENTSCHAR100Optional
BUS000FLDSADEXTBU_ADEXTEXTERNAL ADDRESS NO.CHAR40Not Used
BUS000FLDSADDR_VALID_FROMBU_ADDR_VALID_FROM_STRADDRESS VALID FROMCHAR20System
ADRUCOMM_TYPEAD_COMM

Communication Method (Key) (Business Address Services)

CHAR6Mandatory
ADRUCOMM_USAGEAD_CUSAGE

Communication Usage: Key Field

CHAR20Mandatory
ADRUVALID_FROMAD_VALFROM

Communication Data: Valid From (YYYYMMDDHHMMSS)

CHAR28Mandatory
ADRUVALID_TOAD_VALTO

Communication Data: Valid To (YYYYMMDDHHMMSS)

CHAR28Mandatory


Data Cleansing (Customer)


IDCriticalityError Message/Report DescriptionRuleOutputSource System
3011-001
Corresponding customer master is not in scope

For contact person which customer is not in migration scope. 


PF2/WP2
3011-002
Telephone number contains non-numeric characters

If any non-numeric characters maintained in the telephone number (ADR2-TEL_NUMBER, ADR2-TEL_EXTENS).


PF2/WP2
3011-003
Fax number contains non-numeric characters

If any non-numeric characters maintained in the fax number (ADR3-FAX_NUMBER, ADR3-TEL_EXTENS).


PF2/WP2
3011-004
Invalid email addressIf the email address is not in the patter of XXXX@XXXXX.XX (ADR6-SMTP_ADDR)
PF2/WP2
3011-005
Missing last nameIf the last name is blank (KNVK-NAME1)
PF2/WP2
3011-006
Missing communication languageIf the communication language (KNVK-PARLA) is blank.
PF2/WP2
3011-007
Missing countryIf the country is blank (ADRC-COUNTRY).
PF2/WP2
3011-008
Missing email addressIf the email address (ADR6-SMTP_ADDR) is blank
PF2/WP2
3011-009
Telephone Extension maintained without Telephone numberIf the Telephone number (ADR2-TEL_NUMBER) is blank and Telephone Extension (ADR2-TEL_EXTENS) is not blank.
PF2/WP2
3011-010
Fax Extension maintained without Fax numberIf the Fax number (ADR3-FAX_NUMBER) is blank and Fax Extension (ADR3-FAX_EXTENS) is not blank.
PF2/WP2













Data Cleansing (Vendor)


IDCriticalityError Message/Report DescriptionRuleOutputSource System
3011-001
Corresponding vendor master is not in scope

For contact person which vendors not in migration scope. 


PF2/WP2
3011-002
Telephone number contains non-numeric characters

If any non-numeric characters maintained in the telephone number (ADR2-TEL_NUMBER, ADR2-TEL_EXTENS).


PF2/WP2
3011-003
Fax number contains non-numeric characters

If any non-numeric characters maintained in the fax number (ADR3-FAX_NUMBER, ADR3-TEL_EXTENS).


PF2/WP2
3011-004
Invalid email addressIf the email address is not in the pattern of XXXX@XXXXX.XX (ADR6-SMTP_ADDR) and email does contain spaces.
PF2/WP2
3011-005
Missing last nameIf the last name is blank (KNVK-NAME1)
PF2/WP2
3011-006
Missing communication languageIf the communication language (KNVK-PARLA) is blank.
PF2/WP2
3011-007
Missing countryIf the country is blank (ADRC-COUNTRY).
PF2/WP2
3011-008
Missing email addressIf the email address (ADR6-SMTP_ADDR) is blank
PF2/WP2
3011-009
Telephone Extension maintained without Telephone numberIf the Telephone number (ADR2-TEL_NUMBER) is blank and Telephone Extension (ADR2-TEL_EXTENS) is not blank.
PF2/WP2
3011-010
Fax Extension maintained without Fax numberIf the Fax number (ADR3-FAX_NUMBER) is blank and Fax Extension (ADR3-FAX_EXTENS) is not blank.
PF2/WP2

3011-011


Deduplication

Vendors with same name, Name and Telephone should be unified to avoid redundant BP creation.

Syniti Match report for business to select golden record using parent and child approach.

PF2/WP2

3011-12
Relevant vendors with no contactsIf LFA1-LIFNR does not exist in KNVK-LIFNR.
PF2/WP2



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 ECC system (i.e., WP2/PF2) periodically or from Data Collection Template (DCT). 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:

  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

Extraction Run Sheet

Req #Requirement DescriptionTeam 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 / (L2C/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 ScreenParameter NameSelection TypeRequirementValue 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 3007 customer migration list.

SE16N

Contact person for in-scope customers partner function

To select all contact person assigned to in-scope customers under partner function


Select all contact person from table KNVP Where KNVP-KUNNR is in object 3003 customer 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 3007 vendor 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 NameField DescriptionRule
PARTNERBUSINESS PARTNERDCT key running number
BU_GROUPGROUPINGDefault : BP09
TITLETITLEMust be a valid Title in TSAD3
NAME_FIRSTFirst NameMust not exceed 40 chars
NAME_LASTLast NameMust not exceed 40 chars
LANGU_CORRCORRESPONDENCE LANGUAGEMust be a valid language in T002
BU_SORT1SEARCH TERM 1Must not exceed 20 chars
BU_SORT2SEARCH TERM 2Must not exceed 20 chars
STR_SUPPL1STREET 2Must not exceed 40 chars
STR_SUPPL2STREET 3Must not exceed 40 chars
STREETSTREET NAMEMust not exceed 40 chars
STR_SUPPL3STREET 4Must not exceed 40 chars
LOCATIONSTREET 5Must not exceed 40 chars
CITY2DISTRICTMust not exceed 20 chars
POST_CODE1POSTAL CODEMust not exceed 10 chars
CITY1CITYMust be avalid City in the Country
COUNTRYCOUNTRYMust be avalid Country in T005
REGIONREGIONMust be avalid Region in T005S
PO_BOXPO BOXMust not exceed 10 chars
TEL_NUMBERTELEPHONEMust be numeric
TEL_EXTENSEXTENSIONMust be numeric
TEL_NUMBERMOBILE PHONEMust be numeric
FAX_NUMBERFAXMust be numeric
FAX_EXTENSEXTENSIONMust be numeric
SMTP_ADDRE-MAILMust be a valid email
REMARKCOMMENTSMust not exceed 50 chars

Extraction Dependencies


Item #Step DescriptionTeam 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:

  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 DescriptionTeam Responsible
1Transformation 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
2Data Mapping and Standardization
- Align source fields with target fields.
- Ensure unit consistency (e.g., currency, measurement units)		Data Team, Functional Team
3Business Rule Application
- Implement data enrichment/collection if applicable
- Apply conditional transformations based on predefined logic/business rules		Data Team, Functional Team
4Transformation Execution Plan
- Define batch processing schedules.
- Assign responsibilities for monitoring execution.
- Establish error-handling mechanisms		Syniti
5Configure transformation rules in Syniti Migrate (including calculated fields, formatting rules, etc.)Data Team (Syniti), Data Team (L2C/S2P)
6Review transformation logic and mappings with Business for confirmationBusiness Team + Functional Team (L2C/S2P)
7Perform initial transformation run and generate draft target-ready datasetData Team (Syniti),
8Review draft target-ready data for structure and completenessData Team (L2C/S2P), Functional Team (L2C/S2P)
9Share transformed data with Business for Pre-load ValidationBusiness Team
10Incorporate feedback from Business and refine mappings or transformation logic as neededData Team (L2C/S2P)
11Finalize and approve transformed data as Target Ready Load FileBusiness + Functional (L2C/S2P) + Data Team (L2C/S2P)
12Handover final file to Load Team or trigger the load via Syniti Load WorkbenchData Team (Syniti)


Transformation Rules (L2C)

Rule #Source systemSource TableSource FieldSource DescriptionTarget SystemTarget TableTarget FieldTarget DescriptionTransformation Logic
1PF2 WP2KNVKPRSNRBUSINESS PARTNERCUI ROW ChinaBUT000PARTNERBUSINESS PARTNERApply external number range.
2PF2 WP2

GROUPINGCUI ROW ChinaBUT000BU_GROUPGROUPINGDefault : BP09
3PF2 WP2KNVKANREDTITLECUI ROW ChinaBUT000TITLETITLECopy 1:1
4PF2 WP2ADRPNAME_FIRSTFirst NameCUI ROW ChinaBUT000NAME_FIRSTFirst NameCopy 1:1
5PF2 WP2ADRPNAME_LASTLast NameCUI ROW ChinaBUT000NAME_LASTLast NameCopy 1:1
6PF2 WP2

KNOWN ASCUI ROW ChinaBUT000NICKNAMEKNOWN AS

Not Used for L2C

7PF2 WP2

NAME AT BIRTHCUI ROW ChinaBUT000NAME_LAST2NAME AT BIRTH

Not Used for L2C

8PF2 WP2

MIDDLE NAMECUI ROW ChinaBUT000NAMEMIDDLEMIDDLE NAME

Not Used for L2C

9PF2 WP2

SECOND FAMILY NAMECUI ROW ChinaBUT000NAME_LST2SECOND FAMILY NAME

Not Used for L2C

10PF2 WP2

NAME AFFIX 1/2CUI ROW ChinaBUT000PREFIX1NAME AFFIX 1/2

Not Used for L2C

11PF2 WP2

NAME AFFIX 2/2CUI ROW ChinaBUT000PREFIX2NAME AFFIX 2/2

Not Used for L2C

12PF2 WP2

ACADEMIC TITLE 1/2CUI ROW ChinaBUT000TITLE_ACA1ACADEMIC TITLE 1/2

Not Used for L2C

13PF2 WP2

ACADEMIC TITLE 2/2CUI ROW ChinaBUT000TITLE_ACA2ACADEMIC TITLE 2/2

Not Used for L2C

14PF2 WP2

NAME SUPPLEMENTCUI ROW ChinaBUT000TITLE_ROYLNAME SUPPLEMENT

Not Used for L2C

15PF2 WP2

INITIALSCUI ROW ChinaBUT000INITIALSINITIALS

Not Used for L2C

16PF2 WP2

FULL NAMECUI ROW ChinaBUT000NAME1_TEXTFULL NAME

Not Used for L2C

17PF2 WP2

COUNTRY FOR FORMATCUI ROW ChinaBUT000NAMCOUNTRYCOUNTRY FOR FORMAT

Not Used for L2C

18PF2 WP2

SPECIAL FORMATCUI ROW ChinaBUT000NAMEFORMATSPECIAL FORMAT

Not Used for L2C

19PF2 WP2KNVKPARLACORRESPONDENCE LANGUAGECUI ROW ChinaBUT000LANGU_CORRCORRESPONDENCE LANGUAGECopy 1:1
20PF2 WP2KNVKPARLALANGUAGECUI ROW ChinaBUS000FLDSLANGULANGUAGECopy 1:1
21PF2 WP2KNVKANREDSALUTATIONCUI ROW ChinaBUT000TITLE_LETSALUTATIONCopy 1:1
22PF2 WP2ADRPSORTLSEARCH TERM 1CUI ROW ChinaBUT000BU_SORT1SEARCH TERM 1Copy 1:1
23PF2 WP2ADRPSORT2SEARCH TERM 2CUI ROW ChinaBUT000BU_SORT2SEARCH TERM 2Copy 1:1
24PF2 WP2

Address NumberCUI ROW ChinaADRCADDRNUMBERAddress NumberSystem
25PF2 WP2ADRCNATIONVersion ID for International AddressesCUI ROW ChinaADRCNATIONVersion ID for International AddressesCopy 1:1
26PF2 WP2

BUILDING CODECUI ROW ChinaADRCBUILDINGBUILDING CODE

Not Used for L2C

27PF2 WP2

ROOMCUI ROW ChinaADRCROOMNUMBERROOM

Not Used for L2C

28PF2 WP2

FLOORCUI ROW ChinaADRCFLOORFLOOR

Not Used for L2C

29PF2 WP2ADRCNAME_COC/OCUI ROW ChinaADRCNAME_COC/OCopy 1:1
30PF2 WP2ADRCSTR_SUPPL1STREET 2CUI ROW ChinaADRCSTR_SUPPL1STREET 2Copy 1:1
31PF2 WP2ADRCSTR_SUPPL2STREET 3CUI ROW ChinaADRCSTR_SUPPL2STREET 3Copy 1:1
32PF2 WP2ADRCSTREETSTREET NAMECUI ROW ChinaADRCSTREETSTREET NAMECopy 1:1
33PF2 WP2ADRCHOUSE_NUM1HOUSE NUMBERCUI ROW ChinaADRCHOUSE_NUM1HOUSE NUMBERCopy 1:1
34PF2 WP2ADRCHOUSE_NUM2SUPPLCUI ROW ChinaADRCHOUSE_NUM2SUPPLCopy 1:1
35PF2 WP2ADRCSTR_SUPPL3STREET 4CUI ROW ChinaADRCSTR_SUPPL3STREET 4Copy 1:1
36PF2 WP2ADRCLOCATIONSTREET 5CUI ROW ChinaADRCLOCATIONSTREET 5Copy 1:1
37PF2 WP2ADRCCITY2DISTRICTCUI ROW ChinaADRCCITY2DISTRICTCopy 1:1
38PF2 WP2ADRCHOME_CITYDIFFERENT CITYCUI ROW ChinaADRCHOME_CITYDIFFERENT CITYCopy 1:1
39PF2 WP2ADRCPOST_CODE1POSTAL CODECUI ROW ChinaADRCPOST_CODE1POSTAL CODECopy 1:1
40PF2 WP2ADRCCITY1CITYCUI ROW ChinaADRCCITY1CITYCopy 1:1
41PF2 WP2ADRCCOUNTRYCOUNTRYCUI ROW ChinaADRCCOUNTRYCOUNTRYMapping
42PF2 WP2ADRCREGIONREGIONCUI ROW ChinaADRCREGIONREGIONMapping
43PF2 WP2

TIME ZONECUI ROW ChinaADRCTIME_ZONETIME ZONESystem
44PF2 WP2ADRCTAXJURCODETAX JURISDICTIONCUI ROW ChinaADRCTAXJURCODETAX JURISDICTIONCopy 1:1
45PF2 WP2ADRCTRANSPZONETRANSPORTATION ZONECUI ROW ChinaADRCTRANSPZONETRANSPORTATION ZONEMapping
46PF2 WP2

STRUCTURE GROUPCUI ROW ChinaADRCREGIOGROUPSTRUCTURE GROUP

Not Used for L2C

47PF2 WP2

UNDELIVERABLECUI ROW ChinaADRCDONT_USE_SUNDELIVERABLE

Not Used for L2C

48PF2 WP2ADRCPO_BOXPO BOXCUI ROW ChinaADRCPO_BOXPO BOXCopy 1:1
49PF2 WP2

PO BOX W/O NO.CUI ROW ChinaADRCPO_BOX_NUMPO BOX W/O NO.

Not Used for L2C

50PF2 WP2

DELIVERY SERVICECUI ROW ChinaADRCDELI_SERV_TYPEDELIVERY SERVICE

Not Used for L2C

51PF2 WP2

DELIVERY SERVICE NUMBERCUI ROW ChinaADRCDELI_SERV_NUMBERDELIVERY SERVICE NUMBER

Not Used for L2C

52PF2 WP2

PO BOX LOBBYCUI ROW ChinaADRCPO_BOX_LOBBYPO BOX LOBBY

Not Used for L2C

53PF2 WP2ADRCPOST_CODE2POSTAL CODECUI ROW ChinaADRCPOST_CODE2POSTAL CODECopy 1:1
54PF2 WP2

OTHER CITYCUI ROW ChinaADRCPO_BOX_LOCOTHER CITY

Not Used for L2C

55PF2 WP2

OTHER COUNTRYCUI ROW ChinaADRCPO_BOX_CTYOTHER COUNTRY

Not Used for L2C

56PF2 WP2

OTHER REGIONCUI ROW ChinaADRCPO_BOX_REGOTHER REGION

Not Used for L2C

57PF2 WP2

COMPANY POSTAL CODECUI ROW ChinaADRCPOST_CODE3COMPANY POSTAL CODE

Not Used for L2C

58PF2 WP2

UNDELIVERABLECUI ROW ChinaADRCDONT_USE_SUNDELIVERABLE

Not Used for L2C

59PF2 WP2ADRCLANGULANGUAGECUI ROW ChinaADRCLANGULANGUAGECopy 1:1
60PF2 WP2

Address NumberCUI ROW ChinaADR2ADDRNUMBERAddress NumberSystem
61PF2 WP2

Sequence NumberCUI ROW ChinaADR2CONSNUMBERSequence NumberSystem
62PF2 WP2ADR2TEL_NUMBERTELEPHONECUI ROW ChinaADR2TEL_NUMBERTELEPHONECopy 1:1
63PF2 WP2ADR2TEL_EXTENSEXTENSIONCUI ROW ChinaADR2TEL_EXTENSEXTENSIONCopy 1:1
64PF2 WP2ADR2TEL_NUMBERMOBILE PHONECUI ROW ChinaADR2TEL_NUMBERMOBILE PHONECopy 1:1
65PF2 WP2
 
CUI ROW ChinaADR2FLGDEFAULTStandard Sender Address in this Communication TypeSystem
66PF2 WP2ADR2FLG_NOUSEFlag: This Communication Number is Not UsedCUI ROW ChinaADR2FLG_NOUSEFlag: This Communication Number is Not UsedCopy 1:1
67PF2 WP2ADR2HOME_FLAGRecipient address in this communication type (mail sys.grp)CUI ROW ChinaADR2HOME_FLAGRecipient address in this communication type (mail sys.grp)Copy 1:1
68PF2 WP2

Address NumberCUI ROW ChinaADR3ADDRNUMBERAddress NumberSystem
69PF2 WP2

Sequence NumberCUI ROW ChinaADR3CONSNUMBERSequence NumberSystem
70PF2 WP2ADR3FAX_NUMBERFAXCUI ROW ChinaADR3FAX_NUMBERFAXCopy 1:1
71PF2 WP2ADR3FAX_EXTENSEXTENSIONCUI ROW ChinaADR3FAX_EXTENSEXTENSIONCopy 1:1
72PF2 WP2


CUI ROW ChinaADR3FLGDEFAULTStandard Sender Address in this Communication TypeSystem
73PF2 WP2ADR3FLG_NOUSEFlag: This Communication Number is Not UsedCUI ROW ChinaADR3FLG_NOUSEFlag: This Communication Number is Not UsedCopy 1:1
74PF2 WP2ADR3HOME_FLAGRecipient address in this communication type (mail sys.grp)CUI ROW ChinaADR3HOME_FLAGRecipient address in this communication type (mail sys.grp)Copy 1:1
75PF2 WP2

Address NumberCUI ROW ChinaADR6ADDRNUMBERAddress NumberSystem
76PF2 WP2

Sequence NumberCUI ROW ChinaADR6CONSNUMBERSequence NumberSystem
77PF2 WP2ADR6SMTP_ADDRE-MAILCUI ROW ChinaADR6SMTP_ADDRE-MAILCopy 1:1
78PF2 WP2


CUI ROW ChinaADR6FLGDEFAULTFlag: this address is the default addressSystem
79PF2 WP2ADR6FLG_NOUSEFlag: This Communication Number is Not UsedCUI ROW ChinaADR6FLG_NOUSE

Flag: This Communication Number is Not Used

Copy 1:1
80PF2 WP2ADR6HOME_FLAGRecipient address in this communication type (mail sys.grp)CUI ROW ChinaADR6HOME_FLAG

Recipient address in this communication type (mail sys.grp)

Copy 1:1
81PF2 WP2ADRCTREMARKCOMMENTSCUI ROW ChinaADRCTREMARKCOMMENTSCopy 1:1
82PF2 WP2ADR2FLGDEFAULT

Default Flag

CUI ROW ChinaADRUCOMM_TYPEComm. MethodIF ADR2-FLGDEFAULT = 'X' THEN
COMM_TYPE = TEL
ENDIF
83PF2 WP2ADR2FLGDEFAULTDefault FlagCUI ROW ChinaADRUCOMM_USAGEUSEIF ADR2-FLGDEFAULT = 'X' THEN
COMM_USAGE = AD_DEFAULT
ENDIF
84PF2 WP2ADR2FLGDEFAULTDefault FlagCUI ROW ChinaADRUVALID_FROMVALID FROMIF ADR2-FLGDEFAULT = 'X' THEN
VALID FROM = Load Date
ENDIF
85PF2 WP2ADR2FLGDEFAULTDefault FlagCUI ROW ChinaADRUVALID_TOVALID TOIF ADR2-FLGDEFAULT = 'X' THEN
VALID FROM = 31.12.9999
ENDIF
86PF2 WP2ADR3FLGDEFAULT

Default Flag

CUI ROW ChinaADRUCOMM_TYPEComm. MethodIF ADR3-FLGDEFAULT = 'X' THEN
COMM_TYPE = FAX
ENDIF
87PF2 WP2ADR3FLGDEFAULTDefault FlagCUI ROW ChinaADRUCOMM_USAGEUSEIF ADR3-FLGDEFAULT = 'X' THEN
COMM_USAGE = AD_DEFAULT
ENDIF
88PF2 WP2ADR3FLGDEFAULTDefault FlagCUI ROW ChinaADRUVALID_FROMVALID FROMIF ADR3-FLGDEFAULT = 'X' THEN
VALID FROM = Load Date
ENDIF
89PF2 WP2ADR3FLGDEFAULTDefault FlagCUI ROW ChinaADRUVALID_TOVALID TOIF ADR3-FLGDEFAULT = 'X' THEN
VALID FROM = 31.12.9999
ENDIF
90PF2 WP2ADR6FLGDEFAULT

Default Flag

CUI ROW ChinaADRUCOMM_TYPEComm. MethodIF ADR6-FLGDEFAULT = 'X' THEN
COMM_TYPE = INT
ENDIF
91PF2 WP2ADR6FLGDEFAULTDefault FlagCUI ROW ChinaADRUCOMM_USAGEUSEIF ADR6-FLGDEFAULT = 'X' THEN
COMM_USAGE = AD_DEFAULT
ENDIF
92PF2 WP2ADR6FLGDEFAULTDefault FlagCUI ROW ChinaADRUVALID_FROMVALID FROMIF ADR6-FLGDEFAULT = 'X' THEN
VALID FROM = Load Date
ENDIF
93PF2 WP2ADR6FLGDEFAULTDefault FlagCUI ROW ChinaADRUVALID_TOVALID TOIF ADR6-FLGDEFAULT = 'X' THEN
VALID FROM = 31.12.9999
ENDIF
94PF2 WP2ADRPNATIONAddress VersionCUI ROW ChinaADRPNATIONAddress VersionCopy 1:1


Transformation Rules (S2P Vendor)

  •  From legacy ECC source

Rule #Source systemSource TableSource FieldSource DescriptionTarget SystemTarget TableTarget FieldTarget DescriptionTransformation Logic
1PF2 WP2KNVKPRSNRBUSINESS PARTNERCUI ROW ChinaBUT000PARTNERBUSINESS PARTNERSystem
2PF2 WP2N/AN/AN/ACUI ROW ChinaBUT000BU_GROUPGROUPINGDefault : BP09
3PF2 WP2KNVKANREDTITLECUI ROW ChinaBUT000TITLETITLECopy
4PF2 WP2KNVKNAMEVFirst NameCUI ROW ChinaBUT000NAME_FIRSTFirst Name

Rule:

  If KNVK-NAMEV is blank, parse from first name of KNVK-NAME1.

5PF2 WP2KNVKNAME1Last NameCUI ROW ChinaBUT000NAME_LASTLast Name

Rule:

  If contains '@', then parse last name from KNVK-NAME1, else copy KNVK-NAME1.

6PF2 WP2KNVKPARLACORRESPONDENCE LANGUAGECUI ROW ChinaBUT000LANGU_CORRCORRESPONDENCE LANGUAGECopy
7PF2 WP2KNVKANREDSALUTATIONCUI ROW ChinaBUT000TITLE_LETSALUTATIONCopy
8PF2 WP2KNVKSORTLSEARCH TERM 1CUI ROW ChinaBUT000BU_SORT1SEARCH TERM 1Copy
9PF2 WP2ADRCSORT2SEARCH TERM 2CUI ROW ChinaBUT000BU_SORT2SEARCH TERM 2Copy
10PF2 WP2ADRCNAME_COC/OCUI ROW ChinaADRCNAME_COC/ONot Used
11PF2 WP2ADRCSTR_SUPPL1STREET 2CUI ROW ChinaADRCSTR_SUPPL1STREET 2Copy
12PF2 WP2ADRCSTR_SUPPL2STREET 3CUI ROW ChinaADRCSTR_SUPPL2STREET 3Copy
13PF2 WP2ADRCSTREETSTREET NAMECUI ROW ChinaADRCSTREETSTREET NAMECopy
14PF2 WP2ADRCHOUSE_NUM1HOUSE NUMBERCUI ROW ChinaADRCHOUSE_NUM1HOUSE NUMBERNot Used
15PF2 WP2ADRCHOUSE_NUM2SUPPLCUI ROW ChinaADRCHOUSE_NUM2SUPPLNot Used
16PF2 WP2ADRCSTR_SUPPL3STREET 4CUI ROW ChinaADRCSTR_SUPPL3STREET 4Copy
17PF2 WP2ADRCLOCATIONSTREET 5CUI ROW ChinaADRCLOCATIONSTREET 5Copy
18PF2 WP2ADRCCITY2DISTRICTCUI ROW ChinaADRCCITY2DISTRICTCopy
19PF2 WP2ADRCHOME_CITYDIFFERENT CITYCUI ROW ChinaADRCHOME_CITYDIFFERENT CITYNot Used
20PF2 WP2ADRCPOST_CODE1POSTAL CODECUI ROW ChinaADRCPOST_CODE1POSTAL CODECopy
21PF2 WP2ADRCCITY1CITYCUI ROW ChinaADRCCITY1CITYCopy
22PF2 WP2ADRCCOUNTRYCOUNTRYCUI ROW ChinaADRCCOUNTRYCOUNTRYMapping
23PF2 WP2ADRCREGIONREGIONCUI ROW ChinaADRCREGIONREGIONMapping
24PF2 WP2N/AN/AN/ACUI ROW ChinaADRCTIME_ZONETIME ZONESystem
25PF2 WP2ADRCTAXJURCODETAX JURISDICTIONCUI ROW ChinaADRCTAXJURCODETAX JURISDICTIONCopy
26PF2 WP2ADRCTRANSPZONETRANSPORTATION ZONECUI ROW ChinaADRCTRANSPZONETRANSPORTATION ZONEMapping
27PF2 WP2ADRCPO_BOXPO BOXCUI ROW ChinaADRCPO_BOXPO BOXCopy
28PF2 WP2ADRCPOST_CODE2POSTAL CODECUI ROW ChinaADRCPOST_CODE2POSTAL CODECopy
29PF2 WP2KNVKPARLALANGUAGECUI ROW ChinaADRCLANGULANGUAGECopy
30PF2 WP2ADR2TEL_NUMBERTELEPHONECUI ROW ChinaADR2TEL_NUMBERTELEPHONECopy
31PF2 WP2ADR2TEL_EXTENSEXTENSIONCUI ROW ChinaADR2TEL_EXTENSEXTENSIONCopy
32PF2 WP2ADR2FLGDEFAULTStandard Sender Address in this Communication TypeCUI ROW ChinaADR2FLGDEFAULTStandard Sender Address in this Communication TypeCopy
33PF2 WP2ADR2TEL_NUMBERTELEPHONECUI ROW ChinaADR2TEL_NUMBERMOBILE PHONECopy
34PF2 WP2ADR3FAX_NUMBERFAXCUI ROW ChinaADRCFAX_NUMBERFAXCopy
35PF2 WP2ADR3FAX_EXTENSEXTENSIONCUI ROW ChinaADRCFAX_EXTENSEXTENSIONCopy
36PF2 WP2ADR3FLGDEFAULTStandard Sender Address in this Communication TypeCUI ROW ChinaADR3FLGDEFAULTStandard Sender Address in this Communication TypeCopy
37PF2 WP2ADR6SMTP_ADDRE-MAILCUI ROW ChinaADR6SMTP_ADDRE-MAILCopy
38PF2 WP2ADR6FLGDEFAULTFlag: this address is the default addressCUI ROW ChinaADR6FLGDEFAULTFlag: this address is the default addressCopy
39PF2 WP2ADRCTREMARKCOMMENTSCUI ROW ChinaADRCTREMARKCOMMENTSCopy

  • From DCT source

Rule #Source systemSource TableSource FieldSource DescriptionTarget SystemTarget TableTarget FieldTarget DescriptionTransformation Logic
1DCTBPContact_DCTPARTNERBUSINESS PARTNERCUI ROW ChinaBUT000PARTNERBUSINESS PARTNERSystem
2DCTBPContact_DCTBU_GROUPGROUPINGCUI ROW ChinaBUT000BU_GROUPGROUPINGDefault : BP09
3DCTBPContact_DCTTITLETITLECUI ROW ChinaBUT000TITLETITLECopy
4DCTBPContact_DCTNAME_FIRSTFirst NameCUI ROW ChinaBUT000NAME_FIRSTFirst NameCopy
5DCTBPContact_DCTNAME_LASTLast NameCUI ROW ChinaBUT000NAME_LASTLast NameCopy
6DCTBPContact_DCTLANGU_CORRCORRESPONDENCE LANGUAGECUI ROW ChinaBUT000LANGU_CORRCORRESPONDENCE LANGUAGECopy
7DCTBPContact_DCTBU_SORT1SEARCH TERM 1CUI ROW ChinaBUT000BU_SORT1SEARCH TERM 1Copy
8DCTBPContact_DCTBU_SORT2SEARCH TERM 2CUI ROW ChinaBUT000BU_SORT2SEARCH TERM 2Copy
9DCTBPContact_DCTSTR_SUPPL1STREET 2CUI ROW ChinaADRCSTR_SUPPL1STREET 2Copy
10DCTBPContact_DCTSTR_SUPPL2STREET 3CUI ROW ChinaADRCSTR_SUPPL2STREET 3Copy
11DCTBPContact_DCTSTREETSTREET NAMECUI ROW ChinaADRCSTREETSTREET NAMECopy
12DCTBPContact_DCTSTR_SUPPL3STREET 4CUI ROW ChinaADRCSTR_SUPPL3STREET 4Copy
13DCTBPContact_DCTLOCATIONSTREET 5CUI ROW ChinaADRCLOCATIONSTREET 5Copy
14DCTBPContact_DCTCITY2DISTRICTCUI ROW ChinaADRCCITY2DISTRICTCopy
15DCTBPContact_DCTPOST_CODE1POSTAL CODECUI ROW ChinaADRCPOST_CODE1POSTAL CODECopy
16DCTBPContact_DCTCITY1CITYCUI ROW ChinaADRCCITY1CITYCopy
17DCTBPContact_DCTCOUNTRYCOUNTRYCUI ROW ChinaADRCCOUNTRYCOUNTRYCopy
18DCTBPContact_DCTREGIONREGIONCUI ROW ChinaADRCREGIONREGIONCopy
19DCTBPContact_DCTPO_BOXPO BOXCUI ROW ChinaADRCPO_BOXPO BOXCopy
20DCTBPContact_DCTTEL_NUMBERTELEPHONECUI ROW ChinaADR2TEL_NUMBERTELEPHONECopy
21DCTBPContact_DCTTEL_EXTENSEXTENSIONCUI ROW ChinaADR2TEL_EXTENSEXTENSIONCopy
22DCTBPContact_DCTTEL_NUMBERTELEPHONECUI ROW ChinaADR2TEL_NUMBERMOBILE PHONECopy
23DCTBPContact_DCTFAX_NUMBERFAXCUI ROW ChinaADRCFAX_NUMBERFAXCopy
24DCTBPContact_DCTFAX_EXTENSEXTENSIONCUI ROW ChinaADRCFAX_EXTENSEXTENSIONCopy
25DCTBPContact_DCTSMTP_ADDRE-MAILCUI ROW ChinaADR6SMTP_ADDRE-MAILCopy
26DCTBPContact_DCTREMARKCOMMENTSCUI ROW ChinaADRCTREMARKCOMMENTSCopy

Transformation Mapping

Transformation Mapping Document Link
Mapping Table NameMapping Table Description
MAP_LAND1COUNTRY
MAP_REGIONREGION
MAP_LZONETRANSPORTATION ZONE
N/A for Vendor




Transformation Dependencies

List the steps that need to occur before transformation can commence
Item #Step DescriptionTeam Responsible
1Source Data Integrity
- Ensure extracted data is complete, accurate, and consistent.
- Validate that data types and formats align with transformation requirements.		Syniti
2Referential Integrity
- Ensure dependent records are transformed together or in advance		Syniti
3Transformation Logic and Mapping
- Define data mapping rules between source and target schemas.		Data Team
4Performance and Scalability Considerations
- Optimize transformation processes for large datasets.
- Ensure system resources can handle transformation workloads		Syniti
5Logging 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

TaskAction

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

TaskAction

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

TaskAction

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

TaskAction

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:

  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 DescriptionTeam Responsible
1Load 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
2Load Methodology
- Specify the loading tools and technologies (Migration Cockpit, LSMW, custom loading program).		Syniti
3Data 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
4Load Execution Plan
- Establish execution timelines and batch processing schedules.
- Assign responsibilities for monitoring execution.
- Document dependencies on other migration tasks		Syniti
5Logging 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

Role BUP001 is configured and valid in the target system in table TB003





Conversion Objects

Object #Preceding Object Conversion Approach
3003Business Partners - Customer (Sales and Service) - FLCU01
3007Business Partners - General (Role 000000)
3026Business Partners - 3rd Party Suppliers-FLVN01

Error Handling

Error TypeError DescriptionAction Taken
1

The value XXX for field XXX doesn't exist

  1. Check the mapping/conversion is done properly in the loading file
  2. Validate the target value is configured/transported in the target system
  3. Reach out to function team to validate the configuration
2

There is mandatory field XXX missing

  1. Validate MDS if the fields are set as mandatory
  2. Validate if there is value in the pre-loading file
  3. Validate if the configuration for the mandatory fields are done properly




Post-Load Validation

Project Team

Completeness

TaskAction

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

TaskAction
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

Completeness

TaskAction
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

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





Key Assumptions

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


See also

Change log

Version Published Changed By Comment
CURRENT (v. 56) Apr 15, 2026 05:39 CELEDONIO-ext, Arnold
v. 82 Mar 30, 2026 15:21 LEW-ext, Chun Ming Correct TPAR-NRART
v. 81 Mar 13, 2026 11:26 LEW-ext, Chun Ming
v. 80 Mar 04, 2026 07:48 LEW-ext, Chun Ming Update for the number range
v. 79 Feb 26, 2026 10:15 CELEDONIO-ext, Arnold Update FAX mapping typo ADRC to ADR3
v. 78 Feb 23, 2026 13:28 LEW-ext, Chun Ming Remove CUI portion
v. 77 Feb 11, 2026 10:24 CELEDONIO-ext, Arnold Remouve CUI references for Vendor
v. 76 Feb 04, 2026 10:36 LEW-ext, Chun Ming
v. 75 Feb 02, 2026 15:53 CELEDONIO-ext, Arnold
v. 74 Feb 02, 2026 15:43 CELEDONIO-ext, Arnold

Go to Page History

Workflow history

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

  • No labels