Purpose

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

Conversion Scope

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

From the current system landscape, Material data exists separately in the legacy systems (PF2 and WP2), with potential discrepancies in both organizations. Harmonization and validation are required to ensure accurate and consolidated data in S/4HANA. While PF2 and WP2 serve as source systems, extensive mapping and transformation logic will be necessary to produce properly formatted load templates in line with the target design.

Relevancy Rules

1. All materials created in the previous 6 months will be included unless flagged for deletion
2. These include Material Types ZUNB, ZBOM, ZPRC regardless of activity (unless flagged for deletion)
3. We will only include materials that are extended to the following (excluding ZPRC material type as these do not require plant extension):
   1. Company Codes in scope
   2. Plants in scope
   3. Purchasing Orgs in scope
   4. Sales Orgs in scope
4. Include only Material Types in scope
5. We will include for migration all materials that have activity over the previous 3 years, to include:
   1. For procurement data use EKKO/EKPO tables
   2. For sales data use VBAK/VBAP tables
   3. For production data use AFKO/AFPO tables
6. We will include for migration all materials that have open documents including the following:
   1. Open PO refer to CNV-9045 Open PO spec
   2. Open Contracts refer to CNV-9045 Open PO spec
   3. Open STO refer to CNV-9045 Open PO spec
   4. Open SO refer to CNV-9065 Open SO spec
   5. Open WO refer to CNV-9005 Open WO spec
7. Have current stock - refer to CNV-9051 Open Inventory
8. We will include all BOM data for materials in scope using tables: MAST/STKO/STPO
9. Materials with Deletion Flags will be excluded unless appearing in open transactions
   1. Open PO refer to CNV-9045 Open PO spec
   2. Open SO refer to CNV-9065 Open SO spec
   3. Open WO refer to CNV-9005 Open WO spec
10. Deletion Flags (Table/Field) are as follows: MARA/LVORM = 'X' MARA/MSTAE = Z3, Z4, ZZ (PF2 system) Z0 (WP2 system)
11. Materials with the word 'OBSOLETE' or 'DELETED' contained within the Short Description will be excluded. Also excluded are Materials where Short Description contains '**OBS', '**OBS**', '**OBS***', '*OBS*', '*OBS**', '***OBS***'

Additional Information

Multi-language Requirement

Multi language is supported for Materials - Additional Data. Login via a different language will show the description displayed in the logon language if the language key is maintained.

Document Management

Not Applicable

Legal Requirement

Not Applicable

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.
• Materials - Additional Data is in scope based on data design and any exception requested by business.

See also

Change log

Workflow history