Purpose

The purpose of this document is to define the conversion approach to create 1040-Production Versions in S/4 HANA.

Production Version is used to define the product data structure. Meaning PV contains Master Recipe, BOM and Resources. According with lot size, Production version can be defined for each material to be processed in several production units. Usually, all Manufacturing plants need to use Production Versions for planning and scheduling processes. The aim is to migrate all the active Prod. Versions to S/4 HANA.

Conversion Scope

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

Stand alone rules

The data from legacy system includes:

1. The migration of Production Versions will be governed by the Material Relevancy Criteria, which serve as the foundational rule for identifying and including Production Versions that are valid, active, and business-relevant for conversion to S/4HANA.
2. All active Production Versions W/o locked status
3. All Active Production Versions W/O Deletion Flag
4. All active Production Versions related to active material and Plant (Mapped in the To-Be Plant Mapping)

The data from legacy system excludes:

1. All Production Versions older more than 4 years
2. All production versions with Locked status (This needs to be checked to approve Production versions with Locked status in CM) Data Relevancy Criteria Meeting Review
3. All Production Versions with deletion flag
4. All Production Versions belonging to Materials flagged for deletion
5. All Production Versions Belonging to Material-Plant combination not existing in the To-be Plant Mapping

Relevancy for Syniti

1. Production version creation is only relevant when the following is live and active in a sequential order
2. Material and Plant have a live status at Plant and at a Global level and contain 4 years of process order history
3. BOM and all BOM components are live and active at plant level Based on the condition set that Materials contain 4 years of Process order History
4. Master Recipe is live and an active BOM is available and live at Plant level, based on the condition set that Materials contain 4 years of Process order History

Material/Plant active  BOM and all BOM components are live and active at Plant level Master Recipe is live and an active BOM is available at Plant level = Creation of Production Version

Plant Merging

Plants will be defined accordingly as some plants will be merged into one plant. Plants will be defined as NEW plant codes and be transformed via a transformation table, which will be contained in Syniti.

List of source systems and approximate number of records 

Additional Information

Multi-language Requirement

N/A

Document Management

N/A

Legal Requirement

N/A

Special Requirements

N/A

Target Design

The technical design of the target for this conversion approach.

Data Cleansing

Business will perform data cleansing in the current ECC system. This means ECC will serve as the single source of truth for Manufacturing Data prior to the migration to S/4HANA.

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)

The Data Collection Template (DCT) will not be applicable in this case. If there is a need to create a new Master Data (MD) for Production Version object, the business must perform this activity in the source system. The newly created object will then be captured and migrated as part of the standard migration process. 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