Status

Page Status

Owner

CHANCELEDONIO-ext, Beng Chee MADHOK-ext, Jasleen Arnold

Stakeholders

Purpose

The purpose of this document is to define the conversion approach to create Supplier Vendor Hierarchy in S/4 HANA.

Conversion Scope

The scope of this document covers the approach for converting active Vendor Hierarchy from Legacy Source Systems into S/4HANA following the Vendor Hierarchy Master Data Design Standard.

The data from legacy system includes:

Vendors’ relevant general data according to relevancy criteria. Vendor classes used by active vendors with activities for the past 24 months according to Relevancy Criteria for Vendor in CNV-3007 Business Partners - General (Role 000000).

The data from legacy system excludes:

Vendors blocked or marked for deletion.
Purchasing Vendors with extended only to purchasing organization not in scope
Inter-company Vendors
Inactive vendors with no transactions for the past 2 yearsDuplicate vendors

List of source systems and approximate number of records

Source	Scope	Source Approx No. of Records	Target System	Target Approx No. of Records
WP2, PF2	Active Vendors Only active Vendors that are in-scope Extract from LFA1LFA1	40,000	S/4 Hana	<40,000
DCT	Data will be provided by business via excel upload to DCT	40,000	S/4 Hana	<40,000

Additional Information

Multi-language Requirement

Document Management

Legal Requirement

Special Requirements

Target Design

The technical design of the target for this conversion approach based on MDS

Google Drive Live Link

url	https://docs.google.com/spreadsheets/d/1ST-_e-RdHJDD5EFKxkq8dZYMh_YQNkoS/edit?gid=1410070564#gid=1410070564

, tab: Supplier Hierarchy Defn.

Table	Field	Data Element	Field Description	Data Type	Length	Requirement
BUT050	PARTNER1	BU_PARTNER	Business partner 1	CHAR	10	R
BUT050	RELNR	BU_RELNR	Business Partner Relationship Number	CHAR	12	R
BUT050	PARTNER2	BU_PARTNER	Business partner 2	CHAR	10	R
BUT050	DATE_FROM	DATS	Validity Date (Valid From)	DATS	10	R
BUT050	DATE_TO	DATS	Validity Date (Valid To)	DATS	10	R
BUT050	RELTYP	BU_RELTYP	Business Partner Relationship Category	CHAR	6	R

Data Cleansing

No data cleansing is required for Vendor Hierarchy in the legacy system. If any cleansing is deemed necessary, it will be performed outside of the system.

As a result, the cleansed Vendor Hierarchy data will be populated directly in the Data Collection Template (DCT).

IDCriticalityError Message/Report DescriptionRuleOutputSource System

Conversion Process

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

Image Removed

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

For sites not on SAP-PF2 or WP2 systems
For new classes vendors that need to be created to support the to-be design

Data Privacy and Sensitivity

N/A

Extraction

Perform full data extraction from relevant tables in the source system(s).

Perform extraction through the application layer.

Only if ; cannot connect to the source, data is loaded to the repository from the provided source system extract/report.

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:

Syniti.

The data does not exist (or cannot be converted from its current state). The data is manually collected by the business directly in Syniti. This is to be conducted using DCT (Data Collection Template) in Syniti.

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

Extraction Run Sheet

Req #	Requirement Description	Team Responsible
1	Extract data from source system based on relevancy rule	SyWay Data Team
2	Google Sheet report pre-populated with PF2 and WP2 information to be generated based on relevancy criteria.	SyWay Data Team
3	Business to create the vendor hierarchy using the extract from previous step.	S2P Business / Data Owner

Selection Screen

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

Data Collection Template (DCT)

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

DCT Rules

Field Name	Field Description	Rule
PARTNER1	Business partner 1	LIFNR should be in BUT000
RELNR	Business Partner Relationship Number	Internal
PARTNER2	Business partner 2	LIFNR should be in BUT000
DATE_FROM	Validity Date (Valid From)31.12.9999	2 years prior to cut-over or Loading date (YYYYMMDD)
DATE_TO	Validity Date (Valid To)	31.12.9999Default to 99991231
RELTYP	Business Partner Relationship Category	Default to BUR021 (Parent-Child RelationshipBUR998 (Is Partner of)

Extraction Dependencies

Item #	Step Description	Team Responsible
1	3007 Business Partners - General (Vendor Master)	S2P

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 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.
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	Obtain DCT Sign-off from Business	SyWay S2P Data Team
2	<Add steps from Syniti Migrate here> here> Load the DCT data via Construct page. Run the ETL for the object.	SyWay S2P Data Team
3	Review and Validate Error and Preload Reports	SyWay S2P Data Team
4	Generate Load Files	SyWay S2P Data Team

Transformation Rules

Rule #	Source system	Source Field	Source Description	Target System	Target Table	Target Field	Target Description	Transformation Logic
1	DCT	PARTNER1	Business partner 1	S/4 Hana	BUT050	PARTNER1	Business partner 1	Direct MappingCross Reference
2	DCT	RELNR	Business Partner Relationship Number	S/4 Hana	BUT050	RELNR	Business Partner Relationship Number	Internal
3	DCT	PARTNER2	Business partner 2	S/4 Hana	BUT050	PARTNER2	Business partner 2	Direct MappingCross Reference
4	DCT	DATE_FROM	Validity Date (Valid From)	S/4 Hana	BUT050	DATE_FROM	Validity Date (Valid From)	Direct Mapping
5	DCT	DATE_TO	Validity Date (Valid To)	S/4 Hana	BUT050	DATE_TO	Validity Date (Valid To)	Direct Mapping
6	DCT	RELTYP	Business Partner Relationship Category	S/4 Hana	BUT050	RELTYP	Business Partner Relationship Category	Direct Mapping

Transformation Mapping

Mapping Table Name	Mapping Table Description
xtPARTNER	BP Cross ReferenceN/A

Transformation Dependencies

List the steps that need to occur before transformation can commence

Item #	Step Description	Team Responsible
1	Ensure DCT tables completeness	SyWay S2P Data Team

Pre-Load Validation

Project Team

Completeness

Task	Action
Verify Record Count	SyWay S2P Data Team to verify that the total number of relevant records from the DCT is equal to the total number of records in the Preload and Load Sheets.

Accuracy

Task

Action

Conversion Accuracy

SyWay S2P Data Team to verify that all fields below meet pass the checks:

Mandatory Fields
Field and Value Mapping Correctness
Null Checks
Text Length Checks

Review Error Reports

Review and correct the errors. Achieve a zero-error record count as much as possible. Raise defects for data remediated and requiring a correction in the source data.

Business

Completeness

Task	Action
Verify Record Count	Business Data Owner/s to verify that the total number of relevant records from the the DCT is equal to the total number of records in the Preload and Load Sheets.

Accuracy

Task	Action
Conversion Accuracy	Business Data Owner/s to verify that all the data in the load table/file is accurate as per endorsed transformation/mapping rules (and signed-off DCT data).

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	Go to <Load Tool> (calling the function module BAPI_BUPR_RELATIONSHIP_CREATE)	SyWay S2P Data Team
2	Load 3 records for "Create ClassVendor Relationship" function to validate if data is loaded successfully without errors	SyWay S2P Data Team
3	Validate few records loaded by accessing standard transactions from S/4HANA E.g. CL03 / CL6AN for ClassBP > Relationships	SyWay S2P Data Team
4	Generate post load report if step 3 is validated	SyWay S2P Data Team

Load Phase and Dependencies

Configuration

Item #

Configuration Item (Standard)

1

TBZ9 - BP relationship categories (Confirm if activated for Vendor)

Jira

server	Syensqo's Jira
serverId	d8efc1ef-48bd-3b4e-8714-ad827f4f059b
key	PDM-624

Conversion Objects

Object #	Preceding Object Conversion Approach
1	3007 - BP General Vendor Masterlist 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
Configuration	Invalid relationship category Type	Engage Functional team to expedite and fix the error in the system

Post-Load Validation

Project Team

Completeness

Task	Action
Verify Count	SyWay S2P Data Team to verify the record count created in target S/4 HANA by accessing post load reports in Syniti or standard reports from S/4 HANA.
Verify Logs	Check if there is data that failed to load and perform the necessary actions (e.g. register as post load issue or attempt to load the record again, etc.).

Accuracy

Task	Action
Conversion Accuracy	Verify that the Characteristics data in target S/4 HANA were loaded correctly via Syniti post load reports or standard reports from S/4 HANA.

Business

Completeness

Task	Action
Verify Count	Download Post Load Reports from Syniti and verify that the record count loaded in the target S/4 HANA is the same count as of the endorsed load file.

Accuracy

Task	Action
Conversion Accuracy	Verify that the Vendor Characteristics data in target S/4 HANA were loaded correctly via Syniti post load reports or standard reports from S/4 HANA

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

Change History

limit	10

Mar 18, 2026	Actor	Type	Activity	Version
Revision in Progress	WENNINGER-ext, Sascha	State	changed state to Revision in Progress at 5:49 pm	v10
Mar 10, 2026
Edited following Approval	CELEDONIO-ext, Arnold	Edit	updated the page at 10:16 am Obsolete
Edited following Approval	CELEDONIO-ext, Arnold	State	changed state to Edited following Approval at 9:16 am	v10
Oct 10, 2025
Approved	WILLIAMS-ext, Julie	State	changed state to Approved at 1:32 pm	v9
Lead Approval	WILLIAMS-ext, Julie	State	gave POD Lead Review approval at 1:32 pm
	JAIN-ext, Gaurav	State	changed expiry date to '17 Oct, 2025 12:50 pm' at 12:50 pm
	JAIN-ext, Gaurav	State	changed state to Lead Approval at 12:50 pm	v9

Workflow history

Space shortcuts

Page tree

Page History

Versions Compared

Old Version 2

New Version Current

Key

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