Purpose

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

In SAP ECC, the customer hierarchy is a tree-like hierarchy where each node is a customer (including parent and child customers). The primarily purpose is used for pricing, rebates, and reporting across related customers. It will be maintained via transaction code VDH1N.

In SAP S/4HANA, customers are managed as Business Partners (BP), enabling a more flexible and integrated data model. Hierarchy nodes are created as BPs with sales area data. It is still maintained via VDH1N (or Fiiori app Display/Maintain Customer Hierarchy), but enhanced with validity periods, governance, and inheritance.

Conversion Scope

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

The data from legacy system includes:

1. For Parent, the sales area data has the sales organization in scope
2. For Child, the sales area data has the sales organization in scope and the sales view is still active

The data from legacy system excludes:

Additional Information

Multi-language Requirement

N/A

Document Management

N/A

Legal Requirement

CMMC 2.0 is a mandatory DoD cybersecurity certification for contractors handling Controlled Unclassified Information (CUI) and Federal Contract Information (FCI). CUI includes sensitive technical data (e.g., design specs, system info) related to U.S. military and space applications. The Composites Business handles CUI and is therefore within CMMC scope. Without certification, the business risks disqualification from existing and future DoD programs.
It is mandatory to implement CMMC-compliant systems and processes to for all the organizations that are dealing with CUI.

Therefore, there will be one SAP instance specifically for CUI related entities. The migration for CUI related entities will be covered by US based data consultant using separate tools.

Special Requirements

Different SAP Instance Migration Approach

Due to compliance requirement, there will be one SAP instance for Rest of the World, one for China and one for CUI.

1. For entities in China, the data will be loaded into SAP China instance while the entire migration process will remain the same as rest of the world.
2. For entities which will reside in CUI, the migration will be handled by US based data consultant. 

Please refer to the link for the entity mapping for each instance. In case the data object is applicable for multiples instances, what business rule to follow?

 - To identify the record is for SAP ROW Instance, it will use below logic. 

Target Design

The technical design of the target for this conversion approach.

Data Cleansing

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:

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

Selection Screen

Data Collection Template (DCT)

DCT Rules

Extraction Dependencies

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:

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

Transformation Rules

Transformation Mapping

Transformation Dependencies

Pre-Load Validation

Project Team

Completeness

Accuracy

Business

Completeness

Accuracy

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

Load Phase and Dependencies

Configuration

Conversion Objects

Error Handling

Post-Load Validation

Project Team

Completeness

Accuracy

Business

Completeness

Accuracy

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

Workflow history