Purpose

The purpose of this document is to define the conversion approach to create 1038 Material BOM (Usage 1 & 4)
in S/4 HANA.

BOMS are actually used for all the Production process. All materials related with manufacturing activities have a Product Structure created by BOM/Master Recipe & Production Version. BOM takes a relevant part of the structure, where the components are defined to produce the Semi Finished and Finished products. The aim prior to migrate is to have a exhaustive data cleansing for BOM, as we know that some plants are having issues with them.

All valid BOMS will be migrated to the S4 Hana System, for all the relevant plants and for all the Semifinished and finished materials in scope (refer to CNV- 9070).

Conversion Scope

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

The data from legacy system includes:

1. BOMS > 3 years
2. BOMS w/o Deletion flags
3. BOMS with active Materials in active Plants
4. BOMS that will be migrated to the To-Be Plant Mapping (Take in consideration the To-Be definition of Plants)

The data from legacy system excludes

1. BOMS inactive in the last 3 years
2. BOMS marked for deletion
3. BOMS with Inactive Materials in inactive Plants
4. BOMS belonging to Deleted plants (New plant Definition according with the To-Be Plant mapping)

Additional Information

Multi-language Requirement

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.

See also

Change log

Workflow history