Status
Owner	CHAN-ext, Beng Chee MADHOK-ext, Jasleen
Stakeholders	The 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 – 3^rd 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:

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

The data from legacy system excludes:

Vendors blocked or marked for deletion.
Purchasing organization not in scope
Inactive vendors with no transactions for the past 2 years
Employee Vendor where account group LFA1-KTOKK is ('ZZPE' in PF2, 'Z012' in WP2)
Commission Agent where account group LFA1-KTOKK is 'ZXAG'
Catalog Supplier where Attribute 6 LFA1-ZZLATR6 is not BLANK
Intercompany Vendor Class LFA1-ZZR_SEGT_ATTR is 'G'

List of source systems and approximate number of records

Source

Scope

Source Approx No. of Records

Target System

Target Approx

No. of Records

PF2, WP2

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.

Table	Field	Data Element	Field Description	Data Type	Length	Requirement
LFM1	LIFNR	ELIFN	SUPPLIER NUMBER	CHAR	10	R
LFM1	EKORG	EKORG	PURCHASING ORGANISATION	CHAR	4	R
LFM1	EKGRP	EKGRP	PURCHASING GROUP	CHAR	3	O
LFM1	WAERS	BSTWA	ORDER CURRENCY	CUKY	5	C
LFM1	VERKF	EVERK	SALESPERSON	CHAR	30	O
LFM1	TELF1	TELFE	SUPPLIER'S TELEPHONE NUMBER	CHAR	16	O
LFM1	MINBW	MINBW	MINIMUM ORDER VALUE	CURR	13	O
LFM1	ZTERM	DZTERM	TERM OF PAYMENT KEY	CHAR	4	C
LFM1	INCOV	INCOV	INCO VERSION	CHAR	4	O
LFM1	INCO1	INCO1	INCOTERMS	CHAR	3	R
LFM1	INCO2_ID ??		INCOTERMS LOCATION 1 ID	CHAR	70	R
LFM1	INCO2_L	INCO2_L	INCOTERMS LOCATION 1	CHAR	70	R
LFM1	KALSK	KALSK	GROUP FOR CALCULATION SCHEMA	CHAR	2	O
LFM1	PLIFZ	PLIFZ	PLANNED DELIVERY TIME	DEC	3	O
LFM1	LFABC	LFABC	ABC INDICATOR	CHAR	1	O
LFM1	VSBED	VSBED	SHIPPING CONDITIONS	CHAR	2	R
LFM1	WEBRE	WEBRE	GR-BASED INVOICE VERIFICATION	CHAR	1	C
LFM1	KZAUT	KZAUT	AUTOMATIC PURCHASE ORDER	CHAR	1	O
LFM1	MEPRF	MEPRF	PRICING DATE CONTROL	CHAR	1	O
LFM1	BSTAE	BSTAE	CONFIRMATION CONTROL KEY	CHAR	4	O
LFM1	KZRET	KZRET	RETURNS SUPPLIER	CHAR	1	O
LFM1	AUBEL	AUBEL	AUTOMATIC DEBIT	CHAR	1	O
LFM1	VALID_PRO	VALID_PRO	SETTLEMENT PROFILE	CHAR	4	O
LFM1	HSCABS	HSCABS	ABSOLUTE HANDLING SURCHARGE	CURR	13	O
LFM1	HSCPE	HSCPE	PERCENTAGE HANDLING SURCHARGE	DEC	5	O
LFM1	HSCMIN	HSCMIN	MINIMUM HANDLING SURCHARGE	CURR	13	O
LFM1	HSCMAX	HSCMAX	MAXIMUM HANDLING SURCHARGE	CURR	13	O
LFM1	XERSY	XERSY	AUTOM EVALUATED RECEIPT SETTLEMENT (ERS)	CHAR	1	C
LFM1	XERSR	XERSR	AUTOM EVALUATED GR SETTLEMENT RETURN	CHAR	1	C
LFM1	KZABS	KZABS	ORDER ACKNOWLEDGMENT REQUIREMENT	CHAR	1	C
WYT3	LIFNR	LIFNR	SUPPLIER	CHAR	10	R
WYT3	EKORG	EKORG	PURCHASING ORG	CHAR	4	R
WYT3	PARVW	PARVW	PARTNER FUNCTION	CHAR	2	R
WYT3	LIFN2	LIFN2	SUPPLIER ID	CHAR	10	C
WYT3	PERNR	PERNR_D	EMPLOYEE ID	NUMC	8	O
WYT3	PARNR	PARNR	CONTACT PERSON ID	NUMC	10	O
WYT3	DEFPA	DEFPA	DEFAULT PARTNER	CHAR	1	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		LAST NAME			O
ADRC_NATION LENG (IAV) ??	MIDDLE		MIDDLE NAME or SECOND FORENAME			O
ADRC_NATION LENG (IAV) ??	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	WT_ACNO	SUPPLIER	CHAR	10	R
FIWTIN_TAN_EXEM	BUKRS	BURKS	COMPANY CODE	CHAR	4	R
FIWTIN_TAN_EXEM	SECCODE	SECCO	SECTION CODE / SECTION CODE GROUP	CHAR	4	R
FIWTIN_TAN_EXEM	WT_EXDF	WT_EXDF	EXEMPTION FROM	DATS	8	O
FIWTIN_TAN_EXEM	WT_EXDT	WT_EXDT	EXEMPTION TO	DATS	8	O
FIWTIN_TAN_EXEM	WT_EXNR	WT_EXNR	EXEMPTION NUMBER	CHAR	25	R
FIWTIN_TAN_EXEM	WT_EXRT	WT_EXRT	EXEMPTION RATE	DEC	5	O
FIWTIN_TAN_EXEM	WT-WT_EXRS	WT_WTEXRS	EXEMPTION REASON	CHAR	2	O
FIWTIN_TAN_EXEM	THR	?	EXEMPTION THRESHOLD AMOUNT			O
FIWTIN_TAN_EXEM	WAERS	WAERS	EXEMPTION CURRENCY	CUKY	5	O
LFM1	EXPVZ	EXPVZ	MODE OF TRANSPORT AT BORDER	CHAR	1	R
LFM1	ZTERMDAT	?	TERMS OF PAYMENT KEY			O
LFBK	HBKID	?	SHORT KEY FOR HOUSE BANK			O
LFBK	BANKS	BANKS	BANK COUNTRY / REGION KEY	CHAR	3	R
LFBK	BANKL	BANKK	BANK KEYS	CHAR	15	C
LFBK	BKONT	BKONT	BANK CONTROL KEY	CHAR	2	O
LFBK	BKREF	BKREF	REFERENCE SPECIFICATIONS FOR BANK DETAIL	CHAR	20	O

Data Cleansing

ID	Criticality	Error Message/Report Description	Rule	Output	Source 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)		PF2/WP2
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	PF2/WP2
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.		PF2/WP2
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		PF2/WP2
3026-005	C2	Missing Emails	Check if correct 'Email' is not populated for Purchasing Organization		PF2/WP2
3026-006	C2	Not Approved Payment Terms	Check the Payment Terms assigned to the vendor and verify if it exists in the mapping table		PF2/WP2

Conversion Process

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

SyWay Project > CNV-3026 Business Partners – 3rd Party Suppliers (FLVN001) > image-2025-6-29_22-23-22-1.png

Deduplication

Business Partner – General deduplication will include cleansing activity to remove vendor duplicates. The golden record selected will be referenced for global data info (general data) in migration.

Vendor records without duplicates will automatically selected as golden record on its own.

The next step is to determine Purchasing Organization extensions from Vendors identified in global relevancy and will undergo a deduplication exercise to determine record source of purchasing data for Business Partner – 3^rd Party Suppliers.

This is where business needs to select which record to use as valid source of Purchasing Organization data.

Scenario 1: Non-Duplicate Vendor (Global) having multiple active Purchasing Organization extensions

Vendor has no duplicates at global level. However, vendor has multiple Purchasing Organization data within same name, country, etc.

Scenario 2: Duplicate Vendors (Global) having multiple active Purchasing Organizations

Duplication of vendor exist in Vendor Global duplicate group and extended to same purchasing organization.

Data Privacy and Sensitivity

Extraction

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

The data exists. Syniti Migrate connects to the source and loads the data into Syniti Migrate. There are 3 methods:
1. Perform full data extraction from relevant tables in the source system(s).
2. Perform extraction through the application layer.
3. Only if Syniti Migrate; cannot connect to the source, data is loaded to the repository from the provided source system extract/report.
The data does not exist (or cannot be converted from its current state). The data is manually collected by the business directly in Syniti Migrate. This is to be conducted using DCT (Data Collection Template) in Syniti Migrate

The agreed Relevancy criteria is applied to the extracted records to identify the records that are applicable for the Target loads

Extraction Run Sheet

Req #	Requirement Description	Team Responsible
1	Refresh LFA1, LFM1, LFBK tables via Syniti Tool (Vendor data)	Data

Selection Screen

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

Selection Ref Screen	Parameter Name	Selection Type	Requirement	Value to be entered/set
N/A

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 Name	Field Description	Rule

Extraction Dependencies

List the steps that need to occur before extraction can commence

Item #	Step Description	Team Responsible
1	Ensure that the necessary cleansing activities in legacy sources (PF1,WP1) are complete	Data/Business
2	Ensure that create, change and deletion of master data is freeze in PF1, WP1 Production system	SyWay IT team

Transformation

The Target fields are mapped to the applicable Legacy field that will be its source, this is a 3-way activity involving the Business, Functional team and Data team. This identifies the transformation activity required to allow Syniti Migrate to make the data Target ready:

Perform value mapping and data transformation rules.
1. Legacy values are mapped to the to-be values (this could include a default value)
2. Values are transformed according to the rules defined in Syniti Migrate
Prepare target-ready data in the structure and format that is required for loading via prescribed Load Tool. This step also produces the load data ready for business to perform Pre-load Data Validation

Transformation Run Sheet

Item #	Step Description	Team Responsible
1	Run LFA1 Relevancy in Syniti	Data
2	Run LFM1 Relevancy in Syniti	Data
3	Run BP Relevancy in Syniti	Data
4	Run Business Partner Supplier execution in Syniti	Data

Transformation Rules

Rule #	Source system	Source Table	Source Field	Source Description	Target System	Target Table	Target Field	Target Description	Transformation Logic
1	PF2/WP2	LFA1	LIFNR	VENDOR NUMBER	S/4 HANA	BUT000	PARTNER	SUPPLIER NUMBER	Derive via legacy to SyWay S4 Business Partner mapping
2	PF2/WP2	LFA1	KTOKK	ACCOUNT GROUP	S/4 HANA	BUT000	BU_GROUP	BP GROUPING
3	PF2/WP2	LFA1	SPERQ	BLOCK FUNCTION	S/4 HANA	LFA1	SPERQ	BLOCK FUNCTION
4	PF2/WP2	LFA1	WERKS	PLANT	S/4 HANA	LFA1	WERKS	PLANT
5	PF2/WP2	LFA1	WERKR	PLANT RELEVANT	S/4 HANA	LFA1	WERKR	PLANT RELEVANT
6	PF2/WP2	LFA1	SPERZ	PAYMENT BLOCK	S/4 HANA	LFA1	SPERZ	PAYMENT BLOCK
7	PF2/WP2	LFA1	NODEL	GENERAL DATA BLOCK	S/4 HANA	LFA1	NODEL	GENERAL DATA BLOCK
8	PF2/WP2		SPRAS	PROPOSED LANGUAGE	S/4 HANA		SPRAS	PROPOSED LANGUAGE	Default to "English"
9	PF2/WP2	LFM1	LIFNR	VENDOR NUMBER	S/4 HANA	LFM1	LIFNR	SUPPLIER NUMBER	Derive via legacy to SyWay S4 Business Partner mapping
10	PF2/WP2	LFM1	EKORG	PURCHASING ORGANISATION	S/4 HANA	LFM1	EKORG	PURCHASING ORGANISATION	Derive via legacy to SyWay S4 Purchasing Organization mapping
11	PF2/WP2	LFM1	EKGRP	PURCHASING GROUP	S/4 HANA	LFM1	EKGRP	PURCHASING GROUP	Derive via legacy to SyWay S4 Purchasing Group mapping
12	PF2/WP2	LFM1	WAERS	ORDER CURRENCY	S/4 HANA	LFM1	WAERS	ORDER CURRENCY	*Derive via legacy to SyWay S4 Purchasing Currency code mapping
13	PF2/WP2	LFM1	VERKF	SALESPERSON	S/4 HANA	LFM1	VERKF	SALESPERSON
14	PF2/WP2	LFM1	TELF1	TELEPHONE	S/4 HANA	LFM1	TELF1	TELEPHONE
15	PF2/WP2	LFM1	MINBW	MINIMUM ORDER VALUE	S/4 HANA	LFM1	MINBW	MINIMUM ORDER VALUE
16	PF2/WP2	LFM1	ZTERM	PAYMENT TERMS	S/4 HANA	LFM1	ZTERM	PAYMENT TERMS
17	PF2/WP2	LFM1	INCOV	INCO VERSION	S/4 HANA	LFM1	INCOV	INCO VERSION
18	PF2/WP2	LFM1	INCO1	INCOTERMS	S/4 HANA	LFM1	INCO1	INCOTERMS	Derive via legacy to SyWay S4 Incoterms mapping
19	PF2/WP2	LFM1	INCO2_L	INCOTERMS LOCATION 1	S/4 HANA	LFM1	INCO2_L	INCOTERMS LOCATION 1	*Derive via legacy to SyWay S4 Incoterms Location mapping
20	PF2/WP2	LFM1	INCO3_L	INCOTERMS LOCATION 2	S/4 HANA	LFM1	INCO3_L	INCOTERMS LOCATION 2
21	PF2/WP2	LFM1	KALSK	SCHEMA GROUP SUPPLIER	S/4 HANA	LFM1	KALSK	SCHEMA GROUP SUPPLIER
22	PF2/WP2	LFM1	PLIFZ	PLANNED DELIVERY TIME	S/4 HANA	LFM1	PLIFZ	PLANNED DELIVERY TIME
23
24	PF2/WP2	LFM1	LFABC	ABC INDICATOR	S/4 HANA	LFM1	LFABC	ABC INDICATOR
25	PF2/WP2	LFM1	VSBED	SHIPPING CONDITIONS	S/4 HANA	LFM1	VSBED	SHIPPING CONDITIONS
26	PF2/WP2	LFM1	WEBRE	GR-BASED INVOICE VERIFICATION	S/4 HANA	LFM1	WEBRE	GR-BASED INVOICE VERIFICATION
27	PF2/WP2	LFM1	KZAUT	AUTOMATIC PURCHASE ORDER	S/4 HANA	LFM1	KZAUT	AUTOMATIC PURCHASE ORDER
28	PF2/WP2	LFM1	MEPRF	PRICING DATE CONTROL	S/4 HANA	LFM1	MEPRF	PRICING DATE CONTROL
29	PF2/WP2	LFM1	BSTAE	CONFIRMATION CONTROL KEY	S/4 HANA	LFM1	BSTAE	CONFIRMATION CONTROL KEY
30	PF2/WP2	LFM1	KZRET	RETURNS SUPPLIER	S/4 HANA	LFM1	KZRET	RETURNS SUPPLIER
31	PF2/WP2	LFM1	AUBEL	AUTOMATIC DEBIT	S/4 HANA	LFM1	AUBEL	AUTOMATIC DEBIT
32	PF2/WP2	LFM1	VALID_PRO	SETTLEMENT PROFILE	S/4 HANA	LFM1	VALID_PRO	SETTLEMENT PROFILE
33	PF2/WP2	LFM1	HSCABS	ABSOLUTE HANDLING SURCHARGE	S/4 HANA	LFM1	HSCABS	ABSOLUTE HANDLING SURCHARGE
34	PF2/WP2	LFM1	HSCPE	PERCENTAGE HANDLING SURCHARGE	S/4 HANA	LFM1	HSCPE	PERCENTAGE HANDLING SURCHARGE
35	PF2/WP2	LFM1	HSCMIN	MINIMUM HANDLING SURCHARGE	S/4 HANA	LFM1	HSCMIN	MINIMUM HANDLING SURCHARGE
36	PF2/WP2	LFM1	HSCMAX	MAXIMUM HANDLING SURCHARGE	S/4 HANA	LFM1	HSCMAX	MAXIMUM HANDLING SURCHARGE
37	PF2/WP2	LFM1	XERSY	AUTOM EVALUATED RECEIPT SETTLEMENT (ERS)	S/4 HANA	LFM1	XERSY	AUTOM EVALUATED RECEIPT SETTLEMENT (ERS)
38	PF2/WP2	LFM1	XERSR	AUTOM EVALUATED GR SETTLEMENT RETURN	S/4 HANA	LFM1	XERSR	AUTOM EVALUATED GR SETTLEMENT RETURN
39	PF2/WP2	LFM1	KZABS	ORDER ACKNOWLEDGMENT REQUIREMENT	S/4 HANA	LFM1	KZABS	ORDER ACKNOWLEDGMENT REQUIREMENT
40	PF2/WP2	WYT3	LIFNR	VENDOR	S/4 HANA	WYT3	LIFNR	SUPPLIER
41	PF2/WP2	WYT3	EKORG	PURCHASING ORG	S/4 HANA	WYT3	EKORG	PURCHASING ORG
42	PF2/WP2	WYT3	PARVW	PARTNER FUNCTION	S/4 HANA	WYT3	PARVW	PARTNER FUNCTION
43	PF2/WP2	WYT3	LIFN2	REF TO VENDOR	S/4 HANA	WYT3	LIFN2	REF TO VENDOR
44	PF2/WP2	WYT3	PERNR	PERSONAL NO	S/4 HANA	WYT3	PERNR	PERSONAL NO
45	PF2/WP2	WYT3	PARNR	CONTACT PERSON	S/4 HANA	WYT3	PARNR	CONTACT PERSON
46	PF2/WP2	WYT3	DEFPA	DEFAULT PARTNER	S/4 HANA	WYT3	DEFPA	DEFAULT PARTNER
47	PF2/WP2	STXL	TDNAME	VENDOR	S/4 HANA	Function - READ_TEXT (STHX header table)	LIFNR	SUPPLIER
48	PF2/WP2	STXL	EKORG	PURCHASING ORGRNIZATION	S/4 HANA	Function - READ_TEXT (STHX header table)	EKORG	PURCHASING ORGANIZATION
49	PF2/WP2	STXL	TDID	TEXT ID	S/4 HANA	Function - READ_TEXT (STHX header table)	TDID	TEXT ID
50	PF2/WP2	STXL	TDSPRAS	LANGUAGE	S/4 HANA	Function - READ_TEXT (STHX header table)	TEXT_TDSPRAS	LANGUAGE KEY
51	PF2/WP2	STXL	CLUSTD	DATA	S/4 HANA	Function - READ_TEXT (STHX header table)	TEXT_LINES	TEXT
52	PF2/WP2	KNVK	LIFNR	VENDOR	S/4 HANA	ADRC_NATION LENG (IAV)-LIFNR	LIFNR	SUPPLIER
53	PF1/WP2	KNVK	PARNR	CONTACT PERSON ID	S/4 HANA	ADRC_NATION LENG (IAV)-PARNR	PARNR	CONTACT PERSON ID
54	PF2/WP2	ADRC	NATION	ADDRESS VERSION	S/4 HANA	ADRC_NATION LENG (IAV)-PARNR	NATION	ADDRESS VERSION
55	PF2/WP2	ADRC	NAME1	NAME 1	S/4 HANA	ADRC_NATION	VNAME	FIRST NAME
56	PF2/WP2	ADRC	NAME2	NAME 2	S/4 HANA	ADRC_NATION LENG (IAV)-VNAME	LNAME	LAST NAME
57	PF2/WP2	ADRC	NAME3	NAME 3	S/4 HANA	ADRC_NATION LENG (IAV)-LNAME	NAME_MIDDLE	MIDDLE NAME
58	PF2/WP2	ADRC	NAME4	NAME 4	S/4 HANA	ADRC_NATION LENG (IAV)-MIDDLE	NAME_BIRTH	BIRTH NAME
59	PF2/WP2	?			S/4 HANA	ADRC_NATION LENG (IAV)-BIRTH	BUILDING_B	BUILDING CODE
60	PF2/WP2	?			S/4 HANA	ADRC_NATION LENG (IAV)-BUILDING_B	ROOM_B	ROOM NUMBER
61	PF2/WP2	?			S/4 HANA	ADRC_NATION LENG (IAV)-ROOM_B	FLOOR_B	FLOOR
62	PF2/WP2	ADRC	CITY	CITY1	S/4 HANA	ADRC_NATION LENG (IAV)-FLOOR_B	CITY	CITY
63	PF2/WP2	ADRC	STREET	STREET	S/4 HANA	ADRC_NATION LENG (IAV)-CITY	STREET	STREET
64	PF2/WP2	ADRC	HOUSE_NUM1	HOUSE NUMBER	S/4 HANA	ADRC_NATION LENG (IAV)-STREET	HOUSE_NO	HOUSE NUMBER
65	PF2/WP2	ADRC	BUILDING	BUILDING CODE	S/4 HANA	ADRC_NATION LENG (IAV)-HOUSE_NO	BUILDING	BUILDING CODE
66	PF2/WP2	ADRC	ROOMNUMBER	ROOM NUMBER	S/4 HANA	ADRC_NATION LENG (IAV)--BUILDING	ROOM	ROOM NUMBER
67	PF2/WP2	ADRC	FLOOR	FLOOR	S/4 HANA	ADRC_NATION LENG (IAV)-ROOM	FLOOR	FLOOR
68	PF2/WP2	FIWTIN_TAN_EXEM	ACCNO	SUPPLIER	S/4 HANA	FIWTIN_TAN_EXEM	ACCNO	SUPPLIER
69	PF2/WP2	FIWTIN_TAN_EXEM	BUKRS	COMPANY CODE	S/4 HANA	FIWTIN_TAN_EXEM	BUKRS	COMPANY CODE
70	PF2/WP2	FIWTIN_TAN_EXEM	SECCODE	SECTION CODE	S/4 HANA	FIWTIN_TAN_EXEM	SECCODE	SECTION CODE
71	PF2/WP2	FIWTIN_TAN_EXEM	WT_EXDF	EXEMPTION FROM	S/4 HANA	FIWTIN_TAN_EXEM	WT_EXDF	EXEMPTION FROM
72	PF2/WP2	FIWTIN_TAN_EXEM	WT_EXDT	EXEMPTION TO	S/4 HANA	FIWTIN_TAN_EXEM	WT_EXDT	EXEMPTION TO
73	PF2/WP2	FIWTIN_TAN_EXEM	WT_EXNR	EXEMPTION NUMBER	S/4 HANA	FIWTIN_TAN_EXEM	WT_EXNR	EXEMPTION NUMBER
74	PF2/WP2	FIWTIN_TAN_EXEM	WT_EXRT	EXEMPTION RATE	S/4 HANA	FIWTIN_TAN_EXEM	WT_EXRT	EXEMPTION RATE
75	PF2/WP2	FIWTIN_TAN_EXEM	WT-WT_EXRS	EXEMPTION REASON	S/4 HANA	FIWTIN_TAN_EXEM	WT-WT_EXRS	EXEMPTION REASON
76	PF2/WP2	FIWTIN_TAN_EXEM	THR	EXEMPTION THRESHOLD AMOUNT	S/4 HANA	FIWTIN_TAN_EXEM	THR	EXEMPTION THRESHOLD AMOUNT
77	PF2/WP2	FIWTIN_TAN_EXEM	WAERS	EXEMPTION CURRENCY	S/4 HANA	FIWTIN_TAN_EXEM	WAERS	EXEMPTION CURRENCY
78	PF2/WP2	WYT3	LIFNR	VENDOR	S/4 HANA	WYT3	LIFNR	VENDOR
79	PF2/WP2	WYT3	EKORG	PURCHASING ORGANIZATION	S/4 HANA	WYT3	EKORG	PURCHASING ORGANIZATION	Derive via legacy to SyWay S4 Purchasing Organization mapping
80	PF2/WP2	WYT3	LTSNR	SUPPLIER SUBRANGE	S/4 HANA	WYT3	LTSNR	SUPPLIER SUBRANGE
81	PF2/WP2	WYT3	WERKS	PLANT	S/4 HANA	WYT3	WERKS	PLANT
83	PF2/WP2	LFM1	EXPVZ	MODE OF TRANSPORT AT BORDER	S/4 HANA	LFM1	EXPVZ	MODE OF TRANSPORT AT BORDER
90	PF2/WP2		???		S/4 HANA	LFM1	ZTERMDAT ???	TERMS OF PAYMENT KEY
91	PF2/WP2		???		S/4 HANA	LFM1	HBKID ???	SHORT KEY FOR HOUSE BANK
92	PF2/WP2	LFBK	BANKS	BANK COUNTRY / REGION KEY	S/4 HANA	LFBK	BANKS	BANK COUNTRY / REGION KEY
93	PF2/WP2	LFBK	BANKL	BANK KEYS	S/4 HANA	LFBK	BANKL	BANK KEYS
94	PF2/WP2	LFBK	BKONT	BANK CONTROL KEY	S/4 HANA	LFBK	BKONT	BANK CONTROL KEY
95	PF2/WP2	LFBK	BKREF	REFERENCE SPECIFICATIONS FOR BANK DETAIL	S/4 HANA	LFBK	BKREF	REFERENCE SPECIFICATIONS FOR BANK DETAIL

Transformation Mapping

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

Mapping Table Name	Mapping Table Description
Legacy Vendor-BP Master Mapping	Legacy to SyWay S4 Business Partner mapping
Purchasing Organization Mapping	Legacy to SyWay S4 Purchasing Organization Mapping
Business Partner deDupe mapping (Global Data)	Dedupe Golden-Child (Global) mapping
Payment Terms Mapping	Legacy to SyWay S4 Payment Terms Mapping
Incoterms Mapping	Legacy to SyWay S4 Incoterms Mapping
Purchasing Group Mapping	Legacy to SyWay S4 Purchasing Group Mapping
Partner Function Mapping	*Legacy to SyWay S4 Partner Function Mapping
Purchasing Currency Code Mapping	*Legacy to SyWay S4 Purchasing Currency code mapping
Vendor deDupe mapping (Purchasing Organization Data)	Dedupe Golden-Child (Purchasing Organization) Mapping
*TBD

Transformation Dependencies

List the steps that need to occur before transformation can commence

Item #	Step Description	Team Responsible
1	Extract PF1,WP1 source tables – LFA1, LFM1, LFBK	Data
2	Ensure all vendor master data collection templates, deduplication and cleansing completeness and no errors	Data
3	Ensure that Business Partner – General is loaded	Data
4	Ensure that all required Configurations are in S/4 HANA	Data

Pre-Load Validation

Project Team

Completeness

Task	Action
Verify Count for External Vendor Purchasing Organization extensions/BP Supplier Role	Verify that the record count in the pre-load file is the same as the record count based on the relevancy (including deduplication) results
Verify Count (Others)	Pre-Load validations record counts will be done to verify completeness and accuracy of the transformed data against DCT approved.

Accuracy

Task	Action
Data Accuracy	Data team to verify that all the data in the load table/file is accurate as per signed-off transformation rules and DCT contents
Error Reports	Verify that all necessary error reports have been validated and that errors have been addressed.

Business

Completeness

Task	Action
Verify Count for External Vendor Purchasing Organization extensions/BP Supplier Role	Verify that the record count in the pre-load file is the same as the record count based on the relevancy (including deduplication) results
Verify Count (Others)	Pre-Load validations record counts will be done to verify completeness and accuracy of the transformed data against DCT approved.
Verify Relevancy Rules	Verify that the relevancy rules were correctly applied

Accuracy

Task	Action
Verify Data Accuracy	Verify that all the data in the load table/file is accurate as per signed-off transformation rules and DCT contents
Review Error Reports	Verify that all necessary error reports have been validated, and that errors have been addressed.
Verify Transformation Rules	Verify that the transformation rules are correct and have been carried out correctly

Load

The load process includes:

Execute the automated data load into target system using load tool or product the load file if the load must be done manually
Once the data is loaded to the target system, it will be extracted and prepared for Post Load Data Validation

Load Run Sheet

Item #	Step Description	Team Responsible
1	Load Sample Vendors Default Partner	Data
2	Validate sample Vendors Default Partner	Data
3	Load remaining Vendors Default Partner	Data
4	Validate data loaded for Vendors Default Partner	Data

Load Phase and Dependencies

Configuration

Item #	Configuration Item
1	Obtain the approved upload USER ID’s to be used (e.g. Firefighter ID)
2	SAP USER profile (SU3) Date and Decimal Notation Formats are in sync with the load format
3	Purchasing Organisation Configuration
4	Purchasing Group Configuration
5	Incoterms Configuration
6	Authorization Group Configuration
7	Plant Configuration
8	Confirmation Control Configuration
9	Payment Terms Configuration

Conversion Objects

Object #	Preceding Object Conversion Approach
3007	Business Partners - General
3018	Business Partners – FI Vendor

Error Handling

Error Type	Error Description	Action Taken
Configuration	<configuration> is not valid/missing	If it is a missing configuration item then engage Functional team to expedite and fix the error in the system.
Invalid Data	<parameter> is not valid.	The parameter entry needs to be reviewed (ex. invalid payment terms). If it is an invalid data, business needs to review and correct the source of the data either in PF1/WP1 or if it’s mapped in DCT.
Technical Setup	Interface / Connection issue within target system’s landscape	N/A – the data will be loaded directly to S/4HANA environment
Authorization Error	<USER ID> is not authorized to access Business Partner create	Contact Basis to obtain Fire Fighter ID (or SyWay S4 approved data loading ID) or fix the authorization setup

Post-Load Validation

Project Team

Completeness

Task	Action
Verify Count for External Vendor Purchasing Organization extensions/BP Supplier Role	Verify that the record count in the post-load report is the same as the record count based on the relevancy (including deduplication) results
Verify Count (Others)	Post-Load validations record counts will be done to verify completeness and accuracy of the transformed data against DCT approved.

Accuracy

Task	Action
Data Accuracy	Data team to verify that all the data in the target tables is accurate as per signed-off transformation rules and DCT contents
Post Load Error Reports	Verify that all necessary post-load error reports have been validated, and that errors have been addressed.

Business

Completeness

Task	Action
Verify Count for External Vendor Purchasing Organization extensions/BP Supplier Role	Verify that the record count in the post-load file is the same as the record count based on the relevancy (including deduplication) results
Verify Count (Others)	Post-Load validations record counts will be done to verify completeness and accuracy of the transformed data against DCT approved.
Validate Loaded Data	Validate, as per the loads files signed-off, that all records are in the target system

Accuracy

Task	Action
Verify Data Accuracy	Verify that all the data in the target tables is accurate as per signed-off transformation rules and DCT contents
Review Post Load Error Reports	Verify that all necessary post load error reports have been validated, and that errors have been addressed.
Validate Loaded Data	Validate, as per the loads files signed-off, that all records are in the target system

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.

Purpose

Conversion Scope

Additional Information

Multi-language Requirement

Document Management

Legal Requirement

Special Requirements

Target Design

Data Cleansing

Conversion Process

Data Privacy and Sensitivity

Extraction

Extraction Run Sheet

Selection Screen

Data Collection Template (DCT)

Extraction Dependencies

Transformation

Transformation Run Sheet

Transformation Mapping

Transformation Dependencies

Pre-Load Validation

Project Team

Completeness

Accuracy

Business

Completeness

Accuracy

Load

Load Run Sheet

Conversion Objects

Error Handling

Post-Load Validation

Project Team

Completeness

Accuracy

Business

Completeness

Accuracy

Key Assumptions

See also

Change log

Workflow history