Status	Revision in Progress
Owner	CHAN-ext, Beng Chee MADHOK-ext, Jasleen
Stakeholders

Purpose

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

Conversion Scope

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

The data from legacy system includes:

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

The data from legacy system excludes:

Vendors blocked or marked for deletion.
Purchasing organization not in scope
Inactive vendors with no transactions for the past 2 years

List of source systems and approximate number of records

Source

Scope

Source Approx No. of Records

Target System

Target Approx

No. of Records

PF1, WP1

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

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

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

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

40,000

S/4 HANA

40,000

Additional Information

Multi-language Requirement

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

Document Management

N/A

Legal Requirement

N/A

Special Requirements

TBD

Target Design

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

The technical design of the target for this conversion approach.

Table	Field	Field Description	Requirement
LFM1	LIFNR	SUPPLIER NUMBER	R
LFM1	EKORG	PURCHASING ORGANISATION	R
LFM1	EKGRP	PURCHASING GROUP	O
LFM1	WAERS	ORDER CURRENCY	C
LFM1	VERKF	SALESPERSON	O
LFM1	TELF1	TELEPHONE	O
LFM1	MINBW	MINIMUM ORDER VALUE	O
LFM1	ZTERM	PAYMENT TERMS	C
LFM1	INCOV	INCO VERSION	O
LFM1	INCO1	INCOTERMS	C
LFM1	INCO2_L	INCOTERMS LOCATION 1	O
LFM1	INCO3_L	INCOTERMS LOCATION 2	O
LFM1	KALSK	SCHEMA GROUP SUPPLIER	O
LFM1	PLIFZ	PLANNED DELIVERY TIME	O
LFM1	LFABC	ABC INDICATOR	O
LFM1	VSBED	SHIPPING CONDITIONS	C
LFM1	WEBRE	GR-BASED INVOICE VERIFICATION	C
LFM1	KZAUT	AUTOMATIC PURCHASE ORDER	O
LFM1	MEPRF	PRICING DATE CONTROL	O
LFM1	BSTAE	CONFIRMATION CONTROL KEY	O
LFM1	KZRET	RETURNS SUPPLIER	O
LFM1	AUBEL	AUTOMATIC DEBIT	O
LFM1	VALID_PRO	SETTLEMENT PROFILE	O
LFM1	HSCABS	ABSOLUTE HANDLING SURCHARGE	O
LFM1	HSCPE	PERCENTAGE HANDLING SURCHARGE	O
LFM1	HSCMIN	MINIMUM HANDLING SURCHARGE	O
LFM1	HSCMAX	MAXIMUM HANDLING SURCHARGE	O
LFM1	XERSY	AUTOM EVALUATED RECEIPT SETTLEMENT (ERS)	C
LFM1	XERSR	AUTOM EVALUATED GR SETTLEMENT RETURN	C
LFM1	KZABS	ORDER ACKNOWLEDGMENT REQUIREMENT	C
WYT3	LIFNR	SUPPLIER	R
WYT3	EKORG	PURCHASING ORG	R
WYT3	PARVW	PARTNER FUNCTION	R
WYT3	LIFN2	REF TO VENDOR	C
WYT3	PERNR	PERSONAL NO	O
WYT3	PARNR	CONTACT PERSON	O
WYT3	DEFPA	DEFAULT PARTNER	O
Function - READ_TEXT (STHX header table)	LIFNR	SUPPLIER	R
Function - READ_TEXT (STHX header table)	EKORG	PURCHASING ORGANIZATION	R
Function - READ_TEXT (STHX header table)	TDID	TEXT ID	R
Function - READ_TEXT (STHX header table)	TEXT_TDSPRAS	LANGUAGE KEY	R
Function - READ_TEXT (STHX header table)	TEXT_LINES	TEXT	R
ADRC_NATION LENG (IAV)	LIFNR	SUPPLIER	R
ADRC_NATION LENG (IAV)	PARNR	CONTACT ID	R
ADRC_NATION		Version ID for International Addresses	R
ADRC_NATION LENG (IAV)	VNAME	FIRST NAME	O
ADRC_NATION LENG (IAV)-LNAME	LNAME	LAST NAME	O
ADRC_NATION LENG (IAV)	MIDDLE	MIDDLE NAME or SECOND FORENAME	O
ADRC_NATION LENG (IAV)-BIRTH	BIRTH	BIRTH NAME	O
ADRC_NATION LENG (IAV)	BUILDING_B	BUILDING B	O
ADRC_NATION LENG (IAV)	ROOM_B	ROOM B	O
ADRC_NATION LENG (IAV)	FLOOR_B	FLOOR B	O
ADRC_NATION LENG (IAV)	CITY	CITY	O
ADRC_NATION LENG (IAV)	STREET	STREET	O
ADRC_NATION LENG (IAV)	HOUSE_NO	HOUSE NUMBER	O
ADRC_NATION LENG (IAV)	BUILDING	BUILDING	O
ADRC_NATION LENG (IAV)	ROOM	ROOM	O
ADRC_NATION LENG (IAV)	FLOOR	FLOOR	O
FIWTIN_TAN_EXEM	ACCNO	SUPPLIER	R
FIWTIN_TAN_EXEM	BUKRS	COMPANY CODE	R
FIWTIN_TAN_EXEM	SECCODE	SECTION CODE / SECTION CODE GROUP	R
FIWTIN_TAN_EXEM	WT_EXDF	EXEMPTION FROM	O
FIWTIN_TAN_EXEM	WT_EXDT	EXEMPTION TO	O
FIWTIN_TAN_EXEM	WT_EXNR	EXEMPTION NUMBER	R
FIWTIN_TAN_EXEM	WT_EXRT	EXEMPTION RATE	O
FIWTIN_TAN_EXEM	WT-WT_EXRS	EXEMPTION REASON	O
FIWTIN_TAN_EXEM	THR	EXEMPTION THRESHOLD AMOUNT	O
FIWTIN_TAN_EXEM	WAERS	EXEMPTION CURRENCY	O
WYT3	LIFNR	VENDOR	R
WYT3	EKORG	PURCHASING ORGANIZATION	R
WYT3	LTSNR	SUPPLIER SUBRANGE	O
WYT3	WERKS	PLANT	O
LMF1	WEBRE	INDICATOR : GR-BASED INVOICE VERIFICATION	O
LFM1	EXPVZ	MODE OF TRANSPORT AT BORDER	O
LMF1	XERSR	AUTOMATIC EVALUATED RECEIPT SETTLEMENT	O
LMF1	WAERS	PURCHASE ORDER CURRENCY	O
LFM1	EKGRP	PURCHASING GROUP	O
LFM1	PLIFZDAT	PLANNED DELIVERY TIME	O
LFM1	INCO1	INCOTERMS (PART 1)	O
LFM1	INCO2_L	INCOTERMS LOCATION 1	O
LFM1	ZTERMDAT	TERMS OF PAYMENT KEY	O
LFBK	HBKID	SHORT KEY FOR HOUSE BANK	O
LFBK	BANKS	BANK COUNTRY / REGION KEY	R
LFBK	BANKL	BANK KEYS	C
LFBK	BKONT	BANK CONTROL KEY	O
LFBK	BKREF	REFERENCE SPECIFICATIONS FOR BANL DETAIL	O

Data Cleansing

ID	Criticality	Error Message/Report Description	Rule	Output	Source System
3026-001	C1	Deduplication	Deduplication of supplier records with parent and child approach. Vendors with same name, VAT ID, bank details, etc., should be unified to avoid redundant BP creation. Criteria: Same or similar name Same or similar address, phone number, city. VAT/TAX registration number (where applicable)		PF1/WP1
3026-002	C2	Vendor General Bank - Missing or Incorrect Bank details	1) Bank account numbers and IBANs must be in the correct format. For countries outside the EU, the appropriate format must be validated. 2) SWIFT/BIC codes must be present and valid to ensure proper international transactions. 3) Banks assigned to Vendors (BP) must be validated in Bank Master table (BNKA). If BANK details are not found then after confirmation from Business get missing BANK details configured in System	Vendor, Name, Country, Description, Region, Comment, Baseline	PF1/WP1
3026-003	C2	Vendor General - Missing or Incorrect Address details	1) The address info is mandatory, check if source data is updated. 2) For Business Partners (vendors), ensure the 'City' is populated in the Vendor General Data.		PF1/WP1
3026-004	C2	VAT Number / Tax Number	1) VAT numbers, tax codes, and tax jurisdictions must be valid and correctly formatted 2) International vendors must comply with tax rules of their respective countries 3) Generally all records should have at least one of the fields VAT numbers, tax codes, and tax jurisdictions, CNPJ updated 4) International vendors must comply with tax rules of their respective countries		PF1/WP1
3026-005	C2	Missing Emails	Check if correct 'Email' is not populated for Purchasing Organization		PF1/WP1
3026-006	C2	Not Approved Payment Terms	Check the Payment Terms assigned to the vendor and verify if it exists in the mapping table		PF1/WP1

Conversion Process

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

Data Privacy and Sensitivity

Extraction

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

The data exists. connects to the source and loads the data into . 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 ; 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 . This is to be conducted using DCT (Data Collection Template) in

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

Selection Screen

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

Data Collection Template (DCT)

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

DCT Rules

Field Name	Field Description	Rule

Extraction Dependencies

Item #	Step Description	Team Responsible

Transformation

The Target fields are mapped to the applicable Legacy field that will be its source, this is a 3-way activity involving the Business, Functional team and Data team. This identifies the transformation activity required to allow 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
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

Transformation Rules

Rule #	Source system	Source Table	Source Field	Source Description	Target System	Target Table	Target Field	Target Description	Transformation Logic

Transformation Mapping

Mapping Table Name	Mapping Table Description

Transformation Dependencies

List the steps that need to occur before transformation can commence

Item #	Step Description	Team Responsible

Pre-Load Validation

Project Team

Completeness

Task	Action

Accuracy

Task	Action

Business

Completeness

Task	Action

Accuracy

Task	Action

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

Load Phase and Dependencies

Configuration

Item #	Configuration Item

Conversion Objects

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

Error Handling

Error Type	Error Description	Action Taken

Post-Load Validation

Project Team

Completeness

Task	Action

Accuracy

Task	Action

Business

Completeness

Task	Action

Accuracy

Task	Action

Key Assumptions

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

Change log

Version	Published	Changed By
CURRENT (v. 2)	Apr 21, 2026 13:43	BATTINI-ext, Srinivasarao
v. 61	Apr 09, 2026 06:48	BATTINI-ext, Srinivasarao
v. 60	Apr 09, 2026 06:41	BATTINI-ext, Srinivasarao
v. 59	Apr 09, 2026 06:28	BATTINI-ext, Srinivasarao
v. 58	Apr 09, 2026 06:19	BATTINI-ext, Srinivasarao
v. 57	Apr 09, 2026 06:02	BATTINI-ext, Srinivasarao
v. 56	Apr 08, 2026 12:47	BATTINI-ext, Srinivasarao
v. 55	Apr 02, 2026 11:16	BATTINI-ext, Srinivasarao
v. 54	Apr 02, 2026 09:42	BATTINI-ext, Srinivasarao
v. 53	Mar 31, 2026 14:36	BATTINI-ext, Srinivasarao

Go to Page History

Workflow history

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

From Apr 08, 2026 to Apr 21, 2026	Actor	Type	Activity	Version
Revision in Progress	BATTINI-ext, Srinivasarao	Edit	updated the page at 12:47 pm
Apr 06, 2026
	CHITNEEDI-ext, Nagesh	Comment	commented 5:04 pm WEORA Field not present in ECC
	CHITNEEDI-ext, Nagesh	Comment	commented 10:35 am KTOKK=ZICP
Apr 03, 2026
	CHITNEEDI-ext, Nagesh	Comment	commented 7:17 pm account group field name and How to identify whether the STO is created automatically from STR or not?
		Comment	commented 7:15 pm Required and Blank?
		Comment	commented 7:14 pm J_1NBOESL field is not present in Legacy Table
		Comment	commented 7:12 pm WERKS field is missing in DCT.
		Comment	commented 7:06 pm INCO2_ID field is not in S/4 Hana Target Table Structure as per SE11.
		Comment	commented 7:05 pm INCO2_ID field is not in S/4 Hana Target Table Structure as per SE11.
		Comment	commented 7:03 pm ZDGID field is not in S/4 Hana Target Table Structure as per SE11.
From Mar 30, 2026 to Apr 02, 2026
	BATTINI-ext, Srinivasarao	Edit	updated the page at 11:55 pm
	BATTINI-ext, Srinivasarao	State	changed state to Revision in Progress at 9:55 pm	v49

Workflow history

Space shortcuts

Page tree

CNV-3026 Business Partners – 3rd Party Suppliers (Role FLVN001)

Purpose

Conversion Scope

Additional Information

Multi-language Requirement

Document Management

Legal Requirement

Special Requirements

Target Design

Data Cleansing

Conversion Process

Data Privacy and Sensitivity

Extraction

Extraction Run Sheet

Selection Screen

Data Collection Template (DCT)

Extraction Dependencies

Transformation

Transformation Run Sheet

Transformation Mapping

Transformation Dependencies

Pre-Load Validation

Project Team

Completeness

Accuracy

Business

Completeness

Accuracy

Load

Load Run Sheet

Configuration

Conversion Objects

Error Handling

Post-Load Validation

Project Team

Completeness

Accuracy

Business

Completeness

Accuracy

Key Assumptions

See also

Change log

Workflow history