Purpose

The purpose of this document is to define the conversion approach to create Business Partners - General in S/4 HANA.

In SAP ECC, customer and vendor master data are maintained separately as distinct entities. Customers are managed through Customer Master Data, while vendors are handled via Vendor Master Data. These records store essential details such as company name, address, payment terms, and tax information.
In SAP S/4HANA, the Business Partner (BP) concept replaces the traditional customer and vendor master data approach. The BP model integrates both customer and vendor roles into a single entity, simplifying data management and ensuring consistency across different business functions

Conversion Scope

The scope of this document covers the approach for converting active Customer Master Data General and Vendor Master General from Legacy Source Systems into S/4HANA Business Partner (BP) General (Role 000000) Master Data Design Standard. 

The data from legacy system includes:

1. Customer/Vendor with AR/AP Balance under the company codes within S4 Hana implementation scope.
2. or (Customer doesn't have central deletion indicator AND Customer has sales transaction within the sales organizations in scope within 5 years), e.g., the customer is used as any partner function in the sales document, such as sales order, delivery or billing.
3. or (Customer doesn't have central deletion indicator and customer has financial posting under the company codes within S4 Hana implementation scope within 5 years)
4. or Customer is part of Customer Hierarchy Higher Node, and the sales area data is part of the sales are within migration scope

The data from legacy system excludes:

1. Customer/Vendor has central deletion indicator and without AR/AP Balance under the company codes within S4 Hana implementation scope.
2. or (Customer is not used in any sales transaction under the sales organizations in scope for more than 5 years AND without any financial posting under the company codes in scope for more than 5 years)

Additional Information

Multi-language Requirement

The customer and vendor general data may contain international address. Therefore, the conversion will also need to support the multi-language.  Below language (International versions) are supported. 

Document Management

Legal Requirement

Special Requirements

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.

Change log

Workflow history