Status
Owner	MADHOK-ext, Jasleen CELEDONIO-ext, Arnold BATTINI-ext, Srinivasarao
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 *and Intercompany/Plant Suppliers through FLVN01 Supplier Role including Purchasing Organization, partner function, Plant Specific Purchasing including partner Function data and purchasing Text in S/4 HANA.(TBC - There will be 3 SAP instances, one for ROW, one for China and one for CUI only).

In SAP ECC, the Vendor Master Purchasing View (including the Partner Functions) is part of the Vendor Master Data, which is used to store vendor-related information for purchasing transactions. The setup typically involves maintaining vendor records separately for different purchasing organizations..

In SAP S/4HANA, the Vendor Purchasing View is integrated into the Business Partner (BP) model, which replaces the traditional customer/vendor objects from ECC. The Business Partner serves as a central entity, allowing a single record to hold multiple roles (e.g., customer and vendor). The Vendor Purchasing View in S/4HANA is represented under the BP role FLVN001, which contains-specific data such as purchasing organization, purchasing group, payment terms, purchasing currency, incoterms, shipping conditions and partner functions.

In SAP ECC and SAP S/4 HANA Vendor purchasing texts are stored in the the general text tables STXH (SAPScript Text Header) and STXL (SAPScript Test Lines) and the specific text for a vendor is linked using object type LFM1 and text IDs in these tables. Vendor purchasing text refers to the process and configuration that automatically copies predefined text from the vendor master record into the purchasing documents like purchase orders. *(Extract all records from legacy tables STXH and STXL where TDOBJECT = LFM1)

In SAP ECC and SAP S/4 HANA, Plant specific vendor purchasing data is maintained in within the purchasing organization section in SAP ECC and within the Business Partner(BP) master record under the FLVN01 Supplier Role in the purchasing organization section with an additional plant key. The data is used to define procurement conditions unique to a specific plant overriding the general purchasing organization data where applicable. If alternative data is greyed out then, to activate this field data retention at plant level to be allowed at the general data level.

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.

MDS and Conversion Specification is referring to the tables and fields - LFA1: Supplier Master (General Section),LFA1: Vendor tax data, LFBK - Vendor bank data, LFBW-Withholding tax data which will be covered part of 3007-Business Partners - General (Role 000000 ETL , Conversion Specification and Design.

CNV-3026 Business Partners – 3rd Party Suppliers (FLVN001) is using both ETL and DCT conversion processes for the vendors purchasing view including partner functions data, Vendor purchasing Texts data and plant specific vendors purchasing view including partner functions.

---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

*CR0298 - Delete MDS 3027 Business Partners - Plants/Intercompany Suppliers - CS 3026 now included with the Intercompany Suppliers /Plants conversion logic with the reference of CNV-3007 Business Partners - General (Role 000000) - SyWay Project - Syensqo - Wiki knowledge base for the scope and data migration Approach

CNV-3026 Business Partners - Intercompany / Plant BP Suppliers purchasing view including partner functions data, Vendor purchasing Texts data and plant specific vendors purchasing view including partner functions is in the migration scope which is using both ETL and DCT Conversion process.

However, as the definition follows the Intercompany BP General data migration Scope -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 vendor number if applicable.

Supplier general data - for Intercompany BP scenario, the value will be prepopulated based on the enterprise structure. A mapping of the new Intercompany / Plant BP and legacy ECC intercompany customer/vendor will be provided to propose the baseline values.

Conversion Specification is applicable for both the External Vendors, Intercompany / Plant Vendors with the same set of table structures, transformation, conversion and DCT rules until unless exception rule added throughout the CS.

Basic criteria for the Intercompany / Plant BP Suppliers:

1) Intercompany / Plant BP Suppliers scope will be based on the 3007-Business Partners - General (Role 000000)- CNV Google drive path - CNV-3007 Business Partners - General (Role 000000) - SyWay Project - Syensqo - Wiki knowledge base

2) Relevancy Rules under Data Object (3007-Business Partners - General (Role 000000)), CNV Google drive path - CNV-3007 Business Partners - General (Role 000000) - SyWay Project - Syensqo - Wiki knowledge base

3) Purchase Organization mapping - Follows the enterprise mapping structure

4) Plant mapping - Follows the enterprise mapping structure

5) Business Partners which are not in legacy that they may have been created via DCT including the Intercompany/Plant Vendors.

-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

Tables Includes for the CNV-3026 Business Partners – 3rd Party Suppliers (FLVN001) are:

LFM1: Vendor master record purchasing organization data
WYT3: Partner Functions
LFM2: Vendor Master Record: Purchasing Data - Plant Specific
STXH: STXD SAPscript text file header
STXL: STXD SAPscript text file lines

Relevancy Rule

The data from legacy system includes:

Vendors which pass Relevancy Rules under Data Object (3007-Business Partners - General (Role 000000)), CNV Google drive path - CNV-3007 Business Partners - General (Role 000000) - SyWay Project - Syensqo - Wiki knowledge base
Should be created to Purchasing Organization 'inscope' based on Enterprise Structure Catalog
Should be extended to Standard list(approved list) of Partner Functions (based on MDS-3026).
Vendors’ relevant purchasing data with potential duplicate records as per the criteria - Vendors Purchasing Data Deduplication will be mainly based on the Deduplication process of the CNV 3007 and If there are multiple records identified as duplicates with the combination of vendor and purchasing organization but the different attribute values business needs to select the master record to create in S/4.

The data from legacy system excludes:

Vendors which pass Relevancy Rules under Data Object (3007-Business Partners - General (Role 000000)), CNV Google drive path - CNV-3007 Business Partners - General (Role 000000) - SyWay Project - Syensqo - Wiki knowledge base
Vendors extended in Purchasing organization which are not is scope based on Enterprise Structure.
Vendors blocked or marked for deletion at Purchasing Organization level

Inclusion Table Criteria: Inclusion table should be build or in place where data got excluded for some Vendor + Purchasing data due to the vendor relevancy rule or any data is missing as part of the extraction process or based on the Business input.

Exclusion Table Criteria: Exclusion table should be build or in place where data got included for the Vendor + Purchasing data due to the vendor relevancy rule or not needed now as per the Business or migrate the data as a DCT not using the ETL process.

Note: There is open Jira defect [PDM-1085] 3026 - Business Partners - 3rd Party Suppliers-FLVN01 - New Regulatory Requirement : ensuring that a vendor/carrier Business Partner is authorized to transport Dangerous Goods. - Jira for the new requirement and any other new fields to be added which will be coming in future, These will be included into the CS using CR route in future and moving ahead with the CS approval process based on the MDS checked in so far. *Jira ticket is closed now

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, 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 - 3007-Business Partners - General (Role 000000))	TBC	S/4 HANA	TBC
PF2, WP2	External Vendors - Plant specific vendors purchasing data including the partner functions data	TBC	S/4 HANA	TBC
PF2, WP2	External Vendors - purchasing texts data	TBC	S/4 HANA	TBC
*PF2, WP2	Intercompany / Plant vendors Purchasing Data including Partner Functions data	TBC	S/4 HANA	TBC
PF2, WP2	Intercompany / Plant vendors - Plant specific vendors purchasing data including the partner functions data	TBC	S/4 HANA	TBC
PF2, WP2	Intercompany / Plant vendors - purchasing long texts data	TBC	S/4 HANA	TBC

Additional Information

Multi-language Requirement (TBC as this is based on the multi-language criteria from 3007-Business Partners - General (Role 000000))

Will follow multi-language allowed and created in 3007-Business Partners - General (Role 000000)

Document Management

N/A

Legal Requirement

N/A

Special Requirements

N/A

Target Design

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

MDS Rules and Google Drive path for the MDS - DD-FUN-050 Master Data Standard_BP_3026-Supplier Role_3031_Supplier Doc. Attachments.xlsx - Google Sheets

The technical design of the target for this conversion approach.

Table	Field	Data Element	Field Description	Data Type	Length	Requirement
LFM1	LIFNR	LIFNR	Supplier* (BP Code)	CHAR	10	R
LFM1	EKORG	EKORG	Purchasing Organization*	CHAR	4	R
LFM1	EKGRP	EKGRP	Purchasing Group	CHAR	3	C
LFM1	WAERS	WAERS	Order Currency	CUKY	5	C
LFM1	VERKF	VERKF	Salesperson	CHAR	30	Not Used
LFM1	TELF1	TELF1	Supplier's Telephone Number	CHAR	16	Not Used
LFM1	MINBW	MINBW	Minimum Order Value	CURR	16	Not Used
LFM1	ZTERM	ZTERM	Terms of Payment Key	CHAR	4	C
LFM1	INCOV	INCOV	Inco. Version	CHAR	4	Not Used
LFM1	INCO1	INCO1	Incoterms	CHAR	3	C
*TMINCO_LOC_DATA	INCO2_ID	INCO2_ID	Identifier for Incoterm Location 1	CHAR	20	R
LFM1	INCO2_L	INCO2_L	Incoterms Location 1	CHAR	70	C
LFM1	KALSK	KALSK	Group for Calculation Schema	CHAR	2	R
LFM1	PLIFZ	PLIFZ	Planned Delivery Time in Days	DEC	10	Not Used
LFM1	LFABC	LFABC	ABC Indicator	CHAR	1	Not Used
LFM1	VSBED	VSBED	Shipping Conditions	CHAR	2	C
LFM1	WEBRE	WEBRE	GR-Based Invoice Verification	CHAR	1	C
LFM1	KZAUT	KZAUT	Automatic PO	CHAR	1	R
LFM1	MEPRF	MEPRF	Pricing Date Control	CHAR	1	C
LFM1	BSTAE	BSTAE	Confirmation Control Key	CHAR	4	C
LFM1	KZRET	KZRET	Returns Supplier	CHAR	1	C
LFM1	AUBEL	AUBEL	Automatic Debit	CHAR	1	Not Used
LFM1	VALID_PRO	VALID_PRO	Settlement Profile	CHAR	4	Not Used
LFM1	HSCABS	HSCABS	Absolute Handling Surcharge	CURR	16	Not Used
LFM1	HSCPE	HSCPE	Percentage Handling Surcharge	DEC	16	Not Used
LFM1	HSCMIN	HSCMIN	Minimum Handling Surcharge	CURR	16	Not Used
LFM1	HSCMAX	HSCMAX	Maximum Handling Surcharge	CURR	16	Not Used
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
LFM1	EIKTO	EIKTO	Account with supplier	CHAR	12	Not Used
LFM1	NRGEW	NRGEW	Grant free goods	CHAR	1	Not Used
LFM1	PAPRF	PAPRF	Proact control profile	CHAR	4	Not Used
LFM1	BOLRE	BOLRE	Subsequent settlement	CHAR	1	Not Used
LFM1	XNBWY	XNBWY	Revaluation	CHAR	1	Not Used
LFM1	VENDOR_RMA_REQ	VENDOR_RMA_REQ	RMA required	CHAR	1	Not Used
LFM1	PRFRE	PRFRE	Price determination	CHAR	1	Not Used
LFM1	BOIND	BOIND	Subsequent settlement indicator active	CHAR	1	Not Used
LFM1	BLIND	BLIND	Document index	CHAR	1	TBD
LFM1	AGREL	AGREL	Relevant for settlement management	CHAR	1	Not Used
LFM1	LOEVM	LOEVM	Deletion flag purchasing organization	CHAR	1	Not Used
LFM1	SKRIT	SKRIT	Sort criterion	CHAR	1	Not Used
LFM1	SPERM	SPERM	Selected purchasing organization block	CHAR	1	C
LFM1	MRPPP	MRPPP	Planning calendar	CHAR	3	Not Used
LFM1	LFRHY	LFRHY	Planning cycle	CHAR	3	Not Used
LFM1	BOPNR	BOPNR	Order optimization restriction	CHAR	4	Not Used
LFM1	LIBES	LIBES	Order entry by supplier	CHAR	1	Not Used
LFM1	LIPRE	LIPRE	Price marking Supplier	CHAR	2	Not Used
LFM1	LISER	LISER	Rack Jobbing	CHAR	1	Not Used
LFM1	ZOLLA	ZOLLA	Customs Office: Office of Exit/Entry for Foreign Trade	CHAR	6	C
LFM1	INCO3_L	INCO3_L	Incoterms Location 2	CHAR	70	Not Used
LFM1	RDPRF	RDPRF	Rounding Profile	CHAR	4	Not Used
LFM1	MEGRU	MEGRU	Unit of Measure Group	CHAR	4	Not Used
LFM1	ABUEB	ABUEB	Release Creation Profile	CHAR	4	Not Used
LFM1	LFM1_EEW_PS	LFM1_EEW_PS	Data Element Extensibility for purchase	CHAR	1	Not Used
LFM1	J_1NBOESL	J_1NBOESL	Exchange Key for NF Processing	CHAR	3	C (Not Used)
LFM1	FSH_SC_CID	FSH_SC_CID	Customer/Supplier Identifier	CHAR	2	Not Used
LFM1	FSH_VAS_DETC	FSH_VAS_DETC	VAS Determination Mode	CHAR	1	Not Used
LFM1	UPPRS	UPPRS	Pricing on Subitems (MPN/SUS)	CHAR	1	Not Used
LFM1	ACTIVITY_PROFIL		Activity Profile for PO Controlling	CHAR	4	Not Used
LFM1	TRANSPORT_CHAIN	TRANSPORT_CHAIN	Transportation Chain	CHAR	10	Not Used
LFM1	STAGING_TIME	STAGING_TIME	Staging Time in Days	DEC	3	Not Used
LFM1	EXPVZ	EXPVZ	Mode of Transport at the Border (Intrast	CHAR	1	Not Used
LFM1	VENSL	VENSL	Supplier Service Level	DEC	5	Not Used
LFM1	LEBRE	LEBRE	Service - based Invoice verification	CHAR	1	R
LFM1	UMSAE	UMSAE	Comparison and agreement of business volumes	CHAR	1	Not Used
*LFM1	WEORA	WEO ACTIVITY_PROFILRA	Origin acceptance	CHAR	1	Not Used
*LFM1	ZZ_DGID	ZZ_DGID	DG identification	CHAR	2	C
LFM2	LIFNR	LIFNR	Supplier* (BP code)	CHAR	10	R
LFM2	EKORG	EKORG	Purchasing Organization*	CHAR	4	R
LFM2	LTSNR	LTSNR	Suppl, Subrange*	CHAR	6	R
LFM2	WERKS	WERKS	Plant*	CHAR	4	R
WRF02K(TBC)	HINZE	XDYNP	Indicator: plant level relevant - Purchasing Data	CHAR	1	C
WRF02K(TBC)	HINZP	XDYNP	Indicator: plant level relevant - Partner Functions	CHAR	1	C
LFM2	EKGRP	EKGRP	Purchasing Group	CHAR	3	C
LFM2	WAERS	WAERS	Order Currency	CUKY	5	C
LFM2	VERKF	VERKF	Salesperson	CHAR	30	Not Used
LFM2	TELF1	TELF1	Supplier's Telephone Number	CHAR	16	Not Used
LFM2	MINBW	MINBW	Minimum Order Value	CURR	16	Not Used
LFM2	ZTERM	ZTERM	Terms of Payment Key	CHAR	4	C
LFM2	INCOV	INCOV	Inco. Version	CHAR	4	Not Used
LFM2	INCO1	INCO1	Incoterms	CHAR	3	C
*TMINCO_LOC_DATA	INCO2_ID	INCO2_ID	Identifier for Incoterm Location 1	CHAR	20	R
LFM2	INCO2_L	INCO2_L	Incoterms Location 1	CHAR	70	C
LFM2	KALSK	KALSK	Group for Calculation Schema	CHAR	2	R
LFM2	PLIFZ	PLIFZ	Planned Delivery Time in Days	DEC	10	Not Used
LFM2	LFABC	LFABC	ABC Indicator	CHAR	1	Not Used
LFM2	WEBRE	WEBRE	GR-Based Invoice Verification	CHAR	1	C
LFM2	KZAUT	KZAUT	Automatic PO	CHAR	1	R
LFM2	MEPRF	MEPRF	Pricing Date Control	CHAR	1	C
LFM2	BSTAE	BSTAE	Confirmation Control Key	CHAR	4	C
LFM2	XERSY	XERSY	Autom Evaluated Receipt Settlement (ERS)	CHAR	1	C
LFM2	XERSR	XERSR	Autom Evaluated GR Settlement Return	CHAR	1	C
LFM2	KZABS	KZABS	Order Acknowledgment Requirement	CHAR	1	C
LFM2	PAPRF	PAPRF	Proact control profile	CHAR	4	Not Used
LFM2	BOLRE	BOLRE	Subsequent settlement	CHAR	1	Not Used
LFM2	XNBWY	XNBWY	Revaluation	CHAR	1	Not Used
LFM2	KZABS	KZABS	Order Acknowledgment Requirement	CHAR	1	C
LFM2	PAPRF	PAPRF	Proact control profile	CHAR	4	Not Used
LFM2	BOLRE	BOLRE	Subsequent settlement	CHAR	1	Not Used
LFM2	XNBWY	XNBWY	Revaluation	CHAR	1	Not Used
LFM2	BOIND	BOIND	Subsequent settlement indicator active	CHAR	1	Not Used
LFM2	LOEVM	LOEVM	Deletion flag purchasing organization	CHAR	1	Not Used
LFM2	SPERM	SPERM	Selected purchasing organization block	CHAR	1	C
LFM2	MRPPP	MRPPP	Planning calendar	CHAR	3	Not Used
LFM2	LFRHY	LFRHY	Planning cycle	CHAR	3	Not Used
LFM2	BOPNR	BOPNR	Order optimization restriction	CHAR	4	Not Used
LFM2	LIBES	LIBES	Order entry by supplier	CHAR	1	Not Used
LFM2	LIPRE	LIPRE	Price marking Supplier	CHAR	2	Not Used
LFM2	LISER	LISER	Rack Jobbing	CHAR	1	Not Used
LFM2	ZOLLA	ZOLLA	Customs Office: Office of Exit/Entry for Foreign Trade	CHAR	6	C
LFM2	INCO3_L	INCO3_L	Incoterms Location 2	CHAR	70	Not Used
LFM2	RDPRF	RDPRF	Rounding Profile	CHAR	4	Not Used
LFM2	MEGRU	MEGRU	Unit of Measure Group	CHAR	4	Not Used
LFM2	ABUEB	ABUEB	Release Creation Profile	CHAR	4	Not Used
LFM2	TRANSPORT_CHAIN	TRANSPORT_CHAIN	Transportation Chain	CHAR	10	Not Used
LFM2	STAGING_TIME	STAGING_TIME	Staging Time in Days	DEC	3	Not Used
LFM2	EXPVZ	EXPVZ	Mode of Transport at the Border (Intrast	CHAR	1	Not Used
LFM2	LEBRE	LEBRE	Service - based Invoice verification	CHAR	1	R
LFM2	UMSAE	UMSAE	Comparison and agreement of business volumes	CHAR	1	Not Used
LFM2	WEORA	WEORA	Origin acceptance	CHAR	1	*C (Not Used)
WYT3	LIFNR	LIFNR	Supplier* (BP code)	CHAR	10	R
WYT3	PARVW	PARVW	Partner Function*	CHAR	2	R
WYT3	LIFN2	LIFN2	Ref to vendor	CHAR	10	C
WYT3	PERNR	PERNR	Personnel No.	NUMC	8	Not Used
WYT3	PARNR	PARNR	Contact Person ID	NUMC	10	C
WYT3	DEFPA	DEFPA	Default	CHAR	1	C
WYT3	EKORG	EKORG	Purchasing organization	CHAR	4	R
WYT3	LTSNR	LTSNR	Supplier Subrange	CHAR	6	Not used
WYT3	WERKS	WERKS	Plant	CHAR	4	Not used
*STXH	TDOBJECT	TDOBJECT	Text object	CHAR	10	Not used
STXH	TDNAME	TDNAME	Text Name	CHAR	70	Not used
STXH	TDID	TDID	Text ID	CHAR	4	Not used
STXH	TDSPRAS	TDSPRAS	Language	CHAR	2	Not used
STXL	TDOBJECT	TDOBJECT	Text object	CHAR	10	Required
STXL	TDNAME	TDNAME	Text name	CHAR	70	Required
STXL	TDID	TDID	Text ID	CHAR	4	Required
STXL	TDSPRAS	SPRAS	Language key	LANG	1	Required
STXL	CLUSTD	CLUSTD	Data - SAPscript: LONG RAW field for table STXL	LRAW	7902	Required

*Vendor: Tax Data. Brazil (only for the information and the conversion logic will be covered as part of the CNV 3007 & captured here the field information) hence is there is no technical work for the CNV 3026.

S No	Technical Table-Field	Field Label	Field Description	Data Type	Length	Requirement	Rule Description
1	LFA1-TERM_LI	Terms of Liability	This specifies whether a supplier organization has accepted the terms of liability. This is an indicator field. If the criterion is met, enter X. If not, leave the field empty.	CHAR	1	C	It is a flag. For all countries it is not needed, while it is optional only for Brazil. This specifies whether a supplier organization has accepted the terms of liability. This is an indicator field. If the criterion is met, enter X. If not, leave the field empty.
2	LFA1-COMSIZE	Company Size	Identifies the company's size according to the number of employees and the annual sales revenue. Possible company sizes are: Large company Medium company Small company Micro company Micro entrepreneur	CHAR	2	C	It is validated against relevant company sides available in S/4 HANA. For all countries it is not needed, while it is optional only for Brazil Possible company sizes are: Large company Medium company Small company Micro company Micro entrepreneur"
3	LFA1-CRC_NUM	CRC Number	The CRC number is a unique identification number for the supplier organization according to Brazilian law. Identifies the RG (Registro Geral) number."This can be a maximum of 25 characters in length. Note: You cannot assign the same CRC number to different suppliers. It must be unique for each organization.	CHAR	25	C	It is a freetext. The CRC number is a unique identification number for the supplier organization according to Brazilian law. For all countries it is not needed, while it is optional only for Brazil. This can be a maximum of 25 characters in length. Note: You cannot assign the same CRC number to different suppliers. It must be unique for each organization.
4	LFA1-RG	RG Number	This field captures the issue date of the RG number, a form of identity document specific to Brazil (Registro Geral).	CHAR	11	C	It is a freetext. Identifies the RG (Registro Geral) number. For all countries it is not needed, while it is optional only for Brazil
5	LFA1-EXP	Issued By	Issued By. Describes the issuing authority or organization that issued the identification document. Examples: For passports → issuing country or government agency. For RG in Brazil → state public security department.	CHAR	3	C	It is a freetext. Issued By. For all countries it is not needed, while it is optional only for Brazil
6	LFA1-UF	State	State. Indicates the issuing “State” for identity documents like RG (Registro Geral) in Brazil. Typically represented as a two-letter state code (e.g., “SP” for São Paulo).	CHAR	2	C	It is a freetext. Indicates the issuing “State” for identity documents like RG (Registro Geral) in Brazil. Typically represented as a two-letter state code (e.g., “SP” for São Paulo). For all countries it is not needed, while it is optional only for Brazil
7	LFA1-RGDATE	RG Issuing Date	RG Issuing Date	DATS	10	C	Calendar. This field captures the issue date of the RG number, a form of identity document specific to Brazil (Registro Geral). For all countries it is not needed, while it is optional only for Brazil
8	LFA1-RIC	RIC Number	RIC Number Identifies the civil identity registry number (registro de identidade civil).	NUMC	11	C	It is a freetext. RIC Number. For all countries it is not needed, while it is optional only for Brazil Identifies the civil identity registry number (registro de identidade civil).
9	LFA1-RNE	Foreign National Registration	Identifies the foreign national registration number.	CHAR	10	C	It is a freetext. Identifies the foreign national registration number. For all countries it is not needed, while it is optional only for Brazil
10	LFA1-RNEDATE	RNE Issuing Date	Identifies the foreign national registration issuing date.	DATS	10	C	Calendar. Identifies the foreign national registration issuing date. For all countries it is not needed, while it is optional only for Brazil
11	LFA1-CNAE	CNAE	Identifies the Economic Activity National Classification - CNAE.	CHAR	7	C	It is validated against relevant CNAEs available in S/4 HANA. For all countries it is not needed, while it is optional only for Brazil
12	LFA1-LEGALNAT	Legal Nature	Identifies the company's legal nature.	NUMC	4	C	It is validated against relevant Legal Natures available in S/4 HANA. For all countries it is not needed, while it is optional only for Brazil
13	LFA1-CRTN	CRT Number	Identifies the Tax Regimen Code. The Tax Regimen Code (Código de Regime Tributário), depending on the company and its tributary situation, can be classified as Simples Nacional, Simples Nacional – excesso de sublimite da receita bruta and Regime Normal (não simples).	CHAR	1	C	It is validated against relevant CRTs available in S/4 HANA. For all countries it is not needed, while it is optional only for Brazil Values: 1 Simples Nacional 2 Simples Nacional # excesso de sublimite da receita bruta 3 Regime Normal (não simples) 4 Simples Nacional - Microempreendedor Individual - MEI
14	LFA1-ICMSTAXPAY	ICMS Taxpayer	Identifies the company's category for ICMS payment. The Brazilian government charges ICMS differently according to the type of taxpayer. Companies are classified as Contribuinte (ICMS Taxpayer) and Não Contribuinte (ICMS Non-Taxpayer): Mantain values: - 1 - CO - ICMT Taxpayer (Contribuinte do ICMS) - BP is required to collect ICMS taxes - 2 - EX - ICMS Exempt (Contribuiente Isento do ICM) - BP is registered for a collection process of ICMS but got a law exception and has no requirement to collect it - 9 - NC - ICMS Non Taxpayer (Nao Contribuinte do ICMS) - BP in not registered for the ICMS collection - Blank - when the 3 possibilities above are unknown/ when the master data has been created	CHAR	1	C	Check table J_1BTICMSTAXPAY Fill it by default for Brazil- Mantain values: 1, 2, 9, Blank Others, blank. More details: - 1 - CO - ICMT Taxpayer (Contribuinte do ICMS) - BP is required to collect ICMS taxes - 2 - EX - ICMS Exempt (Contribuiente Isento do ICM) - BP is registered for a collection process of ICMS but got a law exception and has no requirement to collect it - 9 - NC - ICMS Non Taxpayer (Nao Contribuinte do ICMS) - BP in not registered for the ICMS collection - Blank - When the 3 possibilities above are unknown/ when the master data has been created
15	LFA1-INDTYP	Industry Main Type	Identifies the Industry Main Type.	CHAR	2	C	It is validated against relevant Industry main types available in S/4 HANA. For all countries it is not needed, while it is optional only for Brazil
16	LFA1-TDT	Tax Declaration Type	Identifies the type of ICMS paid by the company to the Brazilian government.	CHAR	2	C	It is validated against relevant tax declaration types available in S/4 HANA. For all countries it is not needed, while it is optional only for Brazil

Data Cleansing

Analysis Report or Validation Reports path for the reference -

ID	Criticality	Error Message/Report Description	Rule	Source System
3026-001	C-1	Deduplication	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. Parent and child approach will be used for selection of golden record. 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.	PF2/WP2
3026-002	C-1	Identify Vendor not used in the existing purchasing organization	Needs to be verified for the active vendors based on the relevancy criteria of CNV-3007 & *Get the extract from LFM1 table including all the fields which are in migration scope.	PF2/WP2
3026-003	C-2	Fill in mandatory fields based on master data standards Purchasing Organization Payment Terms Incoterms and incoterms location Purchasing Group Schema Group Shipping Conditions Conformation Control Key Purchasing Currency Partner Functions Plant	For all the active vendors purchasing data in migration scope, make sure to fill all the mandatory fields based on the value mappings agreed to generate the report for the business for the cleansing if needed. Report should be generated for any missing data for the mandatory fields to do the needed cleansing activity by the business	PF2/WP2
3026-004	C-2	Validate obsolete payment term maintained or Not Approved Payment Terms	For all the active vendors in migration scope, if there is payment term, and the payment term value is not in S4 Hana design Check the Payment Terms assigned to the vendor and verify if it exists in the mapping table	PF2/WP2
3026-005	C-2	Not Approved Payment Terms	Check the Payment Terms assigned to the vendor and verify if it exists in the mapping table	PF2/WP2
3026-006	C-1	Vendors Purchasing Long Text Report	Needs to be verified for the active vendors based on the relevancy criteria of CNV-3007 Get the Vendors Purchasing Long Text data from ECC system	PF2/WP2
3026-007	C-2	Vendors Partner Functions Report	Get the Vendors Partner Functions Report where the PI and OA vendors are different from the VN partner from ECC system	PF2/WP2
3026-008	C-2	Vendors Plant Specific Purchasing Organization data (Additional data at Purchasing Organization level)	Get the Vendors Plant Specific Purchasing Organization Report from ECC system	PF2/WP2
3026-009	C-2	Vendors Plant Specific Purchasing Organization Partner Functions data (Additional data at Purchasing Organization level)	Get the Vendors Plant Specific Purchasing Organization Partner Functions Report from ECC system	PF2/WP2

Conversion Process

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

The ETL (Extract, Transform, Load) process is a structured approach to data migration and management, ensuring high-quality data is seamlessly transferred across systems with the exception of DCT for any additional vendor partner functions data . 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.

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 using migration cockpit.

SyWay Project > CNV-3026 Business Partners – 3rd Party Suppliers (FLVN001) > image-2025-11-2_20-5-21-1.png

DCT Process- Collection will be done manually in the Data Collection Template for the following scenarios:

For the vendors purchasing view including partner functions data, Vendor purchasing Texts data and plant specific vendors purchasing view including partner functions data that need to be created to support the to-be design.
For the vendors purchasing view including partner functions data, Vendor purchasing Texts data and plant specific vendors purchasing view including partner functions data that need to be created to support the to-be design. which is not in SAP ECC

High Level Conversion Process - Source - DCT.png

Data Privacy and Sensitivity

N/A

Extraction

Extract data from a source into Syniti Migrate for SAP relevant entities. 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
Refresh Criteria	Refresh LFM1, LFM2, WYT3 tables via Syniti Tool (Vendor data)	Data team
Extraction Scope Definition	Identify the source systems and databases involved. Define the data objects (tables, fields, records) to be extracted. Establish business rules for data selection.	Syniti / Data team
Extraction Methodology	Specify the extraction approach (full, incremental, or delta extraction). Determine the tools and technologies used. Define data filtering criteria to exclude irrelevant records.	Syniti
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

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.

N/A

Data Collection Template (DCT)

Target Ready Data Collection Template will be created for the vendors purchasing view including partner functions data, Vendor purchasing Texts data and plant specific vendors purchasing view including partner functions data.

(if needed) data with exception of some fields which require transformation as mentioned in the transformation rule.

The extracted report will be loaded into the required structure using the DCT.
Standardization activities (including deduplication, standardization and additions) will be carried out within the DCT.

DCT Rules:

Vendors Purchasing Organization Data:
Technical Table-Field	Field Label	Field Description	Rule
LFM1-LIFNR	Supplier*	Supplier* *-BP code.	R
LFM1-EKORG	Purchasing Organization*	An organizational unit in Logistics, subdividing an enterprise according to the requirements of Purchasing. A purchasing organization procures products and services, negotiates conditions of purchase with suppliers, and is responsible for such transactions. You specify the form of procurement by assigning purchasing organizations to company codes and plants.	R
LFM1-EKGRP	Purchasing Group	Key for a buyer or a group of buyers responsible for the procurement of the product.	C
LFM1-WAERS	Order Currency	Key for the currency on which an order placed with a supplier is based.	C
LFM1-ZTERM	Terms of Payment Key	Key for defining payment terms composed of cash discount percentages and payment periods.	C
LFM1-INCO1	Incoterms	*An incoterms version is an edition containing a list of international terms for transportation that is defined by the International Chamber of Commerce (ICC). Version will not be used in TM, just the actual location.	C
*TMINCO_LOC_DATA-INCO2_ID	Identifier for Incoterm Location 1	Planning Responsibility: The duty to organize the transport for a transport section Cost Responsibility: The duty to contract for and pay the costs and freight for a transport section Risk Responsibility (for Incoterm non-C clauses): Assumption of the risk of loss and damage to the goods for a transport section. Logic: INCO2_ID Mandatory and INCO2_L automatically updated from (INCO2_ID) and not editable
LFM1-INCO2_L	Incoterms Location 1	Provides additional information for the Incoterms. INCO2_ID Mandatory and INCO2_L automatically updated from (INCO2_ID) and not editable	C
LFM1-KALSK	Group for Calculation Schema	Determines which calculation schema (pricing procedure) is to be used in purchasing documents containing this supplier number.	R
LFM1-VSBED	Shipping Conditions	General shipping strategy for the delivery of goods from the supplier to the customer.	C
LFM1-WEBRE	GR-Based Invoice Verification	This is an indicator field. If the criterion is met, enter X. If not, leave the field empty.	C
LFM1-KZAUT	Automatic PO	This is an indicator field. If the criterion is met, enter X. If not, leave the field empty. Allows you to automatically generate purchase orders from purchase requisitions if the requisition has been assigned to a supplier (source of supply).	R
LFM1-MEPRF	Pricing Date Control	Determines which date is to be used for price determination (pricing) purposes. By default leave it blank.	C
LFM1-BSTAE	Confirmation Control Key	Determines which confirmation categories are expected for a PO item (for example order acknowledgment, shipping notification).	C
LFM1-KZRET	Returns Supplier	Indicates that a supplier return is carried out using shipping processing. You can also use shipping processing for supplier returns. Enter X or leave the indicator field empty. If you use the return supplier indicator, the customer master record must exists in the system. The customer reference field is at General Data sheet.	C
LFM1-XERSY	Autom Evaluated Receipt Settlement (ERS)	This is an indicator field. If the criterion is met, enter X. If not, leave the field empty.	C
LFM1-XERSR	Autom Evaluated GR Settlement Return	This is an indicator field. If the criterion is met, enter X. If not, leave the field empty.	C
LFM1-KZABS	Order Acknowledgment Requirement	Determines whether the purchasing document (as purchase order, and so on.) is to be acknowledged by the supplier. Enter X or leave the indicator field empty.	C
LFM1-BLIND	Document index	Indicates that a document index is allowed for purchase orders issued to this supplier. The index is used for determining the relevant purchasing documents affected by changes to conditions offered by the supplier.	*C
LFM1-SPERM	Selected purchasing organization block	Indicates whether or not the supplier master record is blocked for the purchasing organization for posting purposes. Based on Business Requirements	C
LFM1- ZOLLA	Customs Office: Office of Exit/Entry for Foreign Trade	Specifies the code of the customs office through which the goods enter or leave the country. This information is used for compiling export/import data for foreign trade statistics.	C
LFM1- J_1NBOESL	Exchange Key for NF Processing	Brazilian taxes	C (Not Used)
LFM1-LEBRE	Service - based Invoice verification	Indicates that service-based invoice verification is defined for a purchase order item. In service-based invoice verification, the quantities and values of services performed and ordered to date are available for checking purposes. As in the case of invoice verification for materials, you are able to change quantities and values within the permitted tolerances. In addition, if service-based invoice verification is active, the acceptance posting is carried out at the level of the services in the entry sheet, and the quantities and values of the accepted and invoiced services are shown in the PO history. For a service PO, It will be always flagged as it is driven by the item category used in the Purchase order (Always Item Category ‘D’ for services).	R
*LFM1-WEORA	Origin Acceptance	Not Used Direct Mapping (Flag X/blank) whether goods must be formally accepted at the place of origin (i.e., the vendor’s or manufacturer’s site) before they are shipped to you. Flag is based on vendor specific information captured.	C (Not Used)
LFM1-ZZ_DGID	DG Identification	Carrier Business Partner Identifier to capture the carrier authorization/capability to transport Dangerous Goods in the master data. An identifier should be maintained at the supplier purchase organization and carrier level with possible values: ZDG, ZXC, BLANK, High Consequence. It will be located at: At Purchase Organization level --> Purchasing Data tab ---> Control Data section in both Roles. Name of the field: “DG identification”, dropdown list field. Possible values: 01. DG 02. Non-DG 03. DG Exempted 04. High Consequence	C
Vendors Purchasing Organization Partner Functions Data:
Technical Table-Field	Field Label	Field Description	Rule
WYT3-LIFNR	Supplier*	Supplier* (BP code)	R
WYT3-PARVW	Partner Function*	The abbreviated form of the name that identifies the partner function. Aligned to the Governance column in "BP Role Matrix Organizations" The partner function that you enter for the data migration differs from the value you see on the UI. Default values: PI – Invoicing Party The partner to whom the payment should be made. Controls invoice processing. GS – Goods Supplier The actual party delivering the goods; used if the delivery source differs from the supplier on PO. OA – Ordering Address The address where the purchase order is sent. Useful when the vendor has multiple branches. VN - Vendor CR - Carrier *CP - Contact Person The logistics provider or freight forwarder responsible for transporting goods. ZA - TMS4S: the value will be the same Main BP code ZB - BN4L: the value will be the same Main BP code ZC - Transwide : the value will be the same Main BP code In case of CASS-> PI partner function with BP code equal to the Main BP can be used- Note: currently it will be only maintained when the email address is different in case of legal entity (Different BP code)	R
WYT3-LIFN2	Ref to vendor	This partner is only mandatory if you choose a partner role which refers to this partner. One of the partner fields is always mandatory.
WYT3-PARNR	Contact Person ID	This partner is only mandatory if you choose a partner role which refers to this partner. One of the partner fields is always mandatory.
WYT3-DEFPA	Default	Specifies a partner as the default for a particular partner function. This is an indicator field. If the criterion is met, enter X. If not, leave the field empty.	C
WYT3-EKORG	Purchasing organization	Purchasing organization. An organizational unit in Logistics, subdividing an enterprise according to the requirements of Purchasing. A purchasing organization procures products and services, negotiates conditions of purchase with suppliers, and is responsible for such transactions. You specify the form of procurement by assigning purchasing organizations to company codes and plants.	R

Vendors Plant Specific Purchasing Organization Data:
Technical Table-Field	Field Label	Field Description	Rule
LFM2-LIFNR	Supplier*	Supplier* (BP code)- key field for Supplier Range at plant level	R
LFM2-EKORG	Purchasing Organization*	Key field for Supplier Range at plant level An organizational unit in Logistics, subdividing an enterprise according to the requirements of Purchasing. A purchasing organization procures products and services, negotiates conditions of purchase with suppliers, and is responsible for such transactions. You specify the form of procurement by assigning purchasing organizations to company codes and plants.	R
LFM2-LTSNR	Suppl, Subrange*	Supplier Subrange - Key field for Supplier Range at plant level.	R
LFM2-WERKS	Plant*	Key that uniquely identifies a plant. GENERAL RULE: All the fields equal to the fields coming from LFM1 (the only one field that could be different is "Customs Office: Office of Exit/Entry for Foreign Trade (LFM2- ZOLLA)	R
WRF02K-HINZE(TBC)	Indicator: plant level relevant - Purchasing Data	Flag. Select in case the specific data within the plant refers to Purchasing Data. GENERAL RULE: All the fields equal to the fields coming from LFM1 (the only one field that could be different is "Customs Office: Office of Exit/Entry for Foreign Trade (LFM2- ZOLLA)	C
WRF02K-HINZP(TBC)	Indicator: plant level relevant - Partner Functions	Flag. Select in case the specific data within the plant refers to Partner function data.	C
LFM2-EKGRP	Purchasing Group	Key for a buyer or a group of buyers responsible for the procurement of the product. Equal to the value at Purchas. Organization level (LFM1 - inherited)	C
LFM2-WAERS	Order Currency	Key for the currency on which an order placed with a supplier is based.	C
LFM2-ZTERM	Terms of Payment Key	Key for defining payment terms composed of cash discount percentages and payment periods.	C
LFM2-INCO1	Incoterms	Incoterms specify certain internationally recognized procedures that the shipper and the receiving party must follow for the shipping transaction to be successfully completed.	C
*TMINCO_LOC_DATA-INCO2_ID	Identifier for Incoterm Location 1	Planning Responsibility: The duty to organize the transport for a transport section Cost Responsibility: The duty to contract for and pay the costs and freight for a transport section Risk Responsibility (for Incoterm non-C clauses): Assumption of the risk of loss and damage to the goods for a transport section. Logic: INCO2_ID Mandatory and INCO2_L automatically updated from (INCO2_ID) and not editable.
LFM2-INCO2_L	Incoterms Location 1	Provides additional information for the Incoterms. INCO2_ID Mandatory and INCO2_L automatically updated from (INCO2_ID) and not editable	C
LFM2-KALSK	Group for Calculation Schema	Determines which calculation schema (pricing procedure) is to be used in purchasing documents containing this supplier number. Equal than at Purchas. Organ. level.(table LFM1 -inherited)	R
LFM2-WEBRE	GR-Based Invoice Verification	This is an indicator field. If the criterion is met, enter X. If not, leave the field empty.	C
LFM2-KZAUT	Automatic PO	This is an indicator field. If the criterion is met, enter X. If not, leave the field empty. Allows you to automatically generate purchase orders from purchase requisitions if the requisition has been assigned to a supplier (source of supply).	R
LFM2-MEPRF	Pricing Date Control	Determines which date is to be used for price determination (pricing) purposes. By default leave it blank.	C
LFM2-BSTAE	Confirmation Control Key	Determines which confirmation categories are expected for a PO item (for example order acknowledgment, shipping notification).	C
LFM2-XERSY	Autom Evaluated Receipt Settlement (ERS)	This is an indicator field. If the criterion is met, enter X. If not, leave the field empty.	C
LFM2-XERSR	Autom Evaluated GR Settlement Return	This is an indicator field. If the criterion is met, enter X. If not, leave the field empty.	C
LFM2-KZABS	Order Acknowledgment Requirement	Determines whether the purchasing document (as purchase order, and so on.) is to be acknowledged by the supplier. Enter X or leave the indicator field empty.	C
LFM2-SPERM	Selected purchasing organization block	Indicates whether or not the supplier master record is blocked for the purchasing organization for posting purposes. Based on Business Requirements	C
LFM2- ZOLLA	Customs Office: Office of Exit/Entry for Foreign Trade	Specifies the code of the customs office through which the goods enter or leave the country. This information is used for compiling export/import data for foreign trade statistics. Note: GENERAL RULE at plant level: All the fields equal to the fields coming from LFM1 (the only one field that could be different is "Customs Office: Office of Exit/Entry for Foreign Trade (LFM2- ZOLLA)	C
LFM2-LEBRE	Service - based Invoice verification	Indicates that service-based invoice verification is defined for a purchase order item. In service-based invoice verification, the quantities and values of services performed and ordered to date are available for checking purposes. As in the case of invoice verification for materials, you are able to change quantities and values within the permitted tolerances. In addition, if service-based invoice verification is active, the acceptance posting is carried out at the level of the services in the entry sheet, and the quantities and values of the accepted and invoiced services are shown in the PO history. For a service PO, It will be always flagged as it is driven by the item category used in the Purchase order (Always Item Category ‘D’ for services).	R
*LFM2-WEORA	Origin Acceptance	Not Used Direct Mapping (Flag X/blank) whether goods must be formally accepted at the place of origin (i.e., the vendor’s or manufacturer’s site) before they are shipped to you. Flag is based on vendor specific information captured.	C (Not Used)
Vendors Plant Specific Purchasing Organization Partner Functions Data:
Technical Table-Field	Field Label	Field Description	Rule
WYT3-LIFNR	Supplier*	Supplier* (BP code)	R
WYT3-PARVW	Partner Function*	The abbreviated form of the name that identifies the partner function. Aligned to the Governance column in "BP Role Matrix Organizations" The partner function that you enter for the data migration differs from the value you see on the UI. Default values: PI – Invoicing Party The partner to whom the payment should be made. Controls invoice processing. GS – Goods Supplier The actual party delivering the goods; used if the delivery source differs from the supplier on PO. OA – Ordering Address The address where the purchase order is sent. Useful when the vendor has multiple branches. VN - Vendor CR - Carrier *CP - Contact person The logistics provider or freight forwarder responsible for transporting goods. ZA - TMS4S: the value will be the same Main BP code ZB - BN4L: the value will be the same Main BP code ZC - Transwide : the value will be the same Main BP code In case of CASS-> PI partner function with BP code equal to the Main BP can be used- Note: currently it will be only maintained when the email address is different in case of legal entity (Different BP code)	R
*WYT3-WERKS	Plant*	Key that uniquely identifies a plant. GENERAL RULE: All the fields equal to the fields coming from LFM1 (the only one field that could be different is "Customs Office: Office of Exit/Entry for Foreign Trade (LFM2- ZOLLA)	R
WYT3-LIFN2	Ref to vendor	This partner is only mandatory if you choose a partner role which refers to this partner. One of the partner fields is always mandatory.	C
WYT3-PARNR	Contact Person ID	This partner is only mandatory if you choose a partner role which refers to this partner. One of the partner fields is always mandatory.	C
WYT3-DEFPA	Default	Specifies a partner as the default for a particular partner function. This is an indicator field. If the criterion is met, enter X. If not, leave the field empty.	C
WYT3-EKORG	Purchasing organization	Purchasing organization. An organizational unit in Logistics, subdividing an enterprise according to the requirements of Purchasing. A purchasing organization procures products and services, negotiates conditions of purchase with suppliers, and is responsible for such transactions. You specify the form of procurement by assigning purchasing organizations to company codes and plants.	R
Vendors Purchasing Long Text:
Technical-Field Name	Field Label	Rule
*STXH-TDOBJECT	Text object	Not used
STXH-TDNAME	Text Name	Not used
STXH-TDID	Text ID	Not used
TDSPRAS	Language Key	Not used
TDOBJECT	Text object	Required
LIFNR (Part of TDNAME)	Vendor Number (Part of Text Name)	Required
EKORG (Part of TDNAME)	Purchasing Organization (Part of Text Name)	Required
TDID	Text ID	Required
TDSPRAS	Language Key	Required A dropdown with the following values: BG - Bulgarian, DE - German, EN - English, ES - Spanish, FI - Finnish, FR - French, IT - Italian, JA - Japanese, KO - Korean, NL - Dutch, PL - Polish, PT - Portuguese, RU - Russian, TH- Thai, ZF - Chinese traditional, ZH - Mandarin, SK - Slovak, Z9 - Brazil Portuguese.
CLUSTD	Data -SAPscript: LONG RAW field for table STXL	Required No special characters: ; Semi-colon : Colon :: Double Colon ? Question Mark / Forward Slash @ At sign & Ampersand = Equal Sign + Plus Sign $ Dollar Sign % Percent \| Vertical Bar [] Left or Right Square Bracket " Double Quotes

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 (PF2, WP2) are complete	Data/Business
2	Ensure that create, change and deletion of master data is freeze in PF2, WP2 Production system	Syensqo IT
3	Source System Availability Ensure that the source database or application is accessible. Confirm that necessary credentials and permissions are granted	Syensqo IT
4	Data Structure Identify relationships between tables, views, and stored procedures.	Syniti
5	Referential Integrity Ensure dependent records are extracted together.	Syniti
6	Extraction Methodology Define whether extraction is full, incremental, or delta-based. Establish batch processing schedules for large datasets.	Syniti
7	Performance and Scalability Considerations Optimize extraction queries to prevent system overload. Ensure network bandwidth supports data transfer volumes.	Syniti
8	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:

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 LFM1, LFM2 and WYT3 Relevancy in Syniti	Syniti
2	Transformation Scope Definition - Identify the source and target data structures. - Define business rules for data standardization. - Establish data cleansing requirements to remove inconsistencies.	Data Team
3	Data Mapping and Standardization - Align source fields with target fields. - Ensure unit consistency (e.g., currency, measurement units)	Data Team
4	Business Rule Application - Implement data enrichment/collection if applicable - Apply conditional transformations based on predefined logic/business rules	Data Team
5	Transformation Execution Plan - Define batch processing schedules. - Assign responsibilities for monitoring execution. - Establish error-handling mechanisms	Syniti

Transformation Rules

Rule #	Source system	Source Table	Source Field	Source Description	Target System	Target Table	Target Field	Target Description	Transformation Logic
1	PF2/WP2	LFM1	LIFNR	VENDOR NUMBER	S/4 HANA	LFM1	LIFNR	SUPPLIER NUMBER	XREF Derive via legacy to SyWay S4 Business Partner mapping Supplier (*BP Code) Automatically created by the system.
2	PF2/WP2	LFM1	EKORG	PURCHASING ORGANISATION	S/4 HANA	LFM1	EKORG	PURCHASING ORGANISATION	XREF Derive via legacy to SyWay S4 Purchasing Organization mapping It is validated against relevant Purchase Organizations available in S/4 HANA. Customizing. Values of the Purchase Organizations already included in the "MM configuration values document"- Enterprise Structure tab.
3	PF2/WP2	LFM1	EKGRP	PURCHASING GROUP	S/4 HANA	LFM1	EKGRP	PURCHASING GROUP	XREF Derive via legacy to SyWay S4 Purchasing Group mapping It is validated against relevant Purchasing Groups available in S/4 HANA.
4	PF2/WP2	LFM1	WAERS	ORDER CURRENCY	S/4 HANA	LFM1	WAERS	ORDER CURRENCY	XREF Derive via legacy to SyWay S4 Purchasing Currency code mapping * In the PO - in case we have PIR/CTR will come from here. Otherwise, it will take it from the BP. In BP Plants (Account Group = ZICP) no contracts will be used, so the value comes from the BP itself.
5	PF2/WP2	LFM1	VERKF	SALESPERSON	S/4 HANA	LFM1	VERKF	SALESPERSON	Not Used It is free text in S4HANA.
6	PF2/WP2	LFM1	TELF1	TELEPHONE	S/4 HANA	LFM1	TELF1	TELEPHONE	Not Used
7	PF2/WP2	LFM1	MINBW	MINIMUM ORDER VALUE	S/4 HANA	LFM1	MINBW	MINIMUM ORDER VALUE	Not Used
8	PF2/WP2	LFM1	ZTERM	PAYMENT TERMS	S/4 HANA	LFM1	ZTERM	PAYMENT TERMS	XREF Values of the payment terms already included in the "MM configuration values document"- BP Suppliers tab: In the PO - in case we have PIR/CTR will come from here. Otherwise, it will take it from the BP. S4HANA. *In BP Plants/IC suppliers (Account Group = ZICP) no contracts will be used, so the value comes from the BP itself.
9	PF2/WP2	LFM1	INCOV	INCO VERSION	S/4 HANA	LFM1	INCOV	INCO VERSION	Not Used
10	PF2/WP2	LFM1	INCO1	INCOTERMS	S/4 HANA	LFM1	INCO1	INCOTERMS	XREF Derive via legacy to SyWay S4 Incoterms mapping Customizing. Values of the payment terms already included in the "MM configuration values document"- BP Suppliers tab: Set as Conditional because it must be mandatory only for the BPs that trigger Transportation module. The BP subjected to TM must have it as mandatory (as this field should be inherited to the corresponding POs) Fill always , and TM when the BP has Carrier Role (CRM010) will reuse it for the process Otherwise, blank
*11	PPF2/WP2	N/A	N/A	Identifier for Incoterm Location 1	S/4 HANA	TMINCO_LOC_DATA	INCO2_ID	Identifier for Incoterm Location 1	XREF Derive via legacy to SyWay S4 Incoterms Location mapping INCO2_ID Mandatory and INCO2_L automatically updated from (INCO2_ID) and not editable
12	PF2/WP2	LFM1	INCO2_L	INCOTERMS LOCATION 1	S/4 HANA	LFM1	INCO2_L	INCOTERMS LOCATION 1	System Generated INCO2_ID Mandatory and INCO2_L automatically updated from (INCO2_ID) and not editable
13	PF2/WP2	LFM1	INCO3_L (INCO2_L)	INCOTERMS LOCATION 2	S/4 HANA	LFM1	INCO3_L (INCO2_L)	INCOTERMS LOCATION 2	Not Used
14	PF2/WP2	LFM1	KALSK	SCHEMA GROUP SUPPLIER	S/4 HANA	LFM1	KALSK	SCHEMA GROUP SUPPLIER	XREF Values of the Calculation Schemas already included in the "MM configuration values document"- BP Suppliers tab: There are 3 Schema Group Values: 01 Default vendor schema group - when (Grouping BP02/Account Group: LIEF) + (Employee vendors (Grouping: BPEE))* 02 Vendor schema group Intercomp - for BP Plants (Account Group = ZICP) 03 Schema Group for TM - when the BP has Carrier Role (CRM010)
15	PF2/WP2	LFM1	PLIFZ	PLANNED DELIVERY TIME	S/4 HANA	LFM1	PLIFZ	PLANNED DELIVERY TIME	Not Used
16	PF2/WP2	LFM1	LFABC	ABC INDICATOR	S/4 HANA	LFM1	LFABC	ABC INDICATOR	Not used A-Category A (high-value, most critical): The smallest number of suppliers that account for a large portion of the total spend (e.g., 10-20% of suppliers representing 70-80% of value). B-Category B (medium-value): The middle group, with moderate spend and value. C-Category C (low-value, least critical) : The largest group of suppliers that represent a small portion of the total spend.
17	PF2/WP2	LFM1	VSBED	SHIPPING CONDITIONS	S/4 HANA	LFM1	VSBED	SHIPPING CONDITIONS	XREF Values of the shipping conditions should be included in the "SD configuration values document" Conditional for the relevant for TM (01- Sea/02-Sea FCL/03-Air/04-Road/05-Road FTL/06- Rail/07- Customer Collection/08- Parcel Standard/10-Parcel Express) Others (09- Non TM) - blank. Set as Conditional because it must be mandatory only for the BPs that trigger Transportation module. The BP subjected to TM must have it as mandatory (as this field should be inherited to the corresponding POs) General shipping strategy for the delivery of goods from the supplier to the customer. *The same rule for BP plants/IC suppliers (Account Group = ZICP).
18	PF2/WP2	LFM1	WEBRE	GR-BASED INVOICE VERIFICATION	S/4 HANA	LFM1	WEBRE	GR-BASED INVOICE VERIFICATION	Conditional By default always flag (X), *exception For BP Plants: (Account Group = ZICP) that should be blank.
19	PF2/WP2	LFM1	KZAUT	AUTOMATIC PURCHASE ORDER	S/4 HANA	LFM1	KZAUT	AUTOMATIC PURCHASE ORDER	Required By default always flag (X), exception: Suppliers with Carrier role (CRM010) AND In BP Plants (Account Group = ZICP) - Flagged X when the STO is created automatically from the STR (Advance IC Stock transfer - STO type: NBIC Advance IC Transfer) Otherwise: Blank*
20	PF2/WP2	LFM1	MEPRF	PRICING DATE CONTROL	S/4 HANA	LFM1	MEPRF	PRICING DATE CONTROL	Conditional Direct Mapping (need change) By default leave it blank. Possible values:* (blank/NULL) = No Control 1 = Purchase Order Date 5 = Goods Receipt Date (GR Date) It is validated against relevant Pricing Data Control available in S/4 HANA.
21	PF2/WP2	LFM1	BSTAE	CONFIRMATION CONTROL KEY	S/4 HANA	LFM1	BSTAE	CONFIRMATION CONTROL KEY	XREF Valid if the criteria is fit by the supplier. Depending on the way of working (order acknowledgment, shipping notification) of the vendor (few filled in ECC) Rule: Values: - 0001 - ASN and OA* - Z001 - Only OA - Z002 - Intercompany Where the Relevant scenarios for CCCK/ user case are the following: 0001 - Suppliers who will be sending ASN and OA both, Used in Direct procurement, Indirect procurement scenarios. Z002 - Intercompany processes Z001 - Suppliers who will only send OA, Used in Service Procurement
22	PF2/WP2	LFM1	KZRET	RETURNS SUPPLIER	S/4 HANA	LFM1	KZRET	RETURNS SUPPLIER	Conditional , Direct Mapping By default X for all suppliers that supply products. Additionally: the customer master record must exists in the system (customer roles) AND the "customer reference" field filled at General Data role. *Always X for BP plants (Account Group = ZICP)
23	PF2/WP2	LFM1	AUBEL	AUTOMATIC DEBIT	S/4 HANA	LFM1	AUBEL	AUTOMATIC DEBIT	Not Used
24	PF2/WP2	LFM1	VALID_PRO	SETTLEMENT PROFILE	S/4 HANA	LFM1	VALID_PRO	SETTLEMENT PROFILE	Not Used
25	PF2/WP2	LFM1	HSCABS	ABSOLUTE HANDLING SURCHARGE	S/4 HANA	LFM1	HSCABS	ABSOLUTE HANDLING SURCHARGE	Not Used
26	PF2/WP2	LFM1	HSCPE	PERCENTAGE HANDLING SURCHARGE	S/4 HANA	LFM1	HSCPE	PERCENTAGE HANDLING SURCHARGE	Not Used
27	PF2/WP2	LFM1	HSCMIN	MINIMUM HANDLING SURCHARGE	S/4 HANA	LFM1	HSCMIN	MINIMUM HANDLING SURCHARGE	Not Used
28	PF2/WP2	LFM1	HSCMAX	MAXIMUM HANDLING SURCHARGE	S/4 HANA	LFM1	HSCMAX	MAXIMUM HANDLING SURCHARGE	Not Used
29	PF2/WP2	LFM1	XERSY	AUTOM EVALUATED RECEIPT SETTLEMENT (ERS)	S/4 HANA	LFM1	XERSY	AUTOM EVALUATED RECEIPT SETTLEMENT (ERS)	Conditional, Direct Mapping It is a flag. Valid if the criteria is fit by the supplier. For the suppliers relevant to ERS - flag X Others, keep it blank. The Business could provide the list of the relevant suppliers.
30	PF2/WP2	LFM1	XERSR	AUTOM EVALUATED GR SETTLEMENT RETURN	S/4 HANA	LFM1	XERSR	AUTOM EVALUATED GR SETTLEMENT RETURN	Conditional, Direct Mapping It is a flag. Valid if the criteria is fit by the supplier. For the suppliers relevant to ERS - flag X Others, keep it blank. The Business could provide the list of the relevant suppliers.
31	PF2/WP2	LFM1	KZABS	ORDER ACKNOWLEDGMENT REQUIREMENT	S/4 HANA	LFM1	KZABS	ORDER ACKNOWLEDGMENT REQUIREMENT	Conditional By default X. *Exception: For BP Plants (Account Group = ZICP) - blank
32	PF2/WP2	LFM1	EIKTO	ACCOUNT WITH SUPPLIER	S/4 HANA	LFM1	EIKTO	ACCOUNT WITH SUPPLIER	Not Used
33	PF2/WP2	LFM1	NRGEW	GRANT FREE GOODS	S/4 HANA	LFM1	NRGEW	GRANT FREE GOODS	Not Used
34	PF2/WP2	LFM1	PAPRF	PROACT CONTROL PROFILE	S/4 HANA	LFM1	PAPRF	PROACT CONTROL PROFILE	Not Used
35	PF2/WP2	LFM1	BOLRE	SUBSEQUENT SETTLEMENT	S/4 HANA	LFM1	BOLRE	SUBSEQUENT SETTLEMENT	Not Used
36	PF2/WP2	LFM1	XNBWY	REVALUATION	S/4 HANA	LFM1	XNBWY	REVALUATION	Not Used
37	PF2/WP2	LFM1	VENDOR_RMA_REQ	RMA REQUIRED	S/4 HANA	LFM1	VENDOR_RMA_REQ	RMA REQUIRED	Not Used
38	PF2/WP2	LFM1	PRFRE	PRICE DETERMINATION	S/4 HANA	LFM1	PRFRE	PRICE DETERMINATION	Not Used
39	PF2/WP2	LFM1	BOIND	SUBSEQUENT SETTLEMENT INDICATOR ACTIVE	S/4 HANA	LFM1	BOIND	SUBSEQUENT SETTLEMENT INDICATOR ACTIVE	Not Used
40	PF2/WP2	LFM1	BLIND	DOCUMENT INDEX	S/4 HANA	LFM1	BLIND	DOCUMENT INDEX	Conditional (TBD) Flag (X) only in case it fits vendor´s conditions.* If not, leave the field empty.
41	PF2/WP2	LFM1	AGREL	RELEVANT FOR SETTLEMENT MANAGEMENT	S/4 HANA	LFM1	AGREL	RELEVANT FOR SETTLEMENT MANAGEMENT	Not Used
42	PF2/WP2	LFM1	LOEVM	DELETION FLAG PURCHASING ORGANIZATION	S/4 HANA	LFM1	LOEVM	DELETION FLAG PURCHASING ORGANIZATION	Not Used
43	PF2/WP2	LFM1	SKRIT	SORT CRITERION	S/4 HANA		SKRIT	SORT CRITERION	Not Used
44	PF2/WP2	LFM1	SPERM	SELECTED PURCHASING ORGANIZATION BLOCK	S/4 HANA	LFM1	SPERM	SELECTED PURCHASING ORGANIZATION BLOCK	Conditional (Not in LTMC - S/4 HANA Template) Set X in case block is needed for posting / purchasing purposes.
45	PF2/WP2	LFM1	MRPPP	PLANNING CALENDAR	S/4 HANA	LFM1	MRPPP	PLANNING CALENDAR	Not Used
46	PF2/WP2	LFM1	LFRHY	PLANNING CYCLE	S/4 HANA	LFM1	LFRHY	PLANNING CYCLE	Not Used
47	PF2/WP2	LFM1	BOPNR	ORDER OPTIMIZATION RESTRICTION	S/4 HANA	LFM1	BOPNR	ORDER OPTIMIZATION RESTRICTION	Not Used
48	PF2/WP2	LFM1	LIBES	ORDER ENTRY BY SUPPLIER	S/4 HANA	LFM1	LIBES	ORDER ENTRY BY SUPPLIER	Not Used
49	PF2/WP2	LFM1	LIPRE	PRICE MARKING SUPPLIER	S/4 HANA	LFM1	LIPRE	PRICE MARKING SUPPLIER	Not Used
50	PF2/WP2	LFM1	LISER	RACK JOBBING	S/4 HANA	LFM1	LISER	RACK JOBBING	Not Used
51	PF2/WP2	LFA1	XZEMP	INDICATOR: ALTERNATIVE PAYEE IN DOCUMENT ALLOWED?	S/4 HANA	LFM1	XZEMP	INDICATOR: ALTERNATIVE PAYEE IN DOCUMENT ALLOWED?	Not Used Part of LFA1
52	PF2/WP2	LFM1	ZOLLA	CUSTOMS OFFICE: OFFICE OF EXIT/ENTRY FOR FOREIGN TRADE	S/4 HANA	LFM1	ZOLLA	CUSTOMS OFFICE: OFFICE OF EXIT/ENTRY FOR FOREIGN TRADE	Conditional (Not in LTMC - S/4 HANA Template) Direct Mapping Valid for Eugenia Tataru - GTS
53	PF2/WP2	LFM1	INCO3_L	INCOTERMS LOCATION 2	S/4 HANA	LFM1	INCO3_L	INCOTERMS LOCATION 2	Not Used
54	PF2/WP2	LFM1	RDPRF	ROUNDING PROFILE	S/4 HANA	LFM1	RDPRF	ROUNDING PROFILE	Not Used
55	PF2/WP2	LFM1	MEGRU	UNIT OF MEASURE GROUP	S/4 HANA	LFM1	MEGRU	UNIT OF MEASURE GROUP	Not Used
56	PF2/WP2	LFM1	ABUEB	RELEASE CREATION PROFILE	S/4 HANA	LFM1	ABUEB	RELEASE CREATION PROFILE	Not Used
57	PF2/WP2	LFM1	LFM1_EEW_PS	DATA ELEMENT EXTENSIBILITY FOR PURCHASE	S/4 HANA	LFM1	LFM1_EEW_PS	DATA ELEMENT EXTENSIBILITY FOR PURCHASE	Not Used
58	PF2/WP2	LFM1	J_1NBOESL	EXCHANGE KEY FOR NF PROCESSING	S/4 HANA	LFM1	J_1NBOESL	EXCHANGE KEY FOR NF PROCESSING	Not Used Direct Mapping
59	PF2/WP2	LFM1	FSH_SC_CID	CUSTOMER/SUPPLIER IDENTIFIER	S/4 HANA	LFM1	FSH_SC_CID	CUSTOMER/SUPPLIER IDENTIFIER	Not Used
60	PF2/WP2	LFM1	FSH_VAS_DETC	VAS DETERMINATION MODE	S/4 HANA	LFM1	FSH_VAS_DETC	VAS DETERMINATION MODE	Not Used
61	PF2/WP2	LFM1	UPPRS	PRICING ON SUBITEMS (MPN/SUS)	S/4 HANA	LFM1	UPPRS	PRICING ON SUBITEMS (MPN/SUS)	Not Used
62	PF2/WP2	LFM1	ACTIVITY_PROFIL	ACTIVITY PROFILE FOR PO CONTROLLING	S/4 HANA	LFM1	ACTIVITY_PROFIL	ACTIVITY PROFILE FOR PO CONTROLLING	Not Used
63	PF2/WP2	LFM1	TRANSPORT_CHAIN	TRANSPORTATION CHAIN	S/4 HANA	LFM1	TRANSPORT_CHAIN	TRANSPORTATION CHAIN	Not Used
64	PF2/WP2	LFM1	STAGING_TIME	STAGING TIME IN DAYS	S/4 HANA	LFM1	STAGING_TIME	STAGING TIME IN DAYS	Not Used
65	PF2/WP2	LFM1	EXPVZ	MODE OF TRANSPORT AT THE BORDER (INTRAST	S/4 HANA	LFM1	EXPVZ	MODE OF TRANSPORT AT THE BORDER (INTRAST	Not Used
66	PF2/WP2	LFM1	VENSL	SUPPLIER SERVICE LEVEL	S/4 HANA	LFM1	VENSL	SUPPLIER SERVICE LEVEL	Not Used
67	PF2/WP2	LFM1	LEBRE	SERVICE - BASED INVOICE VERIFICATION	S/4 HANA	LFM1	LEBRE	SERVICE - BASED INVOICE VERIFICATION	Required (Not in LTMC - S/4 HANA Template) Default to 'X'
68	PF2/WP2	LFM1	UMSAE	COMPARISON AND AGREEMENT OF BUSINESS VOLUMES	S/4 HANA	LFM1	UMSAE	COMPARISON AND AGREEMENT OF BUSINESS VOLUMES	Not Used
69	PF2/WP2	LFM1	WEORA	ORIGIN ACCEPTANCE	S/4 HANA	LFM1	WEORA	ORIGIN ACCEPTANCE	Not Used Direct Mapping (Flag X/blank)* whether goods must be formally accepted at the place of origin (i.e., the vendor’s or manufacturer’s site) before they are shipped to you. Flag is based on vendor specific information captured.
*70	PF2/WP2	LFM1	ZZR_ZLATR9	Attribute 9	S/4 HANA	LFM1	ZZ_DGID	DG identification	Conditional Carrier Business Partner Identifier to capture the carrier authorization/capability to transport Dangerous Goods in the master data.* An identifier should be maintained at the supplier purchase organization and carrier level with possible values: ZDG, ZXC, BLANK, High Consequence. It will be located at: At Purchase Organization level --> Purchasing Data tab ---> Control Data section in both Roles. Name of the field: “DG identification”, dropdown list field. Possible values: 01. DG 02. Non-DG 03. DG Exempted 04. High Consequence
71	PF2/WP2	LFM2	LIFNR	VENDOR NUMBER	S/4 HANA	LFMLFM12	LIFNR	SUPPLIER NUMBER	XREF Derive via legacy to SyWay S4 Business Partner mapping Supplier (BP code) Automatically created by the system. for Plant level Purchasing data to be populated in LFM2 : 1) Plant-level flag should be ticked 2) VSR flag should be maintained - Please check
72	PF2/WP2	LFM2	EKORG	PURCHASING ORGANISATION	S/4 HANA	LFM2	EKORG	PURCHASING ORGANISATION	XREF Derive via legacy to SyWay S4 Purchasing Organization mapping It is validated against relevant Purchase Organizations available in S/4 HANA. Customizing. Values of the Purchase Organizations already included in the "MM configuration values document"- Enterprise Structure tab.
73	PF2/WP2	LFM2	LTSNR	SUPPL. SUBRANGE	S/4 HANA	LFM2	LTSNR	SUPPL. SUBRANGE	Required Default value is " "
74	PF2/WP2	LFM2	WERKS	PLANT*	S/4 HANA	LFM2	WERKS	PLANT*	Required Key that uniquely identifies a plant. GENERAL RULE: All the fields equal to the fields coming from LFM1 (the only one field that could be different is "Customs Office: Office of Exit/Entry for Foreign Trade (LFM2- ZOLLA)
75	PF2/WP2	WRF02K(TBC)	HINZE	Indicator: plant level relevant - Purchasing Data	S/4 HANA	WRF02K(TBC)	HINZE	Indicator: plant level relevant - Purchasing Data	Required For Plant level Purchasing data to be populated in LFM2 - Indicator: plant level relevant - Purchasing Flag should be ticked ("X")
76	PF2/WP2	WRF02K(TBC)	HINZP	Indicator: plant level relevant - Partner Functions	S/4 HANA	WRF02K(TBC)	HINZP	Indicator: plant level relevant - Partner Functions	Required For Plant level Purchasing data to be populated in LFM2 - Indicator: plant level relevant - Partner Functions Flag should be ticked ("X")
77	PF2/WP2	LFM2	EKGRP	PURCHASING GROUP	S/4 HANA	LFM2	EKGRP	PURCHASING GROUP	XREF Derive via legacy to SyWay S4 Purchasing Group mapping It is validated against relevant Purchasing Groups available in S/4 HANA.
78	PF2/WP2	LFM2	WAERS	ORDER CURRENCY	S/4 HANA	LFM2	WAERS	ORDER CURRENCY	XREF Derive via legacy to SyWay S4 Purchasing Currency code mapping In the PO - in case we have PIR/CTR will come from here. Otherwise, it will take it from the BP.* In BP Plants (Account group= ZICP) no contracts will be used, so the value comes from the BP itself.
79	PF2/WP2	LFM2	VERKF	SALESPERSON	S/4 HANA	LFM2	VERKF	SALESPERSON	Not Used It is free text in S4HANA.
80	PF2/WP2	LFM2	TELF1	TELEPHONE	S/4 HANA	LFM2	TELF1	TELEPHONE	Not Used
81	PF2/WP2	LFM2	MINBW	MINIMUM ORDER VALUE	S/4 HANA	LFM2	MINBW	MINIMUM ORDER VALUE	Not Used
82	PF2/WP2	LFM2	ZTERM	PAYMENT TERMS	S/4 HANA	LFM2	ZTERM	PAYMENT TERMS	XREF Values of the payment terms already included in the "MM configuration values document"- BP Suppliers tab: In the PO - in case we have PIR/CTR will come from here. Otherwise, it will take it from the BP.* In BP Plants/IC suppliers (Account group= ZICP) no contracts will be used, so the value comes from the BP itself.
83	PF2/WP2	LFM2	INCOV	INCO VERSION	S/4 HANA	LFM2	INCOV	INCO VERSION	Not Used
84	PF2/WP2	LFM2	INCO1	INCOTERMS	S/4 HANA	LFM2	INCO1	INCOTERMS	XREF Derive via legacy to SyWay S4 Incoterms mapping Customizing. Values of the Inco terms already included in the "MM configuration values document"- BP Suppliers tab: Set as Conditional because it must be mandatory only for the BPs that trigger Transportation module. The BP subjected to TM must have it as mandatory (as this field should be inherited to the corresponding POs) Fill always when the BP has Carrier Role (CRM010) *will reuse it for the process Otherwise, blank
*85	PPF2/WP2	N/A	N/A	Identifier for Incoterm Location 1	S/4 HANA	TMINCO_LOC_DATA	INCO2_ID	Identifier for Incoterm Location 1	XREF Derive via legacy to SyWay S4 Incoterms Location mapping INCO2_ID Mandatory and INCO2_L automatically updated from (INCO2_ID) and not editable
86	PF2/WP2	LFM2	INCO2_L	INCOTERMS LOCATION 1	S/4 HANA	LFM2	INCO2_L	INCOTERMS LOCATION 1	*System Generated INCO2_ID Mandatory and INCO2_L automatically updated from (INCO2_ID) and not editable
87	PF2/WP2	LFM2	KALSK	SCHEMA GROUP SUPPLIER	S/4 HANA	LFM2	KALSK	SCHEMA GROUP SUPPLIER	XREF Values of the Calculation Schemas already included in the "MM configuration values document"- BP Suppliers tab: There are 3 Schema Group Values: 01 Default vendor schema group - when (Grouping BP02/Account Group: LIEF) + (Employee vendors (Grouping: BPEE))* 02 Vendor schema group Intercomp - for BP Plants (Account Group = ZICP) 03 Schema Group for TM - when the BP has Carrier Role (CRM010) Equal than at Purchas. Organ. level.(table LFM1 -inherited)
88	PF2/WP2	LFM2	PLIFZ	PLANNED DELIVERY TIME	S/4 HANA	LFM2	PLIFZ	PLANNED DELIVERY TIME	Not Used
89	PF2/WP2	LFM2	LFABC	ABC INDICATOR	S/4 HANA	LFM2	LFABC	ABC INDICATOR	Not used A-Category A (high-value, most critical): The smallest number of suppliers that account for a large portion of the total spend (e.g., 10-20% of suppliers representing 70-80% of value). B-Category B (medium-value): The middle group, with moderate spend and value. C-Category C (low-value, least critical) : The largest group of suppliers that represent a small portion of the total spend.
90	PF2/WP2	LFM2	WEBRE	GR-BASED INVOICE VERIFICATION	S/4 HANA	LFM2	WEBRE	GR-BASED INVOICE VERIFICATION	Conditional By default always flag (X), exception for Grouping BPAB/Account Group = LIEF (BP Plants) that should be blank. *Exception for BP Plants: (Account Group = ZICP) that should be blank.
91	PF2/WP2	LFM2	KZAUT	AUTOMATIC PURCHASE ORDER	S/4 HANA	LFM2	KZAUT	AUTOMATIC PURCHASE ORDER	Required By default always flag (X), exception: Suppliers with Carrier role (CRM010) AND in BP Plants (Account Group = ZICP)) - Flagged X when the STO is created automatically from the STR (Advance IC Stock transfer - STO type: NBIC Advance IC Transfer) Otherwise: Blank*
92	PF2/WP2	LFM2	MEPRF	PRICING DATE CONTROL	S/4 HANA	LFM2	MEPRF	PRICING DATE CONTROL	Conditional Direct Mapping Exception Rule By default leave it blank. Possible values:* (blank/NULL) = No Control 1 = Purchase Order Date 5 = Goods Receipt Date (GR Date)
93	PF2/WP2	LFM2	BSTAE	CONFIRMATION CONTROL KEY	S/4 HANA	LFM2	BSTAE	CONFIRMATION CONTROL KEY	XREF It is validated against relevant Confirmation Control keys available in S/4 HANA. Check table T163L Rule: Values:* - 0001 - Z001 - only AB Where the Relevant scenarios for CCCK/ use case are the following: 1.- Direct(Inventory managed)/Indirect(Stocked spares) - 0001 2.- Indirect - Account assigned(Non inventory managed) - Z001 - only AB 3.- Intercompany/Intracompany-> when Grouping BPAB/Account Group: LIEF (BP Plants) - 0001 4.- Services - Z001 - only AB
94	PF2/WP2	LFM2	XERSY	AUTOM EVALUATED RECEIPT SETTLEMENT (ERS)	S/4 HANA	LFM2	XERSY	AUTOM EVALUATED RECEIPT SETTLEMENT (ERS)	Conditional, Direct Mapping It is a flag. Valid if the criteria is fit by the supplier. For the suppliers relevant to ERS - flag X Others, keep it blank. The Business could provide the list of the relevant suppliers.
95	PF2/WP2	LFM2	XERSR	AUTOM EVALUATED GR SETTLEMENT RETURN	S/4 HANA	LFM2	XERSR	AUTOM EVALUATED GR SETTLEMENT RETURN	Conditional, Direct Mapping It is a flag. Valid if the criteria is fit by the supplier. For the suppliers relevant to ERS - flag X Others, keep it blank. The Business could provide the list of the relevant suppliers.
96	PF2/WP2	LFM2	KZABS	ORDER ACKNOWLEDGMENT REQUIREMENT	S/4 HANA	LFM2	KZABS	ORDER ACKNOWLEDGMENT REQUIREMENT	Conditional By default X - *Exception: For BP Plants (Account Group = ZICP) - blank
97	PF2/WP2	LFM2	PAPRF	PROACT CONTROL PROFILE	S/4 HANA	LFM2	PAPRF	PROACT CONTROL PROFILE	Not Used
98	PF2/WP2	LFM2	BOLRE	SUBSEQUENT SETTLEMENT	S/4 HANA	LFM2	BOLRE	SUBSEQUENT SETTLEMENT	Not Used
99	PF2/WP2	LFM2	XNBWY	REVALUATION	S/4 HANA	LFM2	XNBWY	REVALUATION	Not Used
100	PF2/WP2	LFM2	PRFRE	PRICE DETERMINATION	S/4 HANA	LFM2	PRFRE	PRICE DETERMINATION	Not Used
101	PF2/WP2	LFM2	BOIND	SUBSEQUENT SETTLEMENT INDICATOR ACTIVE	S/4 HANA	LFM2	BOIND	SUBSEQUENT SETTLEMENT INDICATOR ACTIVE	Not Used
102	PF2/WP2	LFM2	LOEVM	DELETION FLAG PURCHASING ORGANIZATION	S/4 HANA	LFM2	LOEVM	DELETION FLAG PURCHASING ORGANIZATION	Not Used
103	PF2/WP2	LFM2	SPERM	SELECTED PURCHASING ORGANIZATION BLOCK	S/4 HANA	LFM2	SPERM	SELECTED PURCHASING ORGANIZATION BLOCK	Conditional (Not in LTMC - S/4 HANA Template) Set X in case block is needed for posting / purchasing purposes.
104	PF2/WP2	LFM2	MRPPP	PLANNING CALENDAR	S/4 HANA	LFM2	MRPPP	PLANNING CALENDAR	Not Used
105	PF2/WP2	LFM2	LFRHY	PLANNING CYCLE	S/4 HANA	LFM2	LFRHY	PLANNING CYCLE	Not Used
106	PF2/WP2	LFM2	BOPNR	ORDER OPTIMIZATION RESTRICTION	S/4 HANA	LFM2	BOPNR	ORDER OPTIMIZATION RESTRICTION	Not Used
107	PF2/WP2	LFM2	LIBES	ORDER ENTRY BY SUPPLIER	S/4 HANA	LFM2	LIBES	ORDER ENTRY BY SUPPLIER	Not Used
108	PF2/WP2	LFM2	LIPRE	PRICE MARKING SUPPLIER	S/4 HANA	LFM2	LIPRE	PRICE MARKING SUPPLIER	Not Used
109	PF2/WP2	LFM2	LISER	RACK JOBBING	S/4 HANA	LFM2	LISER	RACK JOBBING	Not Used
110	PF2/WP2	LFM2	ZOLLA	CUSTOMS OFFICE: OFFICE OF EXIT/ENTRY FOR FOREIGN TRADE	S/4 HANA	LFM2	ZOLLA	CUSTOMS OFFICE: OFFICE OF EXIT/ENTRY FOR FOREIGN TRADE	Conditional (Not in LTMC - S/4 HANA Template) Direct Mapping Valid for Eugenia Tataru - GTS
111	PF2/WP2	LFM2	INCO3_L	INCOTERMS LOCATION 2	S/4 HANA	LFM2	INCO3_L	INCOTERMS LOCATION 2	Not Used
112	PF2/WP2	LFM2	RDPRF	ROUNDING PROFILE	S/4 HANA	LFM2	RDPRF	ROUNDING PROFILE	Not Used
113	PF2/WP2	LFM2	MEGRU	UNIT OF MEASURE GROUP	S/4 HANA	LFM2	MEGRU	UNIT OF MEASURE GROUP	Not Used
114	PF2/WP2	LFM2	ABUEB	RELEASE CREATION PROFILE	S/4 HANA	LFM2	ABUEB	RELEASE CREATION PROFILE	Not Used
115	PF2/WP2	LFM2	TRANSPORT_CHAIN	TRANSPORTATION CHAIN	S/4 HANA	LFM2	TRANSPORT_CHAIN	TRANSPORTATION CHAIN	Not Used
116	PF2/WP2	LFM2	STAGING_TIME	STAGING TIME IN DAYS	S/4 HANA	LFM2	STAGING_TIME	STAGING TIME IN DAYS	Not Used
117	PF2/WP2	LFM2	EXPVZ	MODE OF TRANSPORT AT THE BORDER (INTRAST	S/4 HANA	LFM2	EXPVZ	MODE OF TRANSPORT AT THE BORDER (INTRAST	Not Used
118	PF2/WP2	LFM2	LEBRE	SERVICE - BASED INVOICE VERIFICATION	S/4 HANA	LFM2	LEBRE	SERVICE - BASED INVOICE VERIFICATION	Required (Not in LTMC - S/4 HANA Template) Default to 'X'
119	PF2/WP2	LFM2	UMSAE	COMPARISON AND AGREEMENT OF BUSINESS VOLUMES	S/4 HANA	LFM2	UMSAE	COMPARISON AND AGREEMENT OF BUSINESS VOLUMES	Not Used
120	PF2/WP2	LFM2	WEORA	ORIGIN ACCEPTANCE	S/4 HANA	LFM2	WEORA	ORIGIN ACCEPTANCE	Not Used Direct Mapping (Flag X/blank)* whether goods must be formally accepted at the place of origin (i.e., the vendor’s or manufacturer’s site) before they are shipped to you. Flag is based on vendor specific information captured.
121	PF2/WP2	WYT3	LIFNR	VENDOR	S/4 HANA	WYT3	LIFNR	SUPPLIER	Required *and XREF Derive via legacy to SyWay S4 Business Partner mapping Supplier (BP code) Automatically created by the system.
122	PF2/WP2	WYT3	PARVW	PARTNER FUNCTION	S/4 HANA	WYT3	PARVW	PARTNER FUNCTION	XREF Customizing. Values of the partner functions already included in the "MM configuration values document"- BP Suppliers tab: Values confirmed: VN Vendor PI Invoicing Party GS Goods supplier OA Ordering address CR Carrier CP - Contact Person ZA - TMS4S: the value will be the same Main BP code ZB - BN4L: the value will be the same Main BP code ZC - Transwide : the value will be the same Main BP code In case of CASS-> PI partner function with BP code equal to the Main BP can be used- Note: currently it will be only maintained when the email address is different in case of legal entity (Different BP code) Note: Contact person must be included in the Returns Supplier for invoicing - VIM requirement) The abbreviated form of the name that identifies the partner function. The UI the partner function is displayed language-dependent. In case BP Plants (Account Group = ZICP- PL** /PX): PLYYYY - " where YYYY is plant code/ PL = Syensqo Plant within the same instance/PXYYYY - "where YYYY is plant code/PX = Syensqo Plant in other instance" Partner Function: By default (the same as external suppliers): VN - Vendor CP - Contact Person - Warehouse manager (for Global Spares Visibility report) GS - Goods Supplier - TBD OA - Ordering address PI - Invoicing Party: "PI (invoicing party) against the Plant (PL)/Vendor CHINA (PX): ICTXXXX - ""where XXXX is company code / T = trading"" ICNXXXX - ""where XXXX is company code / N = Non Trading"""**
123	PF2/WP2	*WYT3	WERKS	Plant	S/4 HANA	WYT3	WERKS	Plant	XREF Derive via legacy to SyWay S4 Plant mapping* Not used for the vendors purchasing view (LFM1 level) related partner functions data Mandatory for the vendors plant specific purchasing view (LFM2 level) related partner functions data
124	PF2/WP2	WYT3	LIFN2	REF TO VENDOR	S/4 HANA	WYT3	LIFN2	REF TO VENDOR	XREF Derive via legacy to SyWay S4 Business Partner mapping* Fill it in case Partner function is VN, OA,PI,GS,,ZA, ZB, ZC This partner is only mandatory if you choose a partner role which refers to this partner. One of the partner fields is always mandatory.
125	PF2/WP2	WYT3	PERNR	PERSONAL NO	S/4 HANA	WYT3	PERNR	PERSONAL NO	Not Used
126	PF2/WP2	WYT3	PARNR	CONTACT PERSON	S/4 HANA	WYT3	PARNR	CONTACT PERSON	*XREF Fill it in case Partner function is CP
127	PF2/WP2	WYT3	DEFPA	DEFAULT PARTNER	S/4 HANA	WYT3	DEFPA	DEFAULT PARTNER	Conditional Direct mapping *Specifies a partner as the default for a particular partner function. This is an indicator field. If the criterion is met, enter X. If not, leave the field empty.
128	PF2/WP2	WYT3	EKORG	PURCHASING ORGANIZATION	S/4 HANA	WYT3	EKORG	PURCHASING ORGANIZATION	XREF Derive via legacy to SyWay S4 Purchasing Organization mapping Values of the Purchase Organizations already included in the "MM configuration values document"- Enterprise Structure tab:
129	PF2/WP2	WYT3	LTSNR	Supplier Subrange	S/4 HANA	WYT3	LTSNR	Supplier Subrange	Not used
130	PF2/WP2	WYT3	WERKS	Plant	S/4 HANA	WYT3	WERKS	Plant	Not used
*131	WP2/PF2	STXH	TDOBJECT	Text object	S/4 HANA	STXH	TDOBJECT	Text object	Required Keep legacy value = LFM1
132	WP2/PF2	STXH	TDNAME	Text Name	S/4 HANA	STXH	TDNAME	Text Name	Required Derive via legacy to BP Master Mapping (leading zero within 10 chars) concatenate with Purchasing Organization mapping (4 chars)
133	WP2/PF2	STXH	TDID	Text ID	S/4 HANA	STXH	TDID	Text ID	Required Keep legacy value
134	WP2/PF2	STXH	TDSPRAS	Language Key	S/4 HANA	STXH	TDSPRAS	Language Key	Required Keep legacy value
135	WP2/PF2	STXL	TDOBJECT	Text object	S/4 HANA	STXL	TDOBJECT	Text object	Required Keep legacy value = LFM1
136	WP2/PF2	STXL	TDNAME (Concatenation of LIFNR and EKORG)	Text Name (Concatenation of Vendor number and Purchasing Organization)	S/4 HANA	STXL	TDNAME (Concatenation of LIFNR and EKORG)	Text Name (Concatenation of Vendor number and Purchasing Organization)	Required Derive via legacy to BP Master Mapping (leading zero within 10 chars) concatenate with Purchasing Organization mapping (4 chars)
137	WP2/PF2	STXL	TDID	Text ID	S/4 HANA	STXL	TDID	Text ID	Required Keep legacy value
138	WP2/PF2	STXL	TDSPRAS	Language Key	S/4 HANA	STXL	TDSPRAS	Language Key	Required Keep legacy value BG - Bulgarian, DE - German, EN - English, ES - Spanish, FI - Finnish, FR - French, IT - Italian, JA - Japanese, KO - Korean, NL - Dutch, PL - Polish, PT - Portuguese, RU - Russian, TH- Thai, ZF - Chinese traditional, ZH - Mandarin, SK - Slovak
139	WP2/PF2	STXL	CLUSTD	Data - SAPscript: LONG RAW field for table STXL	S/4 HANA	STXL	CLUSTD	Data - SAPscript: LONG RAW field for table STXL	Required Keep legacy value No special characters: ; Semi-colon : Colon :: Double Colon ? Question Mark / Forward Slash @ At sign & Ampersand = Equal Sign + Plus Sign $ Dollar Sign % Percent \| Vertical Bar [] Left or Right Square Bracket " Double Quotes

DCT Build Tables including the transformation logic:

Target Ready Data Collection Template will be created for the Vendors Purchasing Organization:

Rule #	Source system	Source Table	Source Field	Source Description	Target System	Target Table	Target Field	Target Description	Transformation Logic
1	DCT	DCT	LIFNR	VENDOR NUMBER	S/4 HANA	LFM1	LIFNR	SUPPLIER NUMBER	XREF Derive via legacy to SyWay S4 Business Partner mapping Supplier (BP code) Automatically created by the system.
2	DCT	DCT	EKORG	PURCHASING ORGANISATION	S/4 HANA	LFM1	EKORG	PURCHASING ORGANISATION	XREF
									Derive via legacy to SyWay S4 Purchasing Organization mapping
									It is validated against relevant Purchase Organizations available in S/4 HANA. Customizing.
									Values of the Purchase Organizations already included in the "MM configuration values document"- Enterprise Structure tab.
3	DCT	DCT	EKGRP	PURCHASING GROUP	S/4 HANA	LFM1	EKGRP	PURCHASING GROUP	XREF
									Derive via legacy to SyWay S4 Purchasing Group mapping
									It is validated against relevant Purchasing Groups available in S/4 HANA.
4	DCT	DCT	WAERS	ORDER CURRENCY	S/4 HANA	LFM1	WAERS	ORDER CURRENCY	XREF
4	DCT	DCT	WAERS	ORDER CURRENCY	S/4 HANA	LFM1	WAERS	ORDER CURRENCY	Derive via legacy to SyWay S4 Purchasing Currency code mapping
5	DCT	DCT	ZTERM	PAYMENT TERMS	S/4 HANA	LFM1	ZTERM	PAYMENT TERMS	XREF
									Values of the payment terms already included in the "MM configuration values document"- BP Suppliers tab:
									In the PO - in case we have PIR/CTR will come from here.
									Otherwise, it will take it from the BP. S4HANA.
6	DCT	DCT	INCO1	INCOTERMS	S/4 HANA	LFM1	INCO1	INCOTERMS	XREF
									Derive via legacy to SyWay S4 Incoterms mapping
									Customizing. Values of the payment terms already included in the "MM configuration values document"- BP Suppliers tab:
									Set as Conditional because it must be mandatory only for the BPs that trigger Transportation module. The BP subjected to TM must have it as mandatory (as this field should be inherited to the corresponding POs)
									Fill always when the BP has Carrier Role (CRM010)
									Otherwise, blank
*7	DCT	DCT	DCT	Identifier for Incoterm Location 1	S/4 HANA	TMINCO_LOC_DATA	INCO2_ID	Identifier for Incoterm Location 1	XREF Derive via legacy to SyWay S4 Incoterms Location mapping INCO2_ID Mandatory and INCO2_L automatically updated from (INCO2_ID) and not editable
8	DCT	DCT	INCO2_L	INCOTERMS LOCATION 1	S/4 HANA	LFM1	INCO2_L	INCOTERMS LOCATION 1	*System Generated
									Derive via legacy to SyWay S4 Incoterms Location mapping
									Conditional. It is validated against relevant Incoterms available in S/4 HANA. Customizing. Values of the payment terms already included in the "MM configuration values document"- BP Suppliers tab:
									Fill always when the BP has Carrier Role (CRM010)
									Otherwise, blank
									Logic:
									If LFM1-INCO1 (incoterms)=
									CFR
									CIF
									CIP
									CPT
									FOB
									INCO2_ID Mandatory and INCO2_L automatically updated from (INCO2_ID) and not editable
9	DCT	DCT	KALSK	SCHEMA GROUP SUPPLIER	S/4 HANA	LFM1	KALSK	SCHEMA GROUP SUPPLIER	XREF
									Values of the Calculation Schemas already included in the "MM configuration values document"- BP Suppliers tab:
									There are 3 pricing procedures:
									01 Default vendor schema group
									02 Vendor schema group Intercomp
									03 Schema Group for TM
									Based on the supplier the pricing procedure will be determined.
10	DCT	DCT	VSBED	SHIPPING CONDITIONS	S/4 HANA	LFM1	VSBED	SHIPPING CONDITIONS	XREF
									Values of the shipping conditions should be included in the "SD configuration values document"
									Conditional for the relevant for TM (01- Sea/02-Sea FCL/03-Air/04-Road/05-Road FTL/06- Rail/07- Customer Collection/08- Parcel Standard/10-Parcel Express)
									Others (09- Non TM) - blank.
									Set as Conditional because it must be mandatory only for the BPs that trigger Transportation module. The BP subjected to TM must have it as mandatory (as this field should be inherited to the corresponding POs)
									General shipping strategy for the delivery of goods from the supplier to the customer.
11	DCT	DCT	WEBRE	GR-BASED INVOICE VERIFICATION	S/4 HANA	LFM1	WEBRE	GR-BASED INVOICE VERIFICATION	Conditional
11	DCT	DCT	WEBRE	GR-BASED INVOICE VERIFICATION	S/4 HANA	LFM1	WEBRE	GR-BASED INVOICE VERIFICATION	By default always flag (X), exception for Grouping BPAB/Account Group = LIEF (BP Plants) that should be blank.
12	DCT	DXT	KZAUT	AUTOMATIC PURCHASE ORDER	S/4 HANA	LFM1	KZAUT	AUTOMATIC PURCHASE ORDER	Required
									By default always flag (X), exception: Suppliers with Carrier role (CRM010) AND Grouping BPAB/Account Group: LIEF (BP Plants) - that should be blank
									It is a flag. Always X.
									PO creation without a previous PR is only in TM (supplier has the carrier role) and IC SO (supplier is a plant)
13	DCT	DCT	MEPRF	PRICING DATE CONTROL	S/4 HANA	LFM1	MEPRF	PRICING DATE CONTROL	Conditional
13	DCT	DCT	MEPRF	PRICING DATE CONTROL	S/4 HANA	LFM1	MEPRF	PRICING DATE CONTROL	Direct Mapping
14	DCT	DCT	BSTAE	CONFIRMATION CONTROL KEY	S/4 HANA	LFM1	BSTAE	CONFIRMATION CONTROL KEY	XREF
14	DCT	DCT	BSTAE	CONFIRMATION CONTROL KEY	S/4 HANA	LFM1	BSTAE	CONFIRMATION CONTROL KEY	Valid if the criteria is fit by the supplier. Depending on the way of working (order acknowledgment, shipping notification) of the vendor (few filled in ECC) Rule: Values: - 0001 - ASN and OA* - Z001 - Only OA - Z002 - Intercompany Where the Relevant scenarios for CCCK/ user case are the following: 0001 - Suppliers who will be sending ASN and OA both, Used in Direct procurement, Indirect procurement scenarios. Z002 - Intercompany processes Z001 - Suppliers who will only send OA, Used in Service Procurement
15	DCT	DCT	KZRET	RETURNS SUPPLIER	S/4 HANA	LFM1	KZRET	RETURNS SUPPLIER	Conditional , Direct Mapping
									By default X for all suppliers that supply products.
									Additionally: the customer master record must exists in the system (customer roles) AND the "customer reference" field filled at General Data role.
16	DCT	DCT	XERSY	AUTOM EVALUATED RECEIPT SETTLEMENT (ERS)	S/4 HANA	LFM1	XERSY	AUTOM EVALUATED RECEIPT SETTLEMENT (ERS)	Conditional, Direct Mapping
									It is a flag. Valid if the criteria is fit by the supplier.
									For the suppliers relevant to ERS - flag X
									Others, keep it blank.
									The Business could provide the list of the relevant suppliers.
17	DCT	DCT	XERSR	AUTOM EVALUATED GR SETTLEMENT RETURN	S/4 HANA	LFM1	XERSR	AUTOM EVALUATED GR SETTLEMENT RETURN	Conditional, Direct Mapping
									It is a flag. Valid if the criteria is fit by the supplier.
									For the suppliers relevant to ERS - flag X
									Others, keep it blank.
									The Business could provide the list of the relevant suppliers.
18	DCT	DCT	KZABS	ORDER ACKNOWLEDGMENT REQUIREMENT	S/4 HANA	LFM1	KZABS	ORDER ACKNOWLEDGMENT REQUIREMENT	Conditional
18	DCT	DCT	KZABS	ORDER ACKNOWLEDGMENT REQUIREMENT	S/4 HANA	LFM1	KZABS	ORDER ACKNOWLEDGMENT REQUIREMENT	By default X - exception Plants (Grouping BPAB/Account Group = LIEF)
19	DCT	DCT	BLIND	DOCUMENT INDEX	S/4 HANA	LFM1	BLIND	DOCUMENT INDEX	TBD
20	DCT	DCT	SPERM	SELECTED PURCHASING ORGANIZATION BLOCK	S/4 HANA	LFM1	SPERM	SELECTED PURCHASING ORGANIZATION BLOCK	Conditional (Not in LTMC - S/4 HANA Template)
20	DCT	DCT	SPERM	SELECTED PURCHASING ORGANIZATION BLOCK	S/4 HANA	LFM1	SPERM	SELECTED PURCHASING ORGANIZATION BLOCK	Set X in case block is needed for posting / purchasing purposes.
21	DCT	DCT	ZOLLA	CUSTOMS OFFICE: OFFICE OF EXIT/ENTRY FOR FOREIGN TRADE	S/4 HANA	LFM1	ZOLLA	CUSTOMS OFFICE: OFFICE OF EXIT/ENTRY FOR FOREIGN TRADE	Conditional (Not in LTMC - S/4 HANA Template)
									Direct Mapping
									Valid for Eugenia Tataru - GTS
22	DCT	DCT	J_1NBOESL	EXCHANGE KEY FOR NF PROCESSING	S/4 HANA	LFM1	J_1NBOESL	EXCHANGE KEY FOR NF PROCESSING	Not Used
22	DCT	DCT	J_1NBOESL	EXCHANGE KEY FOR NF PROCESSING	S/4 HANA	LFM1	J_1NBOESL	EXCHANGE KEY FOR NF PROCESSING	Direct Mapping
23	DCT	DCT	LEBRE	SERVICE - BASED INVOICE VERIFICATION	S/4 HANA	LFM1	LEBRE	SERVICE - BASED INVOICE VERIFICATION	Required (Not in LTMC - S/4 HANA Template)
23	DCT	DCT	LEBRE	SERVICE - BASED INVOICE VERIFICATION	S/4 HANA	LFM1	LEBRE	SERVICE - BASED INVOICE VERIFICATION	Default to 'X'
*24	DCT	DCT	WEORA	Origin acceptance	S/4 HANA	LFM1	WEORA	Origin acceptance	Not Used Direct Mapping (Flag X/blank)* whether goods must be formally accepted at the place of origin (i.e., the vendor’s or manufacturer’s site) before they are shipped to you. Flag is based on vendor specific information captured.
*24	DCT	DCT	WEORA	Origin acceptance	S/4 HANA	LFM1
*25	DCT	DCT	ZZR_ZLATR9	Attribute 9	S/4 HANA	LFM1	ZZ_DGID	DG identification	Conditional Carrier Business Partner Identifier to capture the carrier authorization/capability to transport Dangerous Goods in the master data. An identifier should be maintained at the supplier purchase organization and carrier level with possible values: ZDG, ZXC, BLANK, High Consequence. It will be located at: At Purchase Organization level --> Purchasing Data tab ---> Control Data section in both Roles. Name of the field: “DG identification”, dropdown list field. Possible values: 01. DG 02. Non-DG 03. DG Exempted 04. High Consequence
*25	DCT	DCT			S/4 HANA	LFM1

.Target Ready Data Collection Template will be created for the Vendors Purchasing Organization Partner Functions::

Rule #	Source system	Source Table	Source Field	Source Description	Target System	Target Table	Target Field	Target Description	Transformation Logic
1	DCT	DCT	LIFNR	VENDOR	S/4 HANA	WYT3	LIFNR	SUPPLIER	Required
									Derive via legacy to SyWay S4 Business Partner mapping
									Supplier (BP code) Automatically created by the system.
2	DCT	DCT	EKORG	PURCHASING ORGANIZATION	S/4 HANA	WYT3	EKORG	PURCHASING ORGANIZATION	Required
									Derive via legacy to SyWay S4 Purchasing Organization mapping
									Values of the Purchase Organizations already included in the "MM configuration values document"- Enterprise Structure tab:
3	PF2/WP2	WYT3	PARVW	PARTNER FUNCTION	S/4 HANA	WYT3	PARVW	PARTNER FUNCTION	XREF Customizing. Values of the partner functions already included in the "MM configuration values document"- BP Suppliers tab: Values confirmed: VN Vendor PI Invoicing Party GS Goods supplier OA Ordering address CR - Carrier *CP - Contact Person ZA - TMS4S: the value will be the same Main BP code ZB - BN4L: the value will be the same Main BP code ZC - Transwide : the value will be the same Main BP code In case of CASS-> PI partner function with BP code equal to the Main BP can be used- Note: currently it will be only maintained when the email address is different in case of legal entity (Different BP code) Note: Contact person must be included in the Returns Supplier for invoicing - VIM requirement) The abbreviated form of the name that identifies the partner function. The UI the partner function is displayed language-dependent.
4	DCT	DCT	LIFN2	REF TO VENDOR	S/4 HANA	WYT3	LIFN2	REF TO VENDOR	XREF Derive via legacy to SyWay S4 Business Partner mapping* Fill it in case Partner function is VN, OA,PI,GS,,ZA, ZB, ZC This partner is only mandatory if you choose a partner role which refers to this partner. One of the partner fields is always mandatory.
5	DCT	DCT	PARNR	CONTACT PERSON	S/4 HANA	WYT3	PARNR	CONTACT PERSON	*XREF
5	DCT	DCT	PARNR	CONTACT PERSON	S/4 HANA	WYT3	PARNR	CONTACT PERSON	Fill it in case Partner function is CP
6	DCT	DCT	DEFPA	DEFAULT PARTNER	S/4 HANA	WYT3	DEFPA	DEFAULT PARTNER	Conditional
6	DCT	DCT	DEFPA	DEFAULT PARTNER	S/4 HANA	WYT3	DEFPA	DEFAULT PARTNER	Direct mapping

Target Ready Data Collection Template will be created for the Vendors Plant Specific Purchasing Organization:

Rule #	Source system	Source Table	Source Field	Source Description	Target System	Target Table	Target Field	Target Description	Transformation Logic
1	DCT	DCT	LIFNR	VENDOR NUMBER	S/4 HANA	LFM2	LIFNR	SUPPLIER NUMBER	XREF
									Derive via legacy to SyWay S4 Business Partner mapping
									Supplier (BP code) Automatically created by the system.
2	DCT	DCT	EKORG	PURCHASING ORGANISATION	S/4 HANA	LFM2	EKORG	PURCHASING ORGANISATION	XREF
									Derive via legacy to SyWay S4 Purchasing Organization mapping
									It is validated against relevant Purchase Organizations available in S/4 HANA. Customizing.
									Values of the Purchase Organizations already included in the "MM configuration values document"- Enterprise Structure tab.
3	DCT	DCT	LTSNR	SUPPL. SUBRANGE	S/4 HANA	LFM2	LTSNR	SUPPL. SUBRANGE	Required
3	DCT	DCT	LTSNR	SUPPL. SUBRANGE	S/4 HANA	LFM2	LTSNR	SUPPL. SUBRANGE	Default value is " "
4	DCT	DCT	WERKS	PLANT*	S/4 HANA	LFM2	WERKS	PLANT*	Required
									Key that uniquely identifies a plant.
									GENERAL RULE: All the fields equal to the fields coming from LFM1 (the only one field that could be different is "Customs Office: Office of Exit/Entry for Foreign Trade (LFM2- ZOLLA)
5	DCT	DCT	HINZE	Indicator: plant level relevant - Purchasing Data	S/4 HANA	WRF02K	HINZE	Indicator: plant level relevant - Purchasing Data	Required
5	DCT	DCT	HINZE	Indicator: plant level relevant - Purchasing Data	S/4 HANA	WRF02K	HINZE	Indicator: plant level relevant - Purchasing Data	For Plant level Purchasing data to be populated in LFM2 - Indicator: plant level relevant - Purchasing Flag should be ticked ("X")
6	DCT	DCT	HINZP	Indicator: plant level relevant - Partner Functions	S/4 HANA	WRF02K	HINZP	Indicator: plant level relevant - Partner Functions	Required
6	DCT	DCT	HINZP	Indicator: plant level relevant - Partner Functions	S/4 HANA	WRF02K	HINZP	Indicator: plant level relevant - Partner Functions	For Plant level Purchasing data to be populated in LFM2 - Indicator: plant level relevant - Partner Functions Flag should be ticked ("X")
									It is validated against relevant Purchasing Groups available in S/4 HANA.
7	DCT	DCT	WAERS	ORDER CURRENCY	S/4 HANA	LFM2	WAERS	ORDER CURRENCY	XREF
7	DCT	DCT	WAERS	ORDER CURRENCY	S/4 HANA	LFM2	WAERS	ORDER CURRENCY	Derive via legacy to SyWay S4 Purchasing Currency code mapping
8	DCT	DCT	ZTERM	PAYMENT TERMS	S/4 HANA	LFM2	ZTERM	PAYMENT TERMS	XREF
									Values of the payment terms already included in the "MM configuration values document"- BP Suppliers tab:
									In the PO - in case we have PIR/CTR will come from here.
									Otherwise, it will take it from the BP. S4HANA.
9	DCT	DCT	INCO1	INCOTERMS	S/4 HANA	LFM2	INCO1	INCOTERMS	XREF
									Derive via legacy to SyWay S4 Incoterms mapping
									Customizing. Values of the payment terms already included in the "MM configuration values document"- BP Suppliers tab:
									Set as Conditional because it must be mandatory only for the BPs that trigger Transportation module. The BP subjected to TM must have it as mandatory (as this field should be inherited to the corresponding POs)
									Fill always when the BP has Carrier Role (CRM010)
									Otherwise, blank
*10	DCT	DCT	DCT	Identifier for Incoterm Location 1	S/4 HANA	TMINCO_LOC_DATA	INCO2_ID	Identifier for Incoterm Location 1	XREF Derive via legacy to SyWay S4 Incoterms Location mapping INCO2_ID Mandatory and INCO2_L automatically updated from (INCO2_ID) and not editable
11	DCT	DCT	INCO2_L	INCOTERMS LOCATION 1	S/4 HANA	LFM2	INCO2_L	INCOTERMS LOCATION 1	*System Generated
									Derive via legacy to SyWay S4 Incoterms Location mapping
									Conditional. It is validated against relevant Incoterms available in S/4 HANA. Customizing. Values of the payment terms already included in the "MM configuration values document"- BP Suppliers tab:
									Fill always when the BP has Carrier Role (CRM010)
									Otherwise, blank
									Logic:
									If LFM1-INCO1 (incoterms)=
									CFR
									CIF
									CIP
									CPT
									FOB
									INCO2_ID Mandatory and INCO2_L automatically updated from (INCO2_ID) and not editable
12	DCT	DCT	KALSK	SCHEMA GROUP SUPPLIER	S/4 HANA	LFM2	KALSK	SCHEMA GROUP SUPPLIER	XREF
									Values of the Calculation Schemas already included in the "MM configuration values document"- BP Suppliers tab:
									There are 3 pricing procedures:
									01 Default vendor schema group
									02 Vendor schema group Intercomp
									03 Schema Group for TM
									Based on the supplier the pricing procedure will be determined.
13	DCT	DCT	WEBRE	GR-BASED INVOICE VERIFICATION	S/4 HANA	LFM2	WEBRE	GR-BASED INVOICE VERIFICATION	Conditional
13	DCT	DCT	WEBRE	GR-BASED INVOICE VERIFICATION	S/4 HANA	LFM2	WEBRE	GR-BASED INVOICE VERIFICATION	By default always flag (X), exception for Grouping BPAB/Account Group = LIEF (BP Plants) that should be blank.
14	DCT	DXT	KZAUT	AUTOMATIC PURCHASE ORDER	S/4 HANA	LFM2	KZAUT	AUTOMATIC PURCHASE ORDER	Required
									By default always flag (X), exception: Suppliers with Carrier role (CRM010) AND Grouping BPAB/Account Group: LIEF (BP Plants) - that should be blank
									It is a flag. Always X.
									PO creation without a previous PR is only in TM (supplier has the carrier role) and IC SO (supplier is a plant)
15	DCT	DCT	MEPRF	PRICING DATE CONTROL	S/4 HANA	LFM2	MEPRF	PRICING DATE CONTROL	Conditional
15	DCT	DCT	MEPRF	PRICING DATE CONTROL	S/4 HANA	LFM2	MEPRF	PRICING DATE CONTROL	Direct Mapping
16	DCT	DCT	BSTAE	CONFIRMATION CONTROL KEY	S/4 HANA	LFM2	BSTAE	CONFIRMATION CONTROL KEY	XREF
16	DCT	DCT	BSTAE	CONFIRMATION CONTROL KEY	S/4 HANA	LFM2	BSTAE	CONFIRMATION CONTROL KEY	Valid if the criteria is fit by the supplier. Depending on the way of working (order acknowledgment, shipping notification) of the vendor (few filled in ECC) Rule: Values: - 0001 - ASN and OA* - Z001 - Only OA - Z002 - Intercompany Where the Relevant scenarios for CCCK/ user case are the following: 0001 - Suppliers who will be sending ASN and OA both, Used in Direct procurement, Indirect procurement scenarios. Z002 - Intercompany processes Z001 - Suppliers who will only send OA, Used in Service Procurement
17	DCT	DCT	XERSY	AUTOM EVALUATED RECEIPT SETTLEMENT (ERS)	S/4 HANA	LFM2	XERSY	AUTOM EVALUATED RECEIPT SETTLEMENT (ERS)	Conditional, Direct Mapping
									It is a flag. Valid if the criteria is fit by the supplier.
									For the suppliers relevant to ERS - flag X
									Others, keep it blank.
									The Business could provide the list of the relevant suppliers.
18	DCT	DCT	XERSR	AUTOM EVALUATED GR SETTLEMENT RETURN	S/4 HANA	LFM2	XERSR	AUTOM EVALUATED GR SETTLEMENT RETURN	Conditional, Direct Mapping
									It is a flag. Valid if the criteria is fit by the supplier.
									For the suppliers relevant to ERS - flag X
									Others, keep it blank.
									The Business could provide the list of the relevant suppliers.
19	DCT	DCT	KZABS	ORDER ACKNOWLEDGMENT REQUIREMENT	S/4 HANA	LFM2	KZABS	ORDER ACKNOWLEDGMENT REQUIREMENT	Conditional
19	DCT	DCT	KZABS	ORDER ACKNOWLEDGMENT REQUIREMENT	S/4 HANA	LFM2	KZABS	ORDER ACKNOWLEDGMENT REQUIREMENT	By default X - exception Plants (Grouping BPAB/Account Group = LIEF)
20	DCT	DCT	SPERM	SELECTED PURCHASING ORGANIZATION BLOCK	S/4 HANA	LFM2	SPERM	SELECTED PURCHASING ORGANIZATION BLOCK	Conditional (Not in LTMC - S/4 HANA Template)
20	DCT	DCT	SPERM	SELECTED PURCHASING ORGANIZATION BLOCK	S/4 HANA	LFM2	SPERM	SELECTED PURCHASING ORGANIZATION BLOCK	Set X in case block is needed for posting / purchasing purposes.
21	DCT	DCT	ZOLLA	CUSTOMS OFFICE: OFFICE OF EXIT/ENTRY FOR FOREIGN TRADE	S/4 HANA	LFM2	ZOLLA	CUSTOMS OFFICE: OFFICE OF EXIT/ENTRY FOR FOREIGN TRADE	Conditional (Not in LTMC - S/4 HANA Template)
									Direct Mapping
									Valid for Eugenia Tataru - GTS
22	DCT	DCT	LEBRE	SERVICE - BASED INVOICE VERIFICATION	S/4 HANA	LFM2	LEBRE	SERVICE - BASED INVOICE VERIFICATION	Required (Not in LTMC - S/4 HANA Template)
22	DCT	DCT	LEBRE	SERVICE - BASED INVOICE VERIFICATION	S/4 HANA	LFM2	LEBRE	SERVICE - BASED INVOICE VERIFICATION	Default to 'X'
23	DCT	DCT	WEORA	Origin acceptance	S/4 HANA	LFM2	WEORA	Origin acceptance	Not Used Direct Mapping (Flag X/blank)* whether goods must be formally accepted at the place of origin (i.e., the vendor’s or manufacturer’s site) before they are shipped to you. Flag is based on vendor specific information captured.
23	DCT	DCT	WEORA	Origin acceptance	S/4 HANA	LFM2

Target Ready Data Collection Template will be created for the Vendors Plant Specific Purchasing Organization Partner Functions::

Rule #	Source system	Source Table	Source Field	Source Description	Target System	Target Table	Target Field	Target Description	Transformation Logic
1	DCT	DCT	LIFNR	VENDOR	S/4 HANA	WYT3	LIFNR	SUPPLIER	Required
									Derive via legacy to SyWay S4 Business Partner mapping
									Supplier (BP code) Automatically created by the system.
2	DCT	DCT	EKORG	PURCHASING ORGANIZATION	S/4 HANA	WYT3	EKORG	PURCHASING ORGANIZATION	Required
									Derive via legacy to SyWay S4 Purchasing Organization mapping
									Values of the Purchase Organizations already included in the "MM configuration values document"- Enterprise Structure tab:
*3	DCT	DCT	WERKS	PLANT	S/4 HANA	WYT3	WERKS	PLANT	XREF Derive via legacy to SyWay S4 Plant mapping* Not used for the vendors purchasing view (LFM1 level) related partner functions data Mandatory for the vendors plant specific purchasing view (LFM2 level) related partner functions data
4	PF2/WP2	WYT3	PARVW	PARTNER FUNCTION	S/4 HANA	WYT3	PARVW	PARTNER FUNCTION	XREF Customizing. Values of the partner functions already included in the "MM configuration values document"- BP Suppliers tab: Values confirmed: VN Vendor PI Invoicing Party GS Goods supplier OA Ordering address CR Carrier *CP - Contact Person ZA - TMS4S: the value will be the same Main BP code ZB - BN4L: the value will be the same Main BP code ZC - Transwide : the value will be the same Main BP code In case of CASS-> PI partner function with BP code equal to the Main BP can be used- Note: currently it will be only maintained when the email address is different in case of legal entity (Different BP code) Note: Contact person must be included in the Returns Supplier for invoicing - VIM requirement) The abbreviated form of the name that identifies the partner function. The UI the partner function is displayed language-dependent.
5	DCT	DCT	LIFN2	REF TO VENDOR	S/4 HANA	WYT3	LIFN2	REF TO VENDOR	XREF Derive via legacy to SyWay S4 Business Partner mapping* Fill it in case Partner function is VN, OA,PI,GS,,ZA, ZB, ZC This partner is only mandatory if you choose a partner role which refers to this partner. One of the partner fields is always mandatory.
6	DCT	DCT	PARNR	CONTACT PERSON	S/4 HANA	WYT3	PARNR	CONTACT PERSON	*XREF
6	DCT	DCT	PARNR	CONTACT PERSON	S/4 HANA	WYT3	PARNR	CONTACT PERSON	Fill it in case Partner function is CP
7	DCT	DCT	DEFPA	DEFAULT PARTNER	S/4 HANA	WYT3	DEFPA	DEFAULT PARTNER	Conditional
7	DCT	DCT	DEFPA	DEFAULT PARTNER	S/4 HANA	WYT3	DEFPA	DEFAULT PARTNER	Direct mapping

Target Ready Data Collection Template will be created for the Vendors Purchasing Long Text:

Rule #	Source system	Source Table	Source Field	Source Description	Target System	Target Table	Target Field	Target Description	Transformation Logic
*1	DCT	DCT	TDOBJECT	Text object	S4 Hana	STXH	TDOBJECT	Text object	Not Used Keep legacy value = LFM1
2	DCT	DCT	TDNAME	Text Name	S4 Hana	STXH	TDNAME	Text Name	Not Used Derive via legacy to BP Master Mapping (leading zero within 10 chars) concatenate with Purchasing Organization mapping (4 chars)
3	DCT	DCT	TDID	Text ID	S4 Hana	STXH	TDID	Text ID	Not Used Keep legacy value
4	DCT	DCT	TDSPRAS	Language Key	S4 Hana	STXH	TDSPRAS	Language Key	Not Used Keep legacy value
5	DCT	DCT	TDOBJECT	Text object	S4 Hana	STXL	TDOBJECT	Text object	Required Default to LFM1
6	DCT	DCT	TDNAME (Concatenation of LIFNR and EKORG)	Text Name (Concatenation of Vendor Number and Purchasing Organization)	S4 Hana	STXL	TDNAME (Concatenation of LIFNR and EKORG)	Text Name (Concatenation of Vendor Number and Purchasing Organization)	Derive via legacy to BP Master Mapping (leading zero within 10 chars) concatenate with Purchasing Organization mapping (4 chars)
7	DCT	DCT	TDID	Text ID	S4 Hana	STXL	TDID	Text ID	Required
8	DCT	DCT	TDSPRAS	Language Key	S4 Hana	STXL	TDSPRAS	Language Key	Required A dropdown with the following values: BG - Bulgarian, DE - German, EN - English, ES - Spanish, FI - Finnish, FR - French, IT - Italian, JA - Japanese, KO - Korean, NL - Dutch, PL - Polish, PT - Portuguese, RU - Russian, TH- Thai, ZF - Chinese traditional, ZH - Mandarin, SK - Slovak, Z9 - Brazil Portuguese.
9	DCT	DCT	CLUSTD	Data -SAPscript: LONG RAW field for table STXL	S4 Hana	STXL	CLUSTD	Data -SAPscript: LONG RAW field for table STXL	Required No special characters: ; Semi-colon : Colon :: Double Colon ? Question Mark / Forward Slash @ At sign & Ampersand = Equal Sign + Plus Sign $ Dollar Sign % Percent \| Vertical Bar [] Left or Right Square Bracket " Double Quotes

Transformation Mapping

Value mapping tables google drive path -

Mapping Table Name	Mapping Table Description
Legacy Vendor-BP Master Mapping	XREF - Legacy to SyWay S4 Business Partner mapping
Purchasing Organization Mapping	XREF -Legacy to SyWay S4 Purchasing Organization Mapping MM Config Values.xlsx - Google Sheets
Payment Terms Mapping	XREF -Legacy to SyWay S4 Payment Terms Mapping MM Config Values.xlsx - Google Sheets
Incoterms Mapping	XREF -Legacy to SyWay S4 Incoterms Mapping MM Config Values.xlsx - Google Sheets
Identifier for Incoterm Location 1	XREF -Legacy to SyWay S4 Incoterms Location 1 Mapping MM Config Values.xlsx - Google Sheets
Purchasing Group Mapping	XREF -Legacy to SyWay S4 Purchasing Group Mapping MM Config Values.xlsx - Google Sheets
Group for Calculation Schema	XREF -Legacy to SyWay S4 Schema Group Mapping MM Config Values.xlsx - Google Sheets
Shipping Conditions	Values of the shipping conditions should be included in the "SD configuration values document"
Confirmation Control Key	XREF -Legacy to SyWay S4 Confirmation Control Key Mapping 00_R4_S2P_Process Variants Matrix.xlsx - Google Sheets
Partner Function Mapping	XREF -Legacy to SyWay S4 Partner Function Mapping MM Config Values.xlsx - Google Sheets
Purchasing Currency Code Mapping	XREF -Legacy to SyWay S4 Purchasing Currency code mapping
Plant Mapping	XREF -Legacy to SyWay S4 Plant mapping

Transformation Dependencies

List the steps that need to occur before transformation can commence

Item #	Step Description	Team Responsible
1	Extract PF2,WP2 source tables – LFM1, LFM2, WYT3	Syniti / Data Team
2	Vendor deDupe mapping (Purchasing Organization Data) -Dedupe Golden-Child (Purchasing Organization) Mapping	Syniti
3	Business Partner deDupe mapping (Global Data) - Dedupe Golden-Child (Global) mapping	Syniti
4	Ensure all vendor master data collection templates, deduplication and cleansing completeness and no errors	Syniti / Data Team
5	Ensure that Business Partner – General is loaded	Syniti
6	Ensure that all required Configurations are in S/4 HANA	Data Team
7	Source Data Integrity - Ensure extracted data is complete, accurate, and consistent. - Validate that data types and formats align with transformation requirements.5	Syniti
8	Referential Integrity - Ensure dependent records are transformed together or in advance, such as CNV-3007 Business Partner General	Syniti
9	Transformation Logic and Mapping - Define data mapping rules between source and target schemas. Value Mappings Google Drive path -	Data Team
10	Performance and Scalability Considerations - Optimize transformation processes for large datasets. - Ensure system resources can handle transformation workloads	Syniti
11	Logging and Error Handling - Maintain detailed logs of transformation activities. - Define error-handling procedures for failed transformations	Syniti

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.
Validate the mandatory fields	Validate there is value for all the mandatory fields
Validate Primary Keys and Unique Constraints	Check for duplicate or missing primary key values, i.e., if there is same BP number. Ensure unique constraints are maintained
Test Referential Integrity	Confirm dependent records exist in related tables

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.
Check Data Consistency	Compare field values across systems Validate data formats and structures

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 Scope Definition - Identify the target system and database structure. - Define data objects (tables, fields, records) to be loaded. - Establish business rules for data validation.	Data team
2	Load Methodology - Specify the loading tools and technologies (Migration Cockpit, LSMW, custom loading program).	Syniti
3	Data Quality and Validation - Ensure data integrity checks (null values, duplicates, format validation). - Perform pre-load validations to verify completeness. - Define error handling mechanisms for load failures	Syniti
4	Load Execution Plan - Establish execution timelines and batch processing schedules. - Assign responsibilities for monitoring execution. - Document dependencies on other migration tasks	Syniti
5	Logging and Reporting - Maintain detailed logs of loading activities. - Generate summary reports on loaded data volume and quality. - Define escalation procedures for errors	Syniti

Load Phase and Dependencies

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

To enable the Plant Specific Purchasing data and partner functions data at the additional data - purchasing level below are the two main conditions.
1) Plant relevant (LFA1-WERKR) flag should be ticked (field is available as part of CNV-3007)
2) VSR relevant (LFA1-LTSNA) flag should be ticked (field is available as part of CNV-3007)

Before loading, it will have dependency on the configuration.

Configuration

R4 Config Template and Config Workbook Google drive path for the reference - R4 Config Templates and Config workbooks - Google Sheets

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	LFM1-EKORG. LFM2-EKORG & WYT3-EKORG - Purchasing Organization Configuration (Check table T024E)
4	LFM1-EKGRP - Purchasing Group Configuration (Check table T024)
5	LFM1-WAERS - Order Currency Configuration (Check table TCURC)
6	LFM1-INCO1 - Incoterms Configuration (Check table TINC)
7	LFM1-KALSK - Group for Calculation Schema Configuration (Check table TMKK)
8	LFM1-VSBED - Shipping Conditions Configuration (Check table TVSB)
9	LFM1-BSTAE - Confirmation Control Key Configuration (Check table T163L)
10	LFM1- ZOLLA - Customs Office: Office of Exit/Entry for Foreign Trade (Check table T615)
11	LFM1-ZTERM - Payment Terms Configuration (Check table T052)
12	LFM2-EKGRP - Purchasing Group Configuration (Check table T024)
13	LFM2-WAERS - Order Currency Configuration (Check table TCURC)
14	LFM2-INCO1 - Incoterms Configuration (Check table TINC)
15	LFM2-KALSK - Group for Calculation Schema Configuration (Check table TMKK)
16	LFM2-VSBED - Shipping Conditions Configuration (Check table TVSB)
17	LFM2-BSTAE - Confirmation Control Key Configuration (Check table T163L)
18	LFM2- ZOLLA - Customs Office: Office of Exit/Entry for Foreign Trade (Check table T615)
19	LFM2-ZTERM - Payment Terms Configuration (Check table T052)
20	WYT3-PARVW - Partner Function Configuration (Check table TPAR)
21	WYT3-LTSNR - Supplier Subrange. Derived by the system (Check table WYT1)
22	WYT3-WERKS - Plant Configuration (Check table T001W)

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 value for the field 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	Configuration value for the field 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 PF2/WP2 or if it’s mapped in DCT.
Value Mappings (Transformation Mappings)	Missing or Invalid value mapping for the fields	If it is a missing or invalid value mapping fields then engage Functional team to expedite and fix the error in the system.
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.
Business Partner - Vendor Purchasing View including the Partner Functions Data Object is in scope based on data design and any exception requested by business.
There will be 3 SAP instances, one for ROW, one for China and one for CUI only (TBC - mentioned in the CNV 3007)
BP General data will be loaded into all 3 SAP instances. (TBC - mentioned in the CNV 3007)
This conversion Specification document is finalized based on the MDS valid on 04-Dec-2025

Purpose

Conversion Scope

Additional Information

Multi-language Requirement (TBC as this is based on the multi-language criteria from 3007-Business Partners - General (Role 000000))

Legal Requirement

Special Requirements

Target Design

Data Cleansing

Conversion Process

Extraction

Extraction Run Sheet

Selection Screen

Data Collection Template (DCT)

Extraction Dependencies

Transformation

Transformation Run Sheet

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