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

Compare with Current View Page History

« Previous Version 103 Next »

Status

  Update in progress

Owner

RUAN-ext, Eric CELEDONIO-ext, Arnold  MADHOK-ext, Jasleen 

Stakeholders

Purpose

The purpose of this document is to define the conversion approach to create Business Partners - General in S/4 HANA.

In SAP ECC, customer and vendor master data are maintained separately as distinct entities. Customers are managed through Customer Master Data, while vendors are handled via Vendor Master Data. These records store essential details such as company name, address, payment terms, and tax information.
In SAP S/4HANA, the Business Partner (BP) concept replaces the traditional customer and vendor master data approach. The BP model integrates both customer and vendor roles into a single entity, simplifying data management and ensuring consistency across different business functions


Conversion Scope

The scope of this document covers the approach for converting active Customer Master Data General and Vendor Master General from Legacy Source Systems into S/4HANA Business Partner (BP) General (Role 000000) Master Data Design Standard. 


Customer Master Data - General Information

The data from legacy system includes:

1. Customer with AR Balance under the company codes within S4 Hana implementation scope (BSID-KUNNR).
2. or (Customer doesn't have central deletion indicator (KNA1-LOEVM="") AND Customer has active sales view data within the sales organizations in scope(KNVV-KUNNR)) and there is usage within 4 years. * modified on 16/Oct/2025
3. or (Customer doesn't have central deletion indicator and customer has active company code view within the company codes in scope) and there is usage within 4 years. * modified on 16/Oct/2025
4. or Customer is part of Customer Hierarchy Higher Node, and the sales area data is part of the sales areas within migration scope
5. or there is customer consignment stock and the plant for the consignment stock is within S4 Hana implementation scope. 
6. or Customer is set as the credit account for other customers, and either the customer or credit account customer is not deleted. (if both customer or credit account is deleted, then not in migration scope)

7.  Intercompany customer will be defined based on the Enterprise structure. (To identify Intercompany customer, trading partner will be used. In the meantime, Group field(KNA1-KONZS) from customer general data will be used. For WP2/PF2, Group value = 0000810135 (Syensqo) )

8. or the customer in the partner function is active, then the parent customer will also be migrated. * added on 16/Oct/2025

9. or the customer is active in Salesforce and there are activities within 48 months.* added on 16/Oct/2025

10. or there is an existing forecast for the customer in Kinaxis. * added on 16/Oct/2025

11. or there is active master data for the customer, such as active Pricing Condition records. * added on 16/Oct/2025



CriteriaRelevancy RuleTechnical Details
1Customer with AR Balance under the company codes within S4 Hana implementation scope Select KUNNR from BSID where BSID-BUKRS in (Company code in scope)
2

or (Customer doesn't have central deletion indicator AND Customer has active sales view data within the sales organizations in scope) and there is usage within 2 years.

Select KUNNR from KNA1 where KNA1-LOEVM="" and KNVV-KUNNR = KNA1-KUNNR AND KNVV-VKORG in (Sales Org in scope) and KNVV-LOEVM = "" and usage within 4 years. 


  1. Accounting document (Select MAX(BSAD/BSID-CPUDT) where BSAD/BSID-KUNNR =KNA1-KUNNR and BSAD/BSID-BUKRS = (Company code in scope) )
  2. Sales Document (Select MAX(VBAK-ERDAT) WHERE VBAK-VBELN=VBPA-VBELN AND VBPA-KUNNR = KNA1-KUNNR)
  3. Delivery Document (Select MAX(LIKP-ERDAT) WHERE LIKP-VBELN=VBPA-VBELN AND VBPA-KUNNR = KNA1-KUNNR)
  4. Billing   (Select MAX(VBRK-ERDAT) WHERE VBRK-VBELN=VBPA-VBELN AND VBPA-KUNNR = KNA1-KUNNR)
3

or (Customer doesn't have central deletion indicator and customer has active company code view within the company codes in scope) and there is usage within 2 years

Select KUNNR from KNA1 where KNA1-LOEVM="" and KNB1-KUNNR = KNA1-KUNNR AND KNB1-BUKRS in (Company code in scope) and KNB1-LOVEM = "" and usage with 4 years


  1. Accounting document (Select MAX(BSAD/BSID-CPUDT) where BSAD/BSID-KUNNR =KNA1-KUNNR and BSAD/BSID-BUKRS = (Company code in scope) )
  2. Sales Document (Select MAX(VBAK-ERDAT) WHERE VBAK-VBELN=VBPA-VBELN AND VBPA-KUNNR = KNA1-KUNNR)
  3. Delivery Document (Select MAX(LIKP-ERDAT) WHERE LIKP-VBELN=VBPA-VBELN AND VBPA-KUNNR = KNA1-KUNNR)
  4. Billing   (Select MAX(VBRK-ERDAT) WHERE VBRK-VBELN=VBPA-VBELN AND VBPA-KUNNR = KNA1-KUNNR)
4or Customer is part of Customer Hierarchy Higher Node, and the sales area data is part of the sales areas within migration scopeSelect HKUNNR from KNVH where KNVH-VKORG in (Sales Org in scope)
5or there is customer consignment stock and the plant for the consignment stock is within S4 Hana implementation scope. Select KUNNR from MSKU where MSKU-WERKS in (Plant in scope)
6or Customer is used for Credit Limit Reference in Credit Management, only when the credit account is different from the customer, and at least credit account or customer is still active.Select  KNKLI from KNKK where KNKK-KKBER  = T001CM-KKBER  and T001CM-BUKRS in (Company Code in scope based on the sales organization) where KNKK-KUNNR<>KNKK-KNKLI AND (KNA1-LOEVM is initial where KNA1-KUNNR = KNKK-KUNNR or KNA1-LOEVM is initial where KNA1-KUNNR = KNKK-KNKLI)
7Intercompany Customer is in migration scope, but it will be use Data Collection Template to collect the informationKNA1-VBUND <>"" or KNA1-KONZS
8or the customer in the partner function is active and in migration scope, then the parent customer will also be migrated based on rule 2. * added on 16/Oct/2025

Select KNVP-KUNNR INNER

JOIN KNA1 as a WHERE KNVP-KUNNR = a.kunnr and a.loevm = X and KNVP-VKORG in 'Sales Org in scope'

inner join kna1 as b where knvp-kunn2 = b.kunnr and b.loevm  = '' and kunn2 in rule 2

9or the customer is active in Salesforce and there are activities within 48 months.

Two reports will be provided.


iCare - If (there is value in field 'PRS Code (Account)' or 'RCS code (Account)') and 'Last Activity' is within 48 months and Type <> "Inactive Customer". then the account is in scope. 'PRS Code (Account)' is mapped to PF2 customer number, 'RCS code (Account)' is mapped to WP2 customer number.


Core CRM - If (there is value in field 'PRS ID / RCS ID') and 'Last Activity' is within 48 months and 'Account Organization' = 'SCO' and 'Status'<>"Rejected", then the account is in scope. 'PRS ID / RCS ID' need to split using "/" to get the PRS/RCS code and 'GBU'  in (Novecare, Technology Solutions). 

10or there is an existing forecast for the customer in Kinaxis.
  • This will be parked for now
11or there is active master data for the customer, such as active Pricing Condition records.
  • This will be parked for now

The data from legacy system excludes:

  1. One time customer (Account group is Z004 or ZCPD)
CriteriaRelevancy RuleTechnical Details
1

One time customer (Account group is Z004)

KNA1-KTOKD = Z004 or ZCPD


List of source systems and approximate number of records 
SourceScope

Source Approx No. of Records

Target SystemTarget Approx

No. of Records

WP2Customer Master Data General Information55371S4 Hana ROW / China / CUI55371
PF2Customer Master Data General Information36983S4 Hana ROW / China / CUI36983
WP2Customer Master Data General Information10315S4 Hana China10315
PF2Customer Master Data General Information10168S4 Hana China10168
WP2Customer Master Data General Information7321S4 Hana CUI7321
PF2Customer Master Data General InformationN/AS4 Hana CUIN/A

Vendor Master Data - General Information

The data from legacy system includes:

  1. Vendors’ relevant general data with potential duplicate records (refer Relevancy Criteria for Vendor inclusion)
  2. Vendors’ relevant general data with potential missing information such as bank, tax, etc related fields

The data from legacy system excludes:

  1. Vendors marked for deletion (refer Relevancy Criteria for Vendor exclusion)
  2. Inactive vendors with no transactions for the past 2 years  

 List of source systems and approximate number of records 

SourceScope

Source Approx No. of Records

Target SystemTarget Approx

No. of Records

WP2. PF2

Vendor Master Data General Information

Extract from LFA1, LFB1, LFM1, EKPA, EKKO according to relevancy criteria for vendor and deduplication nominations  

70,000S4 Hana< 70,000
DCT

All active BP's in Intercompany DCT, includes

  • Plant
  • Trade partner
  • Non Trade partner

The number range for Inter-Company is external (as per in MDS) with the following prefixed

  • PLYYYY, where YYYY is plant code (Plant Partner to support stock transfer process. One record per plant)
  • ICT XXXX, where XXXX is company code (Trade Partner to support intercompany stock transfer process)
  • ICNXXXX, where XXXX is company code (Non Trade Partner to support intercompany stock transfer process)

Data collection will be prepared and there's a mapping between Syensqo entities as Vendor in WP2/PF2 and those created in BP Intercompany entities.     

Please refer to data object 3027 - Business Partners - Plants/Intercompany Suppliers for more details


S4 Hana





















Relevancy Criteria for Vendor :

Rules

Relevancy rules - All must be true for the Vendor to be considered for relevancy

1

Deletion Flag and Vendor blocks flagged as no longer used anywhere in system

where Vendor does not belong to the conditions below

  1.  LFA1-LOEVM =  'X' or
  2. LFA1-ZZR_ZLATR8 = ZBY (Unauthorized Vendor requested by Buyers)

2

Has at least one valid extension

having entry in LFB1/LFM1 where LOEVM <> 'X' with Company Code/Purchasing Organization in scope

3

Exclude Inter-company suppliers (identified with class G - group) 

where ZZR_SEGT_ATTR <> 'G'

4

Exclude employees as well where Account groups: (ZZPE / Z012)

if zSource = 'PF2' and KTOKK <> 'ZZPE'

if zSource = 'WP2' and KTOKK <> 'Z012'

Additional rules - Only one needs to be true for the Vendor to be ‘relevant’ [only Vendor that have passed ‘Relevancy rules’ above are included]

1

Has Purchase Order created last 4 yrs

where Vendor has PO created (EKKO-AEDAT in past 4 yrs) and EKKO-BSTYP=F and EKKO-LOEKZ<>X and (EKORG/BUKRS/WERKS in-scope)

2

Has Cleared Items created last 4 yrs

where LIFNR has AP clearing date (BSAK-AUGDT in past 4 yrs) and (EKORG/BUKRS/WERKS in-scope)

3

Has a valid Contract 

where Vendor has Contract created (EKKO-KDATE<Current-Date and EKKO-BSTYP=K and EKKO-LOEKZ<>X and (EKORG/BUKRS/WERKS in-scope)

4

Has and open purchase order

where Vendor has PO (EKKO-BSTYP=F and and EKKO-LOEKZ<>X and EKPO.EREKZ='' and EKPO-LOEKZ<>X and (EKORG/BUKRS/WERKS in-scope)

5

Is a valid Partner in PO/SO created last 4 yrs

here Vendor having entry in EKPA-LIFN2 (PO created in last 4 yrs) or 
in VBPA-LIFNR (SO created in last 4 yrs)

6

Vendor created in the last 6 months

where Current-Date < LFA1-ERDAT > Current-Date – 6 months

7

Is linked to a valid Customer

where Vendor is linked to a relevant Customer (KNA1-LIFNR )

8

Has Open Items Not Cleared 

where Vendor has an entry in BSIK-LIFNR  (within legal company code in scope) 

9

Is One-Time Vendor 

where Vendor Segment Class LFA1-ZZR_SEGT_ATTR is 'D'  (for info only / no activity checks required)

10

Last purchase order transaction date

Vendor's max(EKKO-AEDAT) where and EKKO-BSTYP=F and EKKO-LOEKZ<>X (for info only / no activity checks required)

11

Has Purchase Order created last 5 yrs (only for ZIND/ZABF material types)

where Vendor has PO created (EKKO-AEDAT in past 5yrs) and EKKO-BSTYP=F and EKKO-LOEKZ<>X and EKPO-LOEKZ<>X

and EKPO-MATNR in (MARA-MATNR where MARA-MTART in S4(ZIND/ZABF)) and (EKORG/BUKRS/WERKS in-scope)

12

Has Cleared Items created last 5 yrs (only for ZIND/ZABF material types)

where LIFNR has AP clearing date (BSAK-AUGDT in past 5 yrs) and BSAK-EBELN in

(EKPO-EBELN and and EKPO-LOEKZ<>X and EKPO-MATNR in (MARA-MATNR where MARA-MTART in S4(ZIND/ZABF)) and (EKORG/BUKRS/WERKS in-scope)

13

Has Purchase Requisitions in the last 4 yrs

where Vendor has PR created (EBAN-AEDAT in past 4 yrs) and EBAN-BSTYP=F and EBAN-LOEKZ<>X and (EKORG/BUKRS/WERKS in-scope)

14

Has Process Orders with external procurement in the last 4 yrs

AFKO / AFPO MATNR in-scope???

15

Has Valid SourceList

where LFA1-LIFNR = EORD-LIFNR and EORD-BDATU >= Current-Date and (EKORG/BUKRS/WERKS in-scope)

16

Has valid PIR (Purchase Info Records)

where EINA / EINE (LOEKZ<>X) and (EKORG/BUKRS/WERKS in-scope)

Exception Rules (disregard all above rules)

1

Has VAT changed last 4 yrs

where Vendor EKPA-LIFN2 used in Partner Function EKPA-PARVW 'IP' (Invoice Presented By) and 'VN' (Vendor) is different in open PO. 

2

Inclusion/Exclusion List

Force any vendors to be included or excluded.


   Exclude given list of Vendors from Activity based checks:

1

We should exclude activity checks for Vendors which are extended to Company Code view only (Finance Vendors)- Invoicing Partner/Banks

LFA1-LIFNR not in LFM1

and Vendor does not belong to the conditions below

  1.  LFA1-LOEVM =  'X' or
  2. LFA1-ZZR_ZLATR8 = ZBY (Unauthorized Vendor requested by Buyers)

2

We need to check Vendor ‘Partner Function’ role also (OA, PI) even if they are not extended to any company code or purchasing org. If active Vendors are used as only invoicing Party or as Ordering Address then those vendors will not have any POs.

WYT3-PARVW = 'OA' or 'PI' 

and Vendor does not belong to the conditions below

  1.  LFA1-LOEVM =  'X' or
  2. LFA1-ZZR_ZLATR8 = ZBY (Unauthorized Vendor requested by Buyers)
3

Catalog suppliers (even if they are not extended to any company code or purchasing org)- identified in the attribute 6 field 

ZZR_ZLATR6 = 'CEA' or 'CIA' or 'CIM' or 'COA', or 'CSA'

and Vendor does not belong to the conditions below

  1.  LFA1-LOEVM =  'X or
  2. LFA1-ZZR_ZLATR8 = ZBY (Unauthorized Vendor requested by Buyers)
4

Commission Agents (39*****) where account group is 'ZXAG' even if they are not extended to any company code or purchasing org.

where KTOKK = 'ZXAG'

and Vendor does not belong to the conditions below

  1.  LFA1-LOEVM =  'X' or
  2. LFA1-ZZR_ZLATR8 = ZBY (Unauthorized Vendor requested by Buyers)
5

Not used/Duplicate/VATchange

 LFA1-ZZR_ZLATR8 = ZVN ( (for info only)

and Vendor does not belong to the conditions below

  1.  LFA1-LOEVM =  'X' or
  2. LFA1-ZZR_ZLATR8 = ZBY (Unauthorized Vendor requested by Buyers)

Additional Information

Multi-language Requirement

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


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

Document Management

It is possible the customer has attachment in the legacy system. The migration of attachment will be captured in conversion spec CNV-3004 - Attachment for customer master data. 

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. 

Special Requirements

If the data conversion involves third-party systems or external data sources, such as Icertis, describe any additional requirements related to data mapping, transformation logic, validation rules or security measures that must be followed.

Customer Master Data - General Information

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.

  1. For entities in China, the data will be loaded into SAP China instance while the entire migration process will remain the same as rest of the world.

Please refer to the link for the entity mapping for each instance. SAP instance mapping based on company code

 - To identify the record is for which SAP instance, it will follow below logic. If the same customer is mapped to multiple instances, the customer general data will be migrated in the respective SAP instance. 

  1. For customer with company code view in scope, map the company code to the SAP instance based on the mapping file. 
  2. For customer with sales view in scope, map the sales org to company code first, then map the company code to the SAP instance based on the mapping file.
  3. Reconcile the result from step 1/step 2, and remove duplicate based on Customer/SAP Instance combination.


B. WP2/PF2 Customer General Data Reconciliation

In the meantime, for WP2/PF2 customer master general data, it is possible they are both coming from the same MDM PRS system, therefore, a de-duplication or reconciliation needs to be performed based on below logic. 

  1. In PF2, it will have the relationship that KNA1-ZZR_KUNNR_RCS (RCS Customer code) = WP2, KNA1-KUNNR, then it refers to the same customer. 
  2. In WP2, it will have the relationship that KNA1-ZZR_KUNNR_PRS (PRS Customer code)= PF2, KNA1-KUNNR, then it refers to the same customer. 


C. Intercompany BP General Data

For Intercompany BP, it is in the migration scope. However, as the definition of the to-be Intercompany BP is different from the existing ECC Intercompany BP definition, instead of migrating the ECC Intercompany BP directly, a DCT will be utilized to collect the intercompany information, then map to the ECC customer/vendor number if applicable.


GroupingBP GroupingFrom NumberComments
BPABIntercompany Customer - Trade ICTXXXXwhere XXXX is company code
BPABIntercompany Customer - Non TradeICNXXXXwhere XXXX is company code
BPABPlantPLYYYYwhere YYYY is plant code


 D. BP Number Range

In the BAU (business as usual) scenario, the BP number range for external parties will be Internal number range, meaning SAP will generate the running number based on the sequence of creation. For the migration purpose, it will adopt the external number range, which means each partner will have a pre-defined number when migrating to S4 Hana system. The consideration for this set up is to prepare the R3 customer migration in salesforce to keep the number in sync in both Salesforce and S4 Hana. Although the migration is using external number range, the pattern will be the same as internal number range.


GroupingBP GroupingFrom NumberTo Number
BP02Internal Numbering for standard use100000099999999


E. One-time Customer

One time customer will not be migrated directly. However, if there is one time customer used in the open sales documents, or AR, a corresponding customer will be created as a normal customer. 


 Vendor Master Data - General Information

A. Different SAP Instance Migration Approach

There're three target SAP S4 Hana instances which will follow the following approach -

  • Rest Of The World (All remaining entities from rest of the world will be loaded into S4 Hana Rest Of The World instance)
  • China (Entities in China will be loaded into S4 Hana China instance)  
  • CUI US (Entities in CUI will be handled by US based data consultant)


 The following logic is being used to identify record for SAP ROW Instance. 

  1. Vendor has purchasing organization or company code attributes data in below entities. 
  2. If vendor being used in both ROW entities and others, then General attributes data needs to be created in both SAP ROW and others instances.
SAP ROW Instance Specific Company CodesSAP ROW Instance Specific Purchasing Organization





The following logic is being used to identify record for SAP China Instance. 

  1. Vendor has purchasing organization or company code attributes data in below entities. 
  2. If vendor being used in both China entities and others, then General attributes data needs to be created in both SAP China and other instances.
SAP China Instance Specific Company CodesSAP China Instance Specific Purchasing Organization





The following logic is being used to identify record for SAP CUI Instance. 

  1. Vendor has purchasing organization or company code attributes data in below entities. 
  2. If vendor being used in both CUI entities and others, then General attributes data needs to be created in both SAP CUI and other instances.
SAP CUI Instance Specific Company CodesSAP CUI Instance Specific Purchasing Organization







Target Design

The technical design of the target for this conversion approach. 

TableFieldData ElementField DescriptionData TypeLengthRequirement
BUT000PARTNERPARTNERBusiness PartnerCHAR10Mandatory
BUT000BPKINDBPKINDBP TypeCHAR4Conditional
BUT000BU_GROUPBU_GROUPGroupingCHAR4Mandatory
BUT000BPEXTBPEXTExternal BP NumberCHAR20Mandatory
BUT000BU_SORT1BU_SORT1Search Term 1CHAR20Mandatory
BUT000BU_SORT2BU_SORT2Search Term 2CHAR20Conditional
BUT000CONTACTCONTACTContactCHAR1Conditional
BUT000NAME_ORG1NAME_ORG1Name 1CHAR40Mandatory
BUT000NAME_ORG2NAME_ORG2Name 2CHAR40Conditional
BUT000NATPERSNATPERSNatural PersonCHAR1Conditional
BUT000MILVEMILVEMilitary useCHAR1Conditional
BUT000NUC_SECNUC_SECNuclear SectorCHAR1Conditional
ADRCNATIONNATIONAddress VersionCHAR1Conditional
ADRCNAME1NAME1NameCHAR40Mandatory
ADRCNAME2NAME2Name 2CHAR40Conditional
ADRCNAME3NAME3Name 3CHAR40Conditional
ADRCNAME4NAME4Name 4CHAR40Conditional
ADRCNAME_CONAME_COc/oCHAR40Conditional
ADRCCITY1CITY1CityCHAR40Conditional
ADRCCITY2CITY2DistrictCHAR40Conditional
ADRCPOST_CODE1POST_CODE1Postal CodeCHAR10Conditional
ADRCPOST_CODE2POST_CODE2PO Box Postal CodeCHAR10Conditional
ADRCPOST_CODE3POST_CODE3Company Postal CodeCHAR10Conditional
ADRCPO_BOXPO_BOXPO BoxCHAR10Conditional
ADRCPO_BOX_NUMPO_BOX_NUMPO Box w/o No.CHAR1Conditional
ADRCPO_BOX_LOCPO_BOX_LOCPO Box CityCHAR40Conditional
ADRCPO_BOX_REGPO_BOX_REGPO Box RegionCHAR3Conditional
ADRCPO_BOX_CTYPO_BOX_CTYPO Box Ctry/RegionCHAR3Conditional
ADRCTRANSPZONETRANSPZONETransportation ZoneCHAR10Conditional
ADRCSTREETSTREETStreetCHAR60Conditional
ADRCHOUSE_NUM1HOUSE_NUM1House NumberCHAR10Conditional
ADRCHOUSE_NUM2HOUSE_NUM2SupplementCHAR10Conditional
ADRCSTR_SUPPL1STR_SUPPL1Street 2CHAR40Conditional
ADRCSTR_SUPPL2STR_SUPPL2Street 3CHAR40Conditional
ADRCSTR_SUPPL3STR_SUPPL3Street 4CHAR40Conditional
ADRCLOCATIONLOCATIONStreet 5CHAR40Conditional
ADRCBUILDINGBUILDINGBuilding CodeCHAR20Conditional
ADRCCOUNTRYCOUNTRYCountry/Region KeyCHAR3Mandatory
ADRCLANGULANGULanguage KeyLANG1Mandatory
ADRCREGIONREGIONRegionCHAR3Mandatory
ADRCSORT1SORT1Search Term 1CHAR20Mandatory
ADRCSORT2SORT2Search Term 2CHAR20Conditional
ADRCTEL_NUMBERTEL_NUMBERTelephoneCHAR30Conditional
ADRCTEL_EXTENSTEL_EXTENSExtensionCHAR10Conditional
ADRCFAX_NUMBERFAX_NUMBERFaxCHAR30Conditional
ADRCFAX_EXTENSFAX_EXTENSExtensionCHAR10Conditional
ADRCFLAGCOMM2FLAGCOMM2Telephone...CHAR1Conditional
ADRCFLAGCOMM3FLAGCOMM3Fax...CHAR1Conditional
ADRCFLAGCOMM4FLAGCOMM4TeletexCHAR1Conditional
ADRCFLAGCOMM6FLAGCOMM6E-Mail DefinedCHAR1Conditional
ADRCMC_CITY1MC_CITY1CityCHAR25Conditional
ADRCMC_STREETMC_STREETStreetCHAR25Conditional
ADRCEXTENSION1EXTENSION1Data lineCHAR40Conditional
ADRCEXTENSION2EXTENSION2TeleboxCHAR40Conditional
ADRCTAXJURCODETAXJURCODETax JurisdictionCHAR15Conditional
ADRCPO_BOX_LOBBYPO_BOX_LOBBYPO Box LobbyCHAR40Conditional
BUT0IDTYPETYPEIdentification TypeCHAR6Conditional
BUT0IDIDNUMBERIDNUMBERID NumberCHAR60Conditional
BUT0IDINSTITUTEINSTITUTEResponsible InstitnCHAR40Conditional
BUT0IDENTRY_DATEENTRY_DATEEntry dateDATS8Conditional
BUT0IDVALID_DATE_FROMVALID_DATE_FROMValid fromDATS8Conditional
BUT0IDVALID_DATE_TOVALID_DATE_TOValid ToDATS8Conditional
BUT0IDCOUNTRYCOUNTRYCountry/RegionCHAR3Conditional
BUT0IDREGIONREGIONRegionCHAR3Conditional
DFKKBPTAXNUMPARTNERPARTNERBusiness PartnerCHAR10Conditional
DFKKBPTAXNUMTAXTYPETAXTYPETax Number CategoryCHAR4Conditional
DFKKBPTAXNUMTAXNUMTAXNUMTax numberCHAR20Conditional
ADR2CONSNUMBERCONSNUMBERSequence NumberNUMC3Conditional
ADR2COUNTRYCOUNTRYCountry/RegionCHAR3Conditional
ADR2FLGDEFAULTFLGDEFAULTStandard No.CHAR1Conditional
ADR2FLG_NOUSEFLG_NOUSEDo Not Use Communication NumberCHAR1Conditional
ADR2HOME_FLAGHOME_FLAGHome AddressCHAR1Conditional
ADR2TEL_NUMBERTEL_NUMBERTelephoneCHAR30Conditional
ADR2TEL_EXTENSTEL_EXTENSExtensionCHAR10Conditional
ADR2TELNR_LONGTELNR_LONGTelephone numberCHAR30Conditional
ADR2TELNR_CALLTELNR_CALLCaller numberCHAR30Conditional
ADR2DFT_RECEIVDFT_RECEIVSMS-Enab.CHAR1Conditional
ADR2R3_USERR3_USERMobile phoneCHAR1Conditional
ADR3COUNTRYCOUNTRYCountry/RegionCHAR3Conditional
ADR3FLGDEFAULTFLGDEFAULTStandard No.CHAR1Conditional
ADR3FLG_NOUSEFLG_NOUSEDo Not Use Communication NumberCHAR1Conditional
ADR3HOME_FLAGHOME_FLAGHome AddressCHAR1Conditional
ADR3FAX_NUMBERFAX_NUMBERFaxCHAR30Conditional
ADR3FAX_EXTENSFAX_EXTENSExtensionCHAR10Conditional
ADR3FAXNR_LONGFAXNR_LONGFax NumberCHAR30Conditional
ADR3FAXNR_CALLFAXNR_CALLSender numberCHAR30Conditional
ADR4FLGDEFAULTFLGDEFAULTStandard No.CHAR1Conditional
ADR4FLG_NOUSEFLG_NOUSEDo Not Use Communication NumberCHAR1Conditional
ADR4HOME_FLAGHOME_FLAGHome AddressCHAR1Conditional
ADR4TTX_NUMBERTTX_NUMBERTeletex numberCHAR30Conditional
ADR5FLGDEFAULTFLGDEFAULTStandard No.CHAR1Conditional
ADR5FLG_NOUSEFLG_NOUSEDo Not Use Communication NumberCHAR1Conditional
ADR5HOME_FLAGHOME_FLAGHome AddressCHAR1Conditional
ADR5TLX_NUMBERTLX_NUMBERTelex numberCHAR30Conditional
ADR6FLGDEFAULTFLGDEFAULTStandard addr.CHAR1Conditional
ADR6FLG_NOUSEFLG_NOUSEDo Not Use Communication NumberCHAR1Conditional
ADR6HOME_FLAGHOME_FLAGHome AddressCHAR1Conditional
ADR6SMTP_ADDRSMTP_ADDRE-Mail AddressCHAR241Conditional
ADR6SMTP_SRCHSMTP_SRCHE-Mail AddressCHAR20Conditional
BUT0BKPARTNERPARTNERBusiness PartnerCHAR10Conditional
BUT0BKBKVIDBKVIDBank Details IDCHAR4Conditional
BUT0BKBANKSBANKSBank Country/RegionCHAR3Conditional
BUT0BKBANKLBANKLBank KeyCHAR15Conditional
BUT0BKBANKNBANKNBank acctCHAR18Conditional
BUT0BKBKONTBKONTBank Control KeyCHAR2Conditional
BUT0BKBKREFBKREFReference DetailsCHAR20Conditional
BUT0BKKOINHKOINHAccount HolderCHAR60Conditional
BUT0BKBKEXTBKEXTExtern.bank dtls IDCHAR20Conditional
BUT0BKXEZERXEZERCollection authorizationCHAR1Conditional
BUT0BKACCNAMEACCNAMEAccount NameCHAR40Conditional
BUT0BKMOVE_BKVIDMOVE_BKVIDTarget Bank DetailsCHAR4Conditional
BUT0BKPROTECTPROTECTSensitivityCHAR1Conditional
BUT0BKALIAS_IS_USEDALIAS_IS_USEDAlias Is UsedCHAR1Conditional
BUT0BKBK_VALID_FROMBK_VALID_FROMValid FromDEC15Conditional
BUT0BKBK_VALID_TOBK_VALID_TOValid ToDEC15Conditional
BUT0BKBK_MOVE_DATEBK_MOVE_DATEDate of ChangeDEC15Conditional
BUT0BKIBANIBANIBANCHAR34Conditional
BUT0BKACCOUNT_IDACCOUNT_IDBank Account NumberCHAR35Conditional
BUT0BKCHECK_DIGITCHECK_DIGITBank Account Check DigitCHAR2Conditional
BUT0BKACCOUNT_TYPEACCOUNT_TYPEBank Account TypeCHAR3Conditional
BUT0BKBP_EEW_BUT0BK

BP_EEW_BUT0BK


CHAR1Conditional
BUT100RLTYPRLTYPBP RoleCHAR6Mandatory


Data Cleansing

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

Customer Master Data - General Information

IDCriticalityError Message/Report DescriptionRuleOutputSource System
3007-C01C-1Block customer general data without any usage for more than 2 years

If customer is created for more than 2 years

For customer without Central Deletion Flag and customer is not used in any sales or finance transaction for more than 2 years 


If customer is created for less than 2 years

For customer without Central Deletion Flag and customer is not used in any sales or finance transaction for more than X months



Customer/Name/Country/Last Transaction Date


Below source document will be considered to get the last transaction date

  1. Accounting document (Select MAX(BKPF-BUDAT) where BSEG-KUNNR =KNA1-KUNNR and BKPF-BUKRS = BSEG-BUKRS AND BKPF-BELNR = BSEG-BUKRS AND BKPF-GJAHR =BSEG-BUKRS )
  2. Sales Document (Select MAX(VBAK-ERDAT) WHERE VBAK-VBELN=VBPA-VBELN AND VBPA-KUNNR = KNA1-KUNNR)
  3. Delivery Document (Select MAX(LIKP-ERDAT) WHERE LIKP-VBELN=VBPA-VBELN AND VBPA-KUNNR = KNA1-KUNNR)
  4. Billing   (Select MAX(VBRK-ERDAT) WHERE VBRK-VBELN=VBPA-VBELN AND VBPA-KUNNR = KNA1-KUNNR)
PF2/WP2
3007-C02C-2Missing Postal code in the general dataActive customer in scope and there is no postal code maintained except for HKCustomer/Name/Country/Postal CodePF2/WP2
3007-C03C-2Missing Street in the general dataActive customer in scope and there is no street information in either Street/2/3/4/5Customer/Name/Country/Street/Street2/Street3/Street4/Street5PF2/WP2
3007-C04C-2Missing Region in the general dataActive customer in scope and there is no region code maintainedCustomer/Name/Country/City/Region codePF2/WP2
3007-C05C-2Review the international version address maintained for the customerActive customer in scope and there is international address maintained. In the meantime, the international version content doesn't match the international versionCustomer/Name/International version/International version Name 1/International version Name 2/International version Street/International version Street2PF2/WP2
3007-C06
Review the customer with obsolete region codeActive customer in scope and the region code is no longer valid, i.e., the region code includes description such as D* / Obs / OBLASTCustomer/Name/Country/City/Region code/ECC descriptionPF2/WP2
3007-C07C1Identify duplicate BP
1. customer vs customer

Active customer in scope and meet below 2 conditions

  1. Tax registration number is same
  2. The name/street/country/region/bank information similarity is above the threshold
Customer/Name/Country/Street/Street2/Street3/Street4/Street5/Tax ID/Bank InfoPF2/WP2
3007-C08C1Identify duplicate BP
2. vendor vs customer if applicable

Active customer/vendor in scope and meet below 2 conditions

  1. Tax registration number is same
  2. The name/street/country/region/bank information similarity is above the threshold
Customer/Name/Country/Street/Street2/Street3/Street4/Street5/Tax ID/Bank InfoPF2/WP2
3007-C09C2Missing customer without transportation zone

Active customer in scope and there is no transportation zone

Customer/Name/Street/Country/Region/Transportation ZonePF2/WP2
3007-C10C3Review customer using name 3 and name 4 and re-organize the name if possible?

Active customer in scope, and there is information maintained in name 3 or name 4

Customer/Name/Name2/Name3/Name4/CountryPF2/WP2
3007-C11C3Move C/O to field C/O instead of keeping in Name1/2/3/4

Active customer in scope and there is "C/O" maintained in name 1/2/3/4

Customer/Name/Name2/Name3/Name4PF2/WP2
3007-C12C3Remove room number as the field is no longer in use

Active customer in scope and there is room number

Customer/Name/Country/Street/Street2/Street3/Street4/room numberPF2/WP2
3007-C13C2Identify one customer has multiple VAT ID in different registration country

If the customer has multiple VAT ID, identify if this is for different country and if there is different VAT registration address, if yes, then need to split the customer into multiple ship-to in S4

Customer/Name/Street/Country/Region/VAT ID(STCEG)/Tax Number 1(STCD1)/Tax Number 2(STCD2)/Tax Number 3(STCD3)/Tax Number 4(STCD4)/Tax Number 5(STCD5)/Tax Number 6(STCD6)PF2/WP2
3007-C14C2Customers with identical VAT ID

After de-duplication, there are several customers share the identical VAT ID

Customer/Name/Street/Country/Region/VAT ID(STCEG)/Tax Number 1(STCD1)/Tax Number 2(STCD2)/Tax Number 3(STCD3)/Tax Number 4(STCD4)/Tax Number 5(STCD5)/Tax Number 6(STCD6)PF2/WP2
3007-C14C3Salesforce customer not in SAP

iCare/Core CRM customer in migration scope, but there is no data in WP2/PF2

Account ID / Name / Account Manager / PRS/RCS IDiCare/Core


Vendor Master Data - General Information


IDCriticalityError Message/Report DescriptionRuleOutputSource System

3007-001

C2

Vendor General Bank - Missing/Incorrect bank details

1) Vendors with missing bank account, IBAN.

2) Bank account numbers and IBANs must be in the correct format. For countries outside the EU, the appropriate format must be validated.


3) SWIFT/BIC codes must be present and valid to ensure proper international transactions. 


DCT report to highlight missing bank details such as :-

Vendor, Name, Country, Description, Region, Comment, Baseline

PF2/WP2

3007-002

C2

Deduplication

Vendors with same name, VAT ID, bank details, etc., should be unified to avoid redundant BP creation.


Criteria:

  • Same or similar name
  • Same or similar address, phone number, city.
  • VAT/TAX registration number (where applicable) 
  • Bank Country, Bank Key and Bank Account 
  • DUNS number

DCT for business to select golden record using parent and child approach .

BP - Vendor Dedup Header List

  • Vendor with Same Name
  • No of Count with same name
  • Review Status (Traffic Light)

BP- Vendor Dedup Item List

  • Record Id
  • Source System
  • Vendor
  • Name
  • Name 2
  • Street
  • City
  • Country
  • Golden BP (checkbox)
  • Account Group
  • DUNS 
  • Reviewed (checkbox)
  • Changed By
  • Changed On


PF2/WP2

3007-003C2Missing VAT Number / Tax Number

1) VAT numbers, tax codes, and tax jurisdictions must be valid and correctly formatted


2) International vendors must comply with tax rules of their respective countries


3) Generally all records should have at least one of the fields VAT numbers, tax codes, and tax jurisdictions, CNPJ updated


4) International vendors must comply with tax rules of their respective countries

DCT report to highlight missing VAT number and format that not correctPF2/WP2
3007-004C2Vendor Address Check and Standardization

1) (Street) must be populated

2) (City) must be populated

3) Telephone Number must be numeric

4) Ensure the Postcode is populated and follow the structure expected for the respective country

DCT report to highlight vendor address not in right formatPF2/WP2
3007-005C2

Missing Emails

Vendors with missing emails.DCT report to highlight missing emailsPF2/WP2
3007-006C2Vendor - Marked for Deletion (Reduce Scope)

1) if Central Posting Block (LFA1-SPERR) = X or
2) if Central imposed purchasing Block (LFA1-SPERM) = X or
3) if Central Archiving Flag (BUT000-XDELE) = X or
4) if Central Block for Business Partner (BUT000-XBLCK) = X or
5) LFA1-SPERQ - 'Block Function' is = code 99 (total block)
6) LFA1-ZZR_ZLATR8 - 'ZBY' Unauthorized Vendor or 'ZVN' Obsolete vendor - not used / Duplicate / VAT changed 
7) if (LFB1-SPERR and LFB1-LOEVM) = X  - For Specific Company Code
8) if (LFM1-SPERM and LFM1-LOEVM) = X - For Specific Purchasing Organization

DCT report to reduce scopePF2/WP2
3007-007C2Relevancy report

Create vendor report with all LFA1 fields relevancy flags from Vendor Relevancy plus the additional flags below:

  1. zActive_PO_Spares - If Vendor is present in EKKO table where EKKO-BSTYP=F and EKKO-LOEKZ <> X and EKKO-AEDAT in last 5 years (within in scope – Company Code, PurchOrg) and PO has item in EKPO (within in-scope plant) then this flag is set to 1 and material is an indirect material where EKPO-MATNR found in MARA and MARA-MTART identified in the link sheet below as ZIND under the Material Types Definition tab.

  2. zActive_AP_Cleared - where Vendor has an entry in BSAK-LIFNR in the last 7 years (within legal company code in scope)

  3. zReturn_Vendor - where LFM1-KZRET=X

Info report for relevancy analysisPF2/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. The extracted data is then staged for transformation.

It will extract the customer and vendor master data related table, such as KNA1/LFA1/KNVV/KNB1/LFB1/LFM1/ADRC/ADR2/ADR3/ADR4/ADR5/ADR6 etc.


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. SAP Migration cockpit will be used to migrate the Customer/Supplier separately. If the Business partner is customer and vendor in the same time, the BP general information will be in the Customer loading file.




Data Privacy and Sensitivity

N/A


Extraction

Extract data from a source into Syniti Migrate for SAP ROW and SAP China relevant entities. 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
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.


Major tables to be extracted are  KNA1/LFA1/KNVV/KNB1/LFB1/LFM1/ADRC/ADR2/ADR3/ADR4/ADR5/ADR6.

Syniti / LTC Data team

Extraction Methodology

- Specify the extraction approach (full, incremental, or delta extraction). For this object, it will be full extraction.
- Determine the tools and technologies used.
- Define data filtering criteria to exclude irrelevant records.

Syniti
Extraction Execution Plan- Establish execution timelines and batch processing schedules.
- Assign responsibilities for extraction monitoring.
- Document dependencies on other migration tasks.		Syniti
Data Quality and Validation- Define error handling mechanisms for extraction failures.Syniti




Selection Screen

Selection Ref ScreenParameter NameSelection TypeRequirementValue to be entered/set
N/A



















Data Collection Template (DCT)

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

BP General DCT Rules


Customer Master Data - General Information

Field NameField DescriptionRule
Follow Migration cockpit template layout for Customer










 Vendor Master Data - General Information

Field NameField DescriptionRule













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


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
1Identify target S/4HANA fields and determine applicable legacy source fields from both ECC systems WP2, PF2Functional Team (L2C/S2P)+ Data Team (L2C/S2P)
2Map legacy field values to S/4HANA target values (including field-level mapping and technical names)Data Team (L2C/S2P), Data Team (Syniti)
3Define value mapping rules for fields requiring standardization or harmonization across the two source systems WP2, PF2 Functional Team (L2C/S2P)+ Data Team (L2C/S2P)
4Identify and agree on default values where legacy data is incomplete or inconsistentBusiness Team + Functional Team (L2C/S2P)
5Configure transformation rules in Syniti Migrate 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), Data Load Team


Transformation Rules


Customer Master Data Transformation Rule


Rule #Source systemSource TableSource FieldSource DescriptionTarget SystemTarget TableTarget FieldTarget DescriptionTransformation Logic
1WQ2/PF2KNA1KUNNR
S4 HanaBUT000PARTNERBusiness Partner

Rule - For External BP
Apply external number range from 1000000 to 99999999, use the running number from 1000000
For Intercompany BP, it will be DCT, the numbering will be as following
Legal entity will be ICT/ICN+S4 Company Code
Plant will be PL+S4 Plant code

2WQ2/PF2


S4 HanaBUT000BPKINDBP TypeTBD -
3WQ2/PF2


S4 HanaBUT000BU_GROUPGroupingRule - For External BP - Apply BP02
For Intercompany BP - Apply BPAB
4WQ2/PF2KNA1KUNNR
S4 HanaBUT000BPEXTExternal BP Number

Rule - if it is single, just copy legacy customer or vendor number.
if there are multiples legacy number, use '/' to combine customer/vendor number

5WQ2/PF2ADRCSORT1
S4 HanaBUT000BU_SORT1Search Term 1Copy -
6WQ2/PF2ADRCSORT2
S4 HanaBUT000BU_SORT2Search Term 2Copy -
7WQ2/PF2


S4 HanaBUT000CONTACTContactNot in Use -
8WQ2/PF2ADRCNAME1
S4 HanaBUT000NAME_ORG1Name 1Copy -
9WQ2/PF2ADRCNAME2
S4 HanaBUT000NAME_ORG2Name 2Copy -
10WQ2/PF2KNA1STKZN
S4 HanaBUT000NATPERSNatural PersonCopy - KNA1-STKZN
11WQ2/PF2KNA1MILVE
S4 HanaBUT000MILVEMilitary useCopy - KNA1-MILVE
12WQ2/PF2KNA1CCC02
S4 HanaBUT000NUC_SECNuclear SectorCopy - KNA1-CCC02
13WQ2/PF2


S4 HanaADRCNATIONAddress Version

Rule - Following address version will be used
C - Simplified Chinese
M - Traditional Chinese.
Copy C/M only, rest of the version will not be migrated

14WQ2/PF2ADRCNAME1
S4 HanaADRCNAME1NameCopy
15WQ2/PF2ADRCNAME2
S4 HanaADRCNAME2Name 2Copy
16WQ2/PF2ADRCNAME3
S4 HanaADRCNAME3Name 3Not in Use
17WQ2/PF2ADRCNAME4
S4 HanaADRCNAME4Name 4Not in Use
18WQ2/PF2ADRCNAME_CO
S4 HanaADRCNAME_COc/oCopy
19WQ2/PF2ADRCCITY1
S4 HanaADRCCITY1CityCopy
20WQ2/PF2ADRCCITY2
S4 HanaADRCCITY2DistrictCopy
21WQ2/PF2ADRCPOST_CODE1
S4 HanaADRCPOST_CODE1Postal CodeCopy
22WQ2/PF2ADRCPOST_CODE2
S4 HanaADRCPOST_CODE2PO Box Postal CodeCopy
23WQ2/PF2ADRCPOST_CODE3
S4 HanaADRCPOST_CODE3Company Postal CodeCopy
24WQ2/PF2ADRCPO_BOX
S4 HanaADRCPO_BOXPO BoxCopy
25WQ2/PF2ADRCPO_BOX_NUM
S4 HanaADRCPO_BOX_NUMPO Box w/o No.Copy
26WQ2/PF2ADRCPO_BOX_LOC
S4 HanaADRCPO_BOX_LOCPO Box CityCopy
27WQ2/PF2ADRCPO_BOX_REG
S4 HanaADRCPO_BOX_REGPO Box RegionCopy
28WQ2/PF2ADRCPO_BOX_CTY
S4 HanaADRCPO_BOX_CTYPO Box Ctry/RegionCopy
29WQ2/PF2


S4 HanaADRCTRANSPZONETransportation ZoneRule - This is based on TM's rule
30WQ2/PF2ADRCSTREET
S4 HanaADRCSTREETStreetCopy
31WQ2/PF2ADRCHOUSE_NUM1
S4 HanaADRCHOUSE_NUM1House NumberCopy
32WQ2/PF2ADRCHOUSE_NUM2
S4 HanaADRCHOUSE_NUM2SupplementCopy
33WQ2/PF2ADRCSTR_SUPPL1
S4 HanaADRCSTR_SUPPL1Street 2Copy
34WQ2/PF2ADRCSTR_SUPPL2
S4 HanaADRCSTR_SUPPL2Street 3Copy
35WQ2/PF2ADRCSTR_SUPPL3
S4 HanaADRCSTR_SUPPL3Street 4Copy
36WQ2/PF2ADRCLOCATION
S4 HanaADRCLOCATIONStreet 5Copy
37WQ2/PF2ADRCBUILDING
S4 HanaADRCBUILDINGBuilding CodeCopy
38WQ2/PF2ADRCCOUNTRY
S4 HanaADRCCOUNTRYCountry/Region KeyCopy
39WQ2/PF2ADRCLANGU
S4 HanaADRCLANGULanguage KeyCopy
40WQ2/PF2


S4 HanaADRCREGIONRegion

Mapping - Refer to mapping table MAP_REGION. Based on ADRC-COUNTRY/REGION to map the S4 Hana region code

41WQ2/PF2ADRCSORT1
S4 HanaADRCSORT1Search Term 1Copy
42WQ2/PF2ADRCSORT2
S4 HanaADRCSORT2Search Term 2Copy
43WQ2/PF2ADRCTEL_NUMBER
S4 HanaADRCTEL_NUMBERTelephoneCopy
44WQ2/PF2ADRCTEL_EXTENS
S4 HanaADRCTEL_EXTENSExtensionCopy
45WQ2/PF2ADRCFAX_NUMBER
S4 HanaADRCFAX_NUMBERFaxCopy
46WQ2/PF2ADRCFAX_EXTENS
S4 HanaADRCFAX_EXTENSExtensionCopy
47WQ2/PF2ADRCFLAGCOMM2
S4 HanaADRCFLAGCOMM2Telephone...Copy
48WQ2/PF2ADRCFLAGCOMM3
S4 HanaADRCFLAGCOMM3Fax...Copy
49WQ2/PF2ADRCFLAGCOMM4
S4 HanaADRCFLAGCOMM4TeletexCopy
50WQ2/PF2ADRCFLAGCOMM6
S4 HanaADRCFLAGCOMM6E-Mail DefinedCopy
51WQ2/PF2ADRCMC_CITY1
S4 HanaADRCMC_CITY1CityCopy
52WQ2/PF2ADRCMC_STREET
S4 HanaADRCMC_STREETStreetCopy
53WQ2/PF2ADRCEXTENSION1
S4 HanaADRCEXTENSION1Data lineCopy
54WQ2/PF2ADRCEXTENSION2
S4 HanaADRCEXTENSION2TeleboxCopy
55WQ2/PF2ADRCTAXJURCODE
S4 HanaADRCTAXJURCODETax JurisdictionCopy
56WQ2/PF2ADRCPO_BOX_LOBBY
S4 HanaADRCPO_BOX_LOBBYPO Box LobbyCopy
57WQ2/PF2STXHTDOBJECT
S4 HanaSTXHTDOBJECTText objectCopy -
58WQ2/PF2


S4 HanaSTXHTDNAMEText Name-
59WQ2/PF2


S4 HanaSTXHTDIDText ID-
60WQ2/PF2STXHTDSPRAS
S4 HanaSTXHTDSPRASLanguage KeyCopy -
61WQ2/PF2


S4 HanaSTXLRELID
-
62WQ2/PF2STXLTDOBJECT
S4 HanaSTXLTDOBJECTText objectCopy -
63WQ2/PF2


S4 HanaSTXLTDNAMEText NameMapping -
64WQ2/PF2


S4 HanaSTXLTDIDText ID-
65WQ2/PF2STXLTDSPRAS
S4 HanaSTXLTDSPRASLanguage KeyCopy -
66WQ2/PF2STXLCLUSTD
S4 HanaSTXLCLUSTDDataCopy -
67WQ2/PF2


S4 HanaBUT0IDTYPEIdentification Type

Rule - if follow fields are not blank, map to below ID

KNA1-ZZR_DUNS_DIRECT DUNS direct code - Map to ID BUP001
KNA1-ZZR_DUNS_PARENT DUNS HQ/Parent - Map to ID BUP001
KNA1-ZZR_DUNS_ULT_DOM DUNS domestic ultimate - Map to ID BUP001
KNA1-ZZR_DUNS_ULTIMAT DUNS global ultimate - Map to ID BUP001

68WQ2/PF2


S4 HanaBUT0IDIDNUMBERID Number

Rule - if follow fields are not blank, copy the value

KNA1-ZZR_DUNS_DIRECT DUNS direct code - Map to ID BUP001
KNA1-ZZR_DUNS_PARENT DUNS HQ/Parent - Map to ID BUP001
KNA1-ZZR_DUNS_ULT_DOM DUNS domestic ultimate - Map to ID BUP001
KNA1-ZZR_DUNS_ULTIMAT DUNS global ultimate - Map to ID BUP001

69WQ2/PF2


S4 HanaBUT0IDINSTITUTEResponsible InstitnNot in Use -
70WQ2/PF2


S4 HanaBUT0IDENTRY_DATEEntry dateNot in Use -
71WQ2/PF2


S4 HanaBUT0IDVALID_DATE_FROMValid fromNot in Use -
72WQ2/PF2


S4 HanaBUT0IDVALID_DATE_TOValid ToNot in Use -
73WQ2/PF2


S4 HanaBUT0IDCOUNTRYCountry/RegionNot in Use -
74WQ2/PF2


S4 HanaBUT0IDREGIONRegionNot in Use -
75WQ2/PF2


S4 HanaDFKKBPTAXNUMPARTNERBusiness Partner

Rule - For External BP
Apply external number range from 1000000 to 99999999, use the running number from 1000000
For Intercompany BP
Legal entity will be ICT/ICN+S4 Company Code
Plant will be PL+S4 Plant code

76WQ2/PF2


S4 HanaDFKKBPTAXNUMTAXTYPETax Number Category

Rule - Refer to MAP_TAXTYPE. Based on KNA1-LAND to map the tax number categories

77WQ2/PF2KNA1

STCEG/STCD1/STCD2/STCD3/STCD4/STCD5


S4 HanaDFKKBPTAXNUMTAXNUMTax number

Rule - Refer to MAP_TAXTYPE. Based on KNA1-LAND to map the tax number categories, then copy the value for each category

78WQ2/PF2ADR2CONSNUMBER
S4 HanaADR2CONSNUMBERSequence NumberCopy -
79WQ2/PF2ADR2COUNTRY
S4 HanaADR2COUNTRYCountry/RegionCopy -
80WQ2/PF2ADR2FLGDEFAULT
S4 HanaADR2FLGDEFAULTStandard No.Copy -
81WQ2/PF2ADR2FLG_NOUSE
S4 HanaADR2FLG_NOUSEDo Not Use Communication NumberCopy -
82WQ2/PF2ADR2HOME_FLAG
S4 HanaADR2HOME_FLAGHome AddressCopy -
83WQ2/PF2ADR2TEL_NUMBER
S4 HanaADR2TEL_NUMBERTelephoneCopy -
84WQ2/PF2ADR2TEL_EXTENS
S4 HanaADR2TEL_EXTENSExtensionCopy -
85WQ2/PF2ADR2TELNR_LONG
S4 HanaADR2TELNR_LONGTelephone numberCopy -
86WQ2/PF2ADR2TELNR_CALL
S4 HanaADR2TELNR_CALLCaller numberCopy -
87WQ2/PF2ADR2DFT_RECEIV
S4 HanaADR2DFT_RECEIVSMS-Enab.Copy -
88WQ2/PF2ADR2R3_USER
S4 HanaADR2R3_USERMobile phoneCopy -
89WQ2/PF2ADR3COUNTRY
S4 HanaADR3COUNTRYCountry/RegionCopy -
90WQ2/PF2ADR3FLGDEFAULT
S4 HanaADR3FLGDEFAULTStandard No.Copy -
91WQ2/PF2ADR3FLG_NOUSE
S4 HanaADR3FLG_NOUSEDo Not Use Communication NumberCopy -
92WQ2/PF2ADR3HOME_FLAG
S4 HanaADR3HOME_FLAGHome AddressCopy -
93WQ2/PF2ADR3FAX_NUMBER
S4 HanaADR3FAX_NUMBERFaxCopy -
94WQ2/PF2ADR3FAX_EXTENS
S4 HanaADR3FAX_EXTENSExtensionCopy -
95WQ2/PF2ADR3FAXNR_LONG
S4 HanaADR3FAXNR_LONGFax NumberCopy -
96WQ2/PF2ADR3FAXNR_CALL
S4 HanaADR3FAXNR_CALLSender numberCopy -
97WQ2/PF2ADR4FLGDEFAULT
S4 HanaADR4FLGDEFAULTStandard No.Copy -
98WQ2/PF2ADR4FLG_NOUSE
S4 HanaADR4FLG_NOUSEDo Not Use Communication NumberCopy -
99WQ2/PF2ADR4HOME_FLAG
S4 HanaADR4HOME_FLAGHome AddressCopy -
100WQ2/PF2ADR4TTX_NUMBER
S4 HanaADR4TTX_NUMBERTeletex numberCopy -
101WQ2/PF2ADR5FLGDEFAULT
S4 HanaADR5FLGDEFAULTStandard No.Copy -
102WQ2/PF2ADR5FLG_NOUSE
S4 HanaADR5FLG_NOUSEDo Not Use Communication NumberCopy -
103WQ2/PF2ADR5HOME_FLAG
S4 HanaADR5HOME_FLAGHome AddressCopy -
104WQ2/PF2ADR5TLX_NUMBER
S4 HanaADR5TLX_NUMBERTelex numberCopy -
105WQ2/PF2ADR6FLGDEFAULT
S4 HanaADR6FLGDEFAULTStandard addr.Copy -
106WQ2/PF2ADR6FLG_NOUSE
S4 HanaADR6FLG_NOUSEDo Not Use Communication NumberCopy -
107WQ2/PF2ADR6HOME_FLAG
S4 HanaADR6HOME_FLAGHome AddressCopy -
108WQ2/PF2ADR6SMTP_ADDR
S4 HanaADR6SMTP_ADDRE-Mail AddressCopy -
109WQ2/PF2ADR6SMTP_SRCH
S4 HanaADR6SMTP_SRCHE-Mail AddressCopy -
110WQ2/PF2KNBKKUNNR
S4 HanaBUT0BKPARTNERBusiness Partner

Rule - For External BP
Apply external number range from 1000000 to 99999999, use the running number from 1000000
For Intercompany BP
Legal entity will be ICT/ICN+S4 Company Code
Plant will be PL+S4 Plant code

111WQ2/PF2


S4 HanaBUT0BKBKVIDBank Details IDInternal -
112WQ2/PF2KNBKBANKS
S4 HanaBUT0BKBANKSBank Country/RegionCopy -
113WQ2/PF2KNBKBANKL
S4 HanaBUT0BKBANKLBank KeyMapping -
114WQ2/PF2KNBKBANKN
S4 HanaBUT0BKBANKNBank acctCopy -
115WQ2/PF2KNBKBKONT
S4 HanaBUT0BKBKONTBank Control KeyCopy -
116WQ2/PF2KNBKBKREF
S4 HanaBUT0BKBKREFReference DetailsCopy -
117WQ2/PF2KNBKKOINH
S4 HanaBUT0BKKOINHAccount HolderCopy -
118WQ2/PF2


S4 HanaBUT0BKBKEXTExtern.bank dtls IDNot in Use -
119WQ2/PF2


S4 HanaBUT0BKXEZERCollection authorizationNot in Use -
120WQ2/PF2


S4 HanaBUT0BKACCNAMEAccount NameNot in Use -
121WQ2/PF2


S4 HanaBUT0BKMOVE_BKVIDTarget Bank DetailsNot in Use -
122WQ2/PF2


S4 HanaBUT0BKPROTECTSensitivityNot in Use -
123WQ2/PF2


S4 HanaBUT0BKALIAS_IS_USEDAlias Is UsedNot in Use -
124WQ2/PF2KNBKKOVON
S4 HanaBUT0BKBK_VALID_FROMValid FromCopy -
125WQ2/PF2KNBKKOBIS
S4 HanaBUT0BKBK_VALID_TOValid ToCopy -
126WQ2/PF2


S4 HanaBUT0BKBK_MOVE_DATEDate of ChangeInternal -
127WQ2/PF2


S4 HanaBUT0BKIBANIBANNot in Use -
128WQ2/PF2


S4 HanaBUT0BKACCOUNT_IDBank Account NumberNot in Use -
129WQ2/PF2


S4 HanaBUT0BKCHECK_DIGITBank Account Check DigitNot in Use -
130WQ2/PF2


S4 HanaBUT0BKACCOUNT_TYPEBank Account TypeNot in Use -
131WQ2/PF2


S4 HanaBUT0BK

BP_EEW_BUT0BK


Not in Use -
132WQ2/PF2KNA1AUFSD
S4 HanaKNA1AUFSDCentral order blockCopy -
133WQ2/PF2KNA1FAKSD
S4 HanaKNA1FAKSDCentral billing block-
134WQ2/PF2KNA1KTOKD
S4 HanaKNA1KTOKDAccount group

Mapping - refer to mapping table MAP_KTOKD

135WQ2/PF2KNA1LIFNR
S4 HanaKNA1LIFNRVendor

Mapping - apply BP Supplier vs ECC vendor mapping

136WQ2/PF2KNA1LIFSD
S4 HanaKNA1LIFSDCentral delivery blockCopy -
137WQ2/PF2KNA1LOEVM
S4 HanaKNA1LOEVMCentral deletion flagCopy -
138WQ2/PF2KNA1SPERR
S4 HanaKNA1SPERRCentral posting blockCopy -
139WQ2/PF2KNA1VBUND
S4 HanaKNA1VBUNDTrading partner

Rule - For external customer, this field is not used.
For intercompany customer, it will be via DCT

140WQ2/PF2KNA1WERKS
S4 HanaKNA1WERKSPlantMapping -
141WQ2/PF2KNA1XICMS
S4 HanaKNA1XICMSICMS-exemptCopy -
142WQ2/PF2KNA1XXIPI
S4 HanaKNA1XXIPIIPI-exemptCopy -
143WQ2/PF2KNA1XSUBT
S4 HanaKNA1XSUBTSubTrib groupCopy -
144WQ2/PF2KNA1CFOPC
S4 HanaKNA1CFOPCCust CFOP categoryCopy -
145WQ2/PF2KNA1TXLW1
S4 HanaKNA1TXLW1ICMS textCopy -
146WQ2/PF2KNA1NODEL
S4 HanaKNA1NODELCentral delblockCopy -
147WQ2/PF2KNA1SUFRAMA
S4 HanaKNA1SUFRAMASuframa Code-
148WQ2/PF2KNA1ICMSTAXPAY
S4 HanaKNA1ICMSTAXPAYICMS Taxpayer-
149WQ2/PF2


S4 HanaKNA1DEAR2Indicator: Sales partnerRule - If this is legal entity, it will be X
150WQ2/PF2


S4 HanaBUT100RLTYPBP RoleDefault - FLCU01




























































































































































































































































































Vendor Master Data Transformation Rule



Rule #Source systemSource TableSource FieldSource DescriptionTarget SystemTarget TableTarget FieldTarget DescriptionTransformation Logic
To be updated from the excel file








































As deduplication/consolidation is performed for customer and vendor general data during migration, following fields will have special rule to ensure the complete information is migrated into S4 Hana system.

There will be 3 scenarios. 

a. Multiple customers are merged into 1 customer

b. Multiple vendors are merged into 1 vendor

c. One or several customer and vendor are merged into 1 BP in S4


Rule #Source systemSource TableSource FieldSource DescriptionTarget SystemTarget TableTarget FieldTarget DescriptionTransformation Logic
1WQ2/PF2ADRCAll relevant fields
S4 HanaADRCAll fields
Follow Customer 
2WQ2/PF2ADR2All relevant fieldsTelephone Numbers (Business Address Services)S4 HanaADR2All fields
Merge all the different values
3WQ2/PF2ADR3All relevant fieldsFax Numbers (Business Address Services)S4 HanaADR3All fields
Merge all the different values
4WQ2/PF2ADR4All relevant fieldsTeletex Numbers (Business Address Services)S4 HanaADR4All fields
Merge all the different values
5WQ2/PF2ADR5All relevant fieldsTelex Numbers (Business Address Services)S4 HanaADR5All fields
Merge all the different values
6WQ2/PF2ADR6All relevant fieldsE-Mail Addresses (Business Address Services)S4 HanaADR6All fields
Merge all the different values
7WQ2/PF2KNBK / LFBKAll relevant fieldsCustomer/Vendor Master (Bank Details)S4 HanaBUT0BKAll fields
TBD


 


 



Transformation Mapping

Mapping Table NameMapping Table Description 
MAP_BU_GROUPBP Grouping Mapping Table
MAP_REGIONCountry/Region Code Mapping Table
MAP_BPKINDBP Type Mapping Table


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
Compare Data Counts
  1. Verify row counts between source and target databases.
  2. Identify missing or duplicated records.


Validate the mandatory fieldsValidate there is value for all the mandatory fields
Validate Primary Keys and Unique Constraints
  1. Check for duplicate or missing primary key values, i.e., if there is same BP number.
  2. Ensure unique constraints are maintained.


Test Referential IntegrityConfirm dependent records exist in related tables

Accuracy

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





Business

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

Completeness

TaskAction
Compare Data Counts
  1. Verify row counts between source and target databases.
  2. Identify missing or duplicated records.


Review populated templates for missing or incorrect valuesUse checklists to verify completeness and correctness before submission



Accuracy

TaskAction





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
1Confirm readiness of final approved data sets for each ECC source system WP2 and PF2Business / Functional Team
2Validate transformation rules and mappings in Syniti toolData Team (L2C/S2P-Data)
3Generate target-ready load files based on S/4HANA condition table formatData Team (Syniti)
4Review and approve load files before executionBusiness / Functional Team
5Execute the custom loading program in the S/4HANA system Data Load Team
6Monitor load progress and capture load statistics (records loaded, errors, duplicates, etc.)Data Team (Syniti) / Technical Team
7Extract loaded data from S/4HANA for post-load validationData Team (Syniti)
8Perform post-load data validation (compare target data with source/approved files) for all loaded BP general dataData Team (L2C/S2P-Data)
9Log and resolve any data load errors or mismatches identified during validationData Team (L2C/S2P-Data) + Functional Team
10Obtain business sign-off on successful load and validationBusiness Team
11Archive load logs, error reports, and validation results for audit/complianceData Team (L2C/S2P-Data) / Data Team (Syniti) / PMO


Load Phase and Dependencies

The Business Partner General will be loaded in the pre-cutover period.

Before loading, it will have dependency on the configuration. The configuration needs to be transported into the respective system first, including the manual configuration such as the BP number range set up.

Configuration

Item #Configuration Item
1BP Grouping
2Customer/Vendor Account Group
3International Version
4Tax Category
5BP Type
6BP Number Range/Customer/Vendor Number range

 Conversion Objects

Object #Preceding Object Conversion Approach
1083Bank Master




Error Handling

Error TypeError DescriptionAction Taken
Configuration / Data TransformationThe 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
ConfigurationThere 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
ConfigurationThe BP grouping is External or Internal Number range
  1. Validate the number range set up if this is External or Internal number range


Post-Load Validation

Project Team

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

Completeness

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

Accuracy

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



Business

Post-load validation is a critical step in data migration, ensuring that transferred data is accurate, complete, and functional within the target system.

1. Ensuring Data Integrity
After migration, data must be consistent with its original structure. Post-load validation checks for missing records, incorrect mappings, and formatting errors to prevent discrepancies.
2. Business Continuity
Faulty data can disrupt operations, leading to financial losses and inefficiencies. Validating post-load data ensures that applications function as expected, preventing downtime.
3. Error Detection and Resolution
By validating data post-migration, businesses can detect anomalies early, reducing the cost and effort required for corrections

Completeness

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



Accuracy

TaskAction
Perform Manual TestingConduct manual spot-checks for additional assurance.





Key Assumptions

  • BP Master Data Standard is up to date as on the date of documenting this conversion approach and data load. 
  • BP General (Role 000000) is in scope
  • There will be 3 SAP instances, one for ROW, one for China and one for CUI only.
  • BP General data will be loaded into all 3 SAP instances.




Change log

Version Published Changed By Comment
CURRENT (v. 103) Apr 27, 2026 08:28 CELEDONIO-ext, Arnold
v. 219 Apr 24, 2026 15:27 RUAN-ext, Eric *20260424 update remove the redundant relevancy rule
v. 218 Apr 21, 2026 13:36 CELEDONIO-ext, Arnold Update Vendor mapping rules
v. 217 Apr 20, 2026 14:01 RUAN-ext, Eric 20260420 update for but100 to remove source and add ADR table without selecting the person records
v. 216 Apr 06, 2026 10:14 CELEDONIO-ext, Arnold
v. 215 Apr 02, 2026 14:51 RUAN-ext, Eric
v. 214 Mar 31, 2026 16:16 RUAN-ext, Eric
v. 213 Mar 30, 2026 10:35 CELEDONIO-ext, Arnold
v. 212 Mar 30, 2026 10:23 CELEDONIO-ext, Arnold
v. 211 Mar 26, 2026 14:24 RUAN-ext, Eric

Go to Page History

Workflow history

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

  • No labels