Status

Owner

CHAN-ext, Beng Chee MADHOK-ext, Jasleen 

StakeholdersThe business stakeholders involved in making, reviewing, and endorsing this decision. Type @ to mention people by name

Purpose

The purpose of the document is to define the data conversion approach to create Business Partners – 3rd Party Suppliers through FLVN01 Supplier Role including partner function/bank/tax view in S/4 HANA.


Conversion Scope

The scope of this document covers the approach for converting active Vendor Master purchasing attributes records from Legacy Source Systems into Business Partner – Supplier Role FLVN001 in S/4 HANA following the Vendor Master Data Design Standard.

The data from legacy system includes:

  1. Vendors’ relevant purchasing data with potential duplicate records
  2. Vendors’ relevant purchasing data with potential missing information such as partner function, bank, tax, etc related fields

The data from legacy system excludes:

  1. Vendors blocked or marked for deletion.
  2. Purchasing organization not in scope
  3. 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

PF1, WP1

Supplier role is applicable only for legally registered entities and strictly adheres to Master Data Standards (MDS) which elaborates out these criteria and other requirements such as Partner Function, Bank and Tax details being mandatory information used across Business Partner. 

Identified relevant suppliers from the Global level relevancy. Relevant suppliers with valid purchasing organization extensions in source systems will be in-scope for deduplication analysis.

Deduplication exercise will check duplicates at purchasing organization level and business will choose the source of supplier role attributes to be used for migration. Otherwise, if record has no duplicates, it automatically becomes the source for supplier master data transformation.

(for further relevancy scope, refer to Business Partner – General DCS)

40,000

S/4 HANA

40,000

Additional Information

Multi-language Requirement

Will follow multi-language allowed and created in Business Partner - General.

Document Management

N/A

Legal Requirement

N/A

Special Requirements

TBD


Target Design

The Business Partner - Supplier master data strictly adheres to Master Data Standards as specified below.

The technical design of the target for this conversion approach.

TableFieldData ElementField DescriptionData TypeLengthRequirement

LFM1

LIFNR


SUPPLIER NUMBER

CHAR18

R

LFM1

EKORG


PURCHASING ORGANISATION



R

LFM1

EKGRP


PURCHASING GROUP



O

LFM1

WAERS


ORDER CURRENCY



C

LFM1

VERKF


SALESPERSON



O

LFM1

TELF1


TELEPHONE



O

LFM1

MINBW


MINIMUM ORDER VALUE



O

LFM1

ZTERM


PAYMENT TERMS



C

LFM1

INCOV


INCO VERSION



O

LFM1

INCO1


INCOTERMS



C

LFM1

INCO2_L


INCOTERMS LOCATION 1



O

LFM1

INCO3_L


INCOTERMS LOCATION 2



O

LFM1

KALSK


SCHEMA GROUP SUPPLIER



O

LFM1

PLIFZ


PLANNED DELIVERY TIME



O

LFM1

LFABC


ABC INDICATOR



O

LFM1

VSBED


SHIPPING CONDITIONS



C

LFM1

WEBRE


GR-BASED INVOICE VERIFICATION



C

LFM1

KZAUT


AUTOMATIC PURCHASE ORDER



O

LFM1

MEPRF


PRICING DATE CONTROL



O

LFM1

BSTAE


CONFIRMATION CONTROL KEY



O

LFM1

KZRET


RETURNS SUPPLIER



O

LFM1

AUBEL


AUTOMATIC DEBIT



O

LFM1

VALID_PRO


SETTLEMENT PROFILE



O

LFM1

HSCABS


ABSOLUTE HANDLING SURCHARGE



O

LFM1

HSCPE


PERCENTAGE HANDLING SURCHARGE



O

LFM1

HSCMIN


MINIMUM HANDLING SURCHARGE



O

LFM1

HSCMAX


MAXIMUM HANDLING SURCHARGE



O

LFM1

XERSY


AUTOM EVALUATED RECEIPT SETTLEMENT (ERS)



C

LFM1

XERSR


AUTOM EVALUATED GR SETTLEMENT RETURN



C

LFM1

KZABS


ORDER ACKNOWLEDGMENT REQUIREMENT



C

WYT3

LIFNR


SUPPLIER



R

WYT3

EKORG


PURCHASING ORG



R

WYT3

PARVW


PARTNER FUNCTION



R

WYT3

LIFN2


REF TO VENDOR



C

WYT3

PERNR


PERSONAL NO



O

WYT3

PARNR


CONTACT PERSON



O

WYT3

DEFPA


DEFAULT PARTNER



O

Function - READ_TEXT (STHX header table)

LIFNR

SUPPLIER



R

Function - READ_TEXT (STHX header table)

EKORG

PURCHASING ORGANIZATION



R

Function - READ_TEXT (STHX header table)

TDID

TEXT ID



R

Function - READ_TEXT (STHX header table)

TEXT_TDSPRAS

LANGUAGE KEY



R

Function - READ_TEXT (STHX header table)

TEXT_LINES

TEXT



R

ADRC_NATION LENG (IAV)

LIFNR

SUPPLIER



R

ADRC_NATION LENG (IAV)

PARNR

CONTACT ID



R

ADRC_NATION



Version ID for International Addresses



R

ADRC_NATION LENG (IAV)

VNAME

FIRST NAME



O

ADRC_NATION LENG (IAV)-LNAME

LNAME

LAST NAME



O

ADRC_NATION LENG (IAV)

MIDDLE

MIDDLE NAME or SECOND FORENAME



O

ADRC_NATION LENG (IAV)-BIRTH

BIRTH

BIRTH NAME



O

ADRC_NATION LENG (IAV)

BUILDING_B

BUILDING B



O

ADRC_NATION LENG (IAV)

ROOM_B

ROOM B



O

ADRC_NATION LENG (IAV)

FLOOR_B

FLOOR B



O

ADRC_NATION LENG (IAV)

CITY

CITY



O

ADRC_NATION LENG (IAV)

STREET

STREET



O

ADRC_NATION LENG (IAV)

HOUSE_NO

HOUSE NUMBER



O

ADRC_NATION LENG (IAV)

BUILDING

BUILDING



O

ADRC_NATION LENG (IAV)

ROOM

ROOM



O

ADRC_NATION LENG (IAV)

FLOOR

FLOOR



O

FIWTIN_TAN_EXEM

ACCNO

SUPPLIER



R

FIWTIN_TAN_EXEM

BUKRS

COMPANY CODE



R

FIWTIN_TAN_EXEM

SECCODE

SECTION CODE / SECTION CODE GROUP



R

FIWTIN_TAN_EXEM

WT_EXDF

EXEMPTION FROM 



O

FIWTIN_TAN_EXEM

WT_EXDT

EXEMPTION TO



O

FIWTIN_TAN_EXEM

WT_EXNR

EXEMPTION NUMBER



R

FIWTIN_TAN_EXEM

WT_EXRT

EXEMPTION RATE



O

FIWTIN_TAN_EXEM

WT-WT_EXRS

EXEMPTION REASON



O

FIWTIN_TAN_EXEM

THR

EXEMPTION THRESHOLD AMOUNT



O

FIWTIN_TAN_EXEM

WAERS

EXEMPTION CURRENCY



O

WYT3

LIFNR

VENDOR



R

WYT3

EKORG

PURCHASING ORGANIZATION



R

WYT3

LTSNR

SUPPLIER SUBRANGE



O

WYT3

WERKS

PLANT



O

LMF1

WEBRE

INDICATOR : GR-BASED INVOICE VERIFICATION



O

LFM1

EXPVZ

MODE OF TRANSPORT AT BORDER



O

LMF1

XERSR

AUTOMATIC EVALUATED RECEIPT SETTLEMENT



O

LMF1

WAERS

PURCHASE ORDER CURRENCY



O

LFM1

EKGRP

PURCHASING GROUP



O

LFM1

PLIFZDAT

PLANNED DELIVERY TIME



O

LFM1

INCO1

INCOTERMS (PART 1)



O

LFM1

INCO2_L

INCOTERMS LOCATION 1



O

LFM1

ZTERMDAT

TERMS OF PAYMENT KEY



O

LFBK

HBKID

SHORT KEY FOR HOUSE BANK



O

LFBK

BANKS

BANK COUNTRY / REGION KEY



R

LFBK

BANKL

BANK KEYS



C

LFBK

BKONT

BANK CONTROL KEY



O

LFBK

BKREF

REFERENCE SPECIFICATIONS FOR BANL DETAIL



O


Data Cleansing


IDCriticalityError Message/Report DescriptionRuleOutputSource System

3026-001

C1

Deduplication

Deduplication of supplier records with parent and child approach.

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)



PF1/WP1

3026-002

C2

Vendor General Bank - Missing or Incorrect Bank details

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

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

3) Banks assigned to Vendors (BP) must be validated in Bank Master table (BNKA). If BANK details are not found then after confirmation from Business get missing BANK details configured in System 


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

PF1/WP1

3026-003

C2

Vendor General - Missing or Incorrect Address details 

1) The address info is mandatory, check if source data is updated.

2) For Business Partners (vendors), ensure the 'City' is populated in the Vendor General Data.



PF1/WP1

3026-004

 C2

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



PF1/WP1
3026-005C2Missing Emails

Check if correct 'Email' is not populated for Purchasing Organization


PF1/WP1

3026-006

 C2

Not Approved Payment Terms

Check the Payment Terms assigned to the vendor and verify if it  exists in the mapping table


PF1/WP1








Conversion Process

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

Summarize High-Level Process. Include diagrams, where applicable. Include information supporting details of Extract, Transform and Load specific to the Data Object


Data Privacy and Sensitivity

Summarize Data Privacy and Sensitivity Requirements, if any


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













Selection Screen

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





















Data Collection Template (DCT)

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

<Object> DCT Rules

Field NameField DescriptionRule












Extraction Dependencies

List the steps that need to occur before extraction can commence

Item #Step DescriptionTeam Responsible













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













Transformation Rules

Rule #Source systemSource TableSource FieldSource DescriptionTarget SystemTarget TableTarget FieldTarget DescriptionTransformation Logic









































Transformation Mapping

Use the exact name and reference this section in the “Transformation rules” above
Mapping Table NameMapping Table Description








Transformation Dependencies

List the steps that need to occur before transformation can commence
Item #Step DescriptionTeam Responsible













Pre-Load Validation

Project Team

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

Completeness

TaskAction
titlespecific details of what and how the task needs to be performed e.g. which reports are being used etc.





Accuracy

TaskAction
titlespecific details of what and how the task needs to be performed e.g. which reports are being used etc.





Business

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

Completeness

TaskAction
titlespecific details of what and how the task needs to be performed e.g. which reports are being used etc.





Accuracy

TaskAction
titlespecific details of what and how the task needs to be performed e.g. which reports are being used etc.





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













Load Phase and Dependencies

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

Configuration

List the Configurations required before loading can commence

Item #Configuration Item






Conversion Objects

Object #Preceding Object Conversion Approach

list the exact title of the conversion object of only the immediate predecessor – this will then confirm the DDD (Data Dependency Diagram)




Error Handling

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

Error TypeError DescriptionAction Taken










Post-Load Validation

Project Team

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

Completeness

TaskAction
titlespecific details of what and how the task needs to be performed e.g. which reports are being used etc.





Accuracy

TaskAction
titlespecific details of what and how the task needs to be performed e.g. which reports are being used etc.





Business

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

Completeness

TaskAction
titlespecific details of what and how the task needs to be performed e.g. which reports are being used etc.





Accuracy

TaskAction
titlespecific details of what and how the task needs to be performed e.g. which reports are being used etc.





Key Assumptions

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

Any additional key assumptions.


See also

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

Change log

Workflow history