You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 7 Next »

Status

  Revision in Progress

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 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:

  1. 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:

  1. Vendors blocked or marked for deletion.
  2. Vendors with extended only to purchasing organization not in scope
  3. Inter-company Vendors
  4. Duplicate vendors


List of source systems and approximate number of records
SourceScope

Source Approx No. of Records

Target SystemTarget Approx

No. of Records

WP2, PF2

Only active Vendors that are in-scope

Extract from LFA1 

40,000S/4 Hana<40,000
DCTData will be provided by business via excel upload to DCT40,000S/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 , tab: Supplier Hierarchy Defn.

TableFieldData ElementField DescriptionData TypeLengthRequirement
BUT050PARTNER1BU_PARTNERBusiness partner 1CHAR10R
BUT050RELNRBU_RELNRBusiness Partner Relationship NumberCHAR12R
BUT050PARTNER2BU_PARTNERBusiness partner 2CHAR10R
BUT050DATE_FROMDATSValidity Date (Valid From)DATS10R
BUT050DATE_TODATSValidity Date (Valid To)DATS10R
BUT050RELTYPBU_RELTYPBusiness Partner Relationship CategoryCHAR6R


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

Conversion Process

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

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

  1. 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 DescriptionTeam Responsible
1Extract data from source system based on relevancy ruleSyWay Data Team
2Google Sheet report pre-populated with PF2 and WP2 information to be generated based on relevancy criteria. SyWay Data Team
3Business to create the vendor hierarchy using the extract from previous step.S2P Business / Data Owner




Selection Screen

Selection Ref ScreenParameter NameSelection TypeRequirementValue 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 NameField DescriptionRule
PARTNER1Business partner 1LIFNR should be in BUT000
RELNRBusiness Partner Relationship NumberInternal
PARTNER2Business partner 2LIFNR should be in BUT000
DATE_FROMValidity Date (Valid From)2 years prior to cut-over or Loading date (YYYYMMDD)
DATE_TOValidity Date (Valid To)Default to 99991231
RELTYPBusiness Partner Relationship CategoryDefault to BUR021 (Parent-Child Relationship)

Extraction Dependencies

Item #Step DescriptionTeam Responsible
13007 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:

  1. 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.
  2. 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 DescriptionTeam Responsible
1Obtain DCT Sign-off from BusinessSyWay S2P Data Team
2<Add steps from Syniti here>SyWay S2P Data Team
3Review and Validate Error and Preload ReportsSyWay S2P Data Team
4

Generate Load Files

SyWay S2P Data Team


Transformation Rules

Rule #Source systemSource TableSource FieldSource DescriptionTarget SystemTarget TableTarget FieldTarget DescriptionTransformation Logic
1DCT
PARTNER1Business partner 1S/4 HanaBUT050PARTNER1Business partner 1Cross Reference
2DCT
RELNRBusiness Partner Relationship NumberS/4 HanaBUT050RELNRBusiness Partner Relationship NumberInternal
3DCT
PARTNER2Business partner 2S/4 HanaBUT050PARTNER2Business partner 2Cross Reference
4DCT
DATE_FROMValidity Date (Valid From)S/4 HanaBUT050DATE_FROMValidity Date (Valid From)Direct Mapping
5DCT
DATE_TOValidity Date (Valid To)S/4 HanaBUT050DATE_TOValidity Date (Valid To)Direct Mapping
6DCT
RELTYPBusiness Partner Relationship CategoryS/4 HanaBUT050RELTYPBusiness Partner Relationship CategoryDirect Mapping


Transformation Mapping

Mapping Table NameMapping Table Description
xtPARTNERBP Cross Reference






Transformation Dependencies

List the steps that need to occur before transformation can commence
Item #Step DescriptionTeam Responsible
1Ensure DCT tables completenessSyWay S2P Data Team










Pre-Load Validation

Project Team

Completeness

TaskAction
Verify Record CountSyWay 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

TaskAction
Conversion Accuracy

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

  1. Mandatory Fields
  2. Field and Value Mapping Correctness
  3. Null Checks
  4. Text Length Checks
Review Error ReportsReview 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

TaskAction
Verify Record CountBusiness 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

TaskAction
Conversion AccuracyBusiness 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:

  1. Execute the automated data load into target system using load tool or product the load file if the load must be done manually
  2. 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 DescriptionTeam Responsible
1Go to <Load Tool> (calling the function module BAPI_BUPR_RELATIONSHIP_CREATE)SyWay S2P Data Team
2Load 3 records for "Create Vendor Relationship" function to validate if data is loaded successfully without errorsSyWay S2P Data Team
3Validate few records loaded by accessing standard transactions from S/4HANA E.g. BP > RelationshipsSyWay S2P Data Team
4Generate post load report if step 3 is validatedSyWay S2P Data Team


Load Phase and Dependencies

Configuration

Item #Configuration Item (Standard)
1

TBZ9 - BP relationship categories (Confirm if activated for Vendor) PDM-624 - Getting issue details... STATUS





Conversion Objects

Object #Preceding Object Conversion Approach
13007 - BP General Vendor Master




Error Handling

Error TypeError DescriptionAction Taken
Configuration

Invalid relationship category Type

Engage Functional team to expedite and fix the error in the system







Post-Load Validation

Project Team

Completeness

TaskAction

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

TaskAction

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

TaskAction

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

TaskAction

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.


See also

Change log

Version Published Changed By Comment
CURRENT (v. 7) Mar 10, 2026 10:16 CELEDONIO-ext, Arnold Obsolete
v. 9 Oct 06, 2025 14:29 CELEDONIO-ext, Arnold Update Transformation Run Sheet
v. 8 Sept 23, 2025 16:40 CELEDONIO-ext, Arnold
v. 7 Sept 22, 2025 15:43 CELEDONIO-ext, Arnold
v. 6 Sept 22, 2025 13:12 CELEDONIO-ext, Arnold
v. 5 Sept 22, 2025 12:45 CELEDONIO-ext, Arnold
v. 4 Sept 22, 2025 09:38 CELEDONIO-ext, Arnold
v. 3 Sept 22, 2025 09:20 CELEDONIO-ext, Arnold Updated Target/Mapping and Load Run Sheet
v. 2 Sept 09, 2025 16:24 CELEDONIO-ext, Arnold Added Transformation rules and Preload/Postload approach
v. 1 Jul 22, 2025 10:41 CHAN-ext, Beng Chee

  • No labels