Status	Approved
Owner	CELEDONIO-ext, Arnold
Stakeholders

Purpose

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

Conversion Scope

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

The data from legacy system includes:

Active vendors 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.
Inter-company Vendors ( LFA1-ZZR_SEGT_ATTR = 'G' )
Duplicate vendor

List of source systems and approximate number of records

Source	Scope	Source Approx No. of Records	Target System	Target Approx No. of Records
DCT	Data will be provided by business via excel upload to DCT	40,000	S/4 Hana	< 40,000

Additional Information

Multi-language Requirement

N/A

Document Management

Legal Requirement

Special Requirements

Target Design

The technical design of the target for this conversion approach.

Table	Field	Data Element	Field Description	Data Type	Length	Requirement
HRRP_NODE	HRYID	HRYID	Hierarchy ID	CHAR	42	Required
HRRP_NODE	HRYNODE	HRYNODE	Hierarchy Node	CHAR	50	System
HRRP_NODE	PARNODE	PARNODE	Hierarchy Parent Node	CHAR	50	Required
HRRP_NODE	HRYVALFROM	HRYVALFROM	Valid From	DATS	8	Required
HRRP_NODE	HRYVALTO	HRYVALTO	Valid To	DATS	8	Required
HRRP_NODE	NODETYPE	NODETYPE	Node Type	CHAR	1	System
HRRP_NODE	NODEVALUE	NODEVALUE	Node Value - Supplier	CHAR	40	Required
HRRP_NODE	HRYVER	HRYVER	HierarchyVersion	NUMC	15	System
HRRP_NODE	HRYSEQNBR	HRYSEQNBR	SequenceNumber	NUMC	6	System
HRRP_NODE	HRYTYPE	HRYTYPE	HierarchyType	CHAR	4	System
HRRP_NODET	NODETXT	NODETXT	Node Description	CHAR	50	Required
HRRP_NODE	HRYLEVEL	HRYLEVEL	HierarchyLevel	NUMC	6	Required

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).

ID	Criticality	Error Message/Report Description	Rule	Output	Source System
N/A

Conversion Process

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

Collection will be done manually in the DCT (Data Collection Template).

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

Data Privacy and Sensitivity

N/A

Extraction

Extract data from a source into 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 relevant vendors based on 3007 approved vendor dedup results.	SyWay Data Team
2	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 data with exception of some fields which require transformation as mentioned in the transformation rule.

DCT Rules

Field Name	Field Description	Rule
HRYID	Hierarchy ID	DCT key and must be any of the following values: ZSUP/9000000 - Supplier Hierarchy_HQ ZSUP/9000001 - Supplier Hierarchy_Plants ZSUP/9000002 - Supplier Hierarchy_Banks ZSUP/9000003 - Supplier Hierarchy_Employees ZSUP/9000004 - Supplier Hierarchy_Carriers
PARNODE	Hierarchy Parent Node	DCT key and must not exceed 50 characters (Range from 7000000 - 7999999)
HRYVALTO	Valid To	DCT key and must be a valid date YYYYMMDD and not earlier than Valid From or default to 99991231
HRYVALFROM	Valid From	Must be a valid date YYYYMMDD.
zLegacyNODEVALUE	Node Value - Legacy Supplier	Must be a relevant vendor from ECC LFA1-LIFNR
NODETXT	Node Description	Must not exceed 50 characters
HRYLEVEL	HierarchyLevel	Must be numeric

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 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
1	Obtain DCT Sign-off from Business	SyWay S2P Data Team
2	<Add steps from Syniti 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 Table	Source Field	Source Description	Target System	Target Table	Target Field	Target Description	Transformation Logic
1	DCT	BPVendorHierarchy_DCT	HRYID	Hierarchy ID	ROW China	HRRP_NODE	HRYID	Hierarchy ID	Copy
2	DCT	BPVendorHierarchy_DCT	PARNODE	Hierarchy Parent Node	ROW China	HRRP_NODE	PARNODE	Hierarchy Parent Node	Copy
3	DCT	BPVendorHierarchy_DCT	HRYVALFROM	Valid From	ROW China	HRRP_NODE	HRYVALFROM	Valid From	Copy or default to load date if blank.
4	DCT	BPVendorHierarchy_DCT	HRYVALTO	Valid To	ROW China	HRRP_NODE	HRYVALTO	Valid To	Copy or default to 99991231 if blank.
5	DCT	BPVendorHierarchy_DCT	zLegacyNODEVALUE	Node Value - Legacy Supplier	ROW China	HRRP_NODE	NODEVALUE	Node Value - Supplier	Vendor_XREF
6	DCT	BPVendorHierarchy_DCT	NODETXT	Node Description	ROW China	HRRP_NODET	NODETXT	Node Description	Copy
7	DCT	BPVendorHierarchy_DCT	HRYLEVEL	HierarchyLevel	ROW China	HRRP_NODE	HRYLEVEL	HierarchyLevel	Copy

Transformation Mapping

Mapping Document Link

Mapping Table Name	Mapping Table Description
Vendor_XREF	LIFNR: Old Vendor Code to New Vendor Code

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
Review Error Reports	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 Fiori <Load Tool>	SyWay S2P Data Team
2	Load 3 records 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	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
1	Hierarchy ID HRYID is configured and valid in the target system in table HRRP_DIRECTORY

Conversion Objects

Object #	Preceding Object Conversion Approach
1	3007 - BP General Vendor Master

Error Handling

Error Type	Error Description	Action Taken
1	The value XXX for field XXX doesn't exist	Check the mapping/conversion is done properly in the loading file Validate the target value is configured/transported in the target system Reach out to function team to validate the configuration
2	There is mandatory field XXX missing	Validate MDS if the fields are set as mandatory Validate if there is value in the pre-loading file Validate if the configuration for the mandatory fields are done properly

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

Version	Published	Changed By	Comment
CURRENT (v. 7)	Apr 15, 2026 07:39	CELEDONIO-ext, Arnold
v. 7	Apr 13, 2026 13:24	CELEDONIO-ext, Arnold	Added valid values for Hierarchy ID
v. 6	Mar 25, 2026 08:48	CELEDONIO-ext, Arnold
v. 5	Mar 23, 2026 08:32	CELEDONIO-ext, Arnold
v. 4	Mar 20, 2026 15:58	CELEDONIO-ext, Arnold
v. 3	Mar 20, 2026 15:27	CELEDONIO-ext, Arnold
v. 2	Mar 20, 2026 13:59	CELEDONIO-ext, Arnold
v. 1	Mar 10, 2026 10:14	CELEDONIO-ext, Arnold

Apr 20, 2026	Actor	Type	Activity	Version
Approved	HOLMES-ext, Richard	State	changed state to Approved at 7:32 am	v8
Lead Approval	HOLMES-ext, Richard	State	gave POD Lead Review approval at 7:32 am
Apr 19, 2026
	JAIN-ext, Gaurav	State	changed expiry date to '26 Apr, 2026 10:59 pm' at 10:59 pm
	JAIN-ext, Gaurav	State	changed state to Lead Approval at 10:59 pm	v8
Tech Review of Updates	JAIN-ext, Gaurav	State	gave Minor change approval at 10:59 pm
Tech Review of Updates	JAIN-ext, Gaurav	State	changed state to Tech Review of Updates at 10:59 pm changes and efforts are tracked via JIRA PDM-1660	v8
Apr 15, 2026
Update in progress	CELEDONIO-ext, Arnold	Edit	updated the page at 7:39 am

Workflow history

Space shortcuts

Page tree

CNV-3024 Vendor Hierarchy (CR0252)

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