Purpose

The purpose of this document is to define the conversion approach to create Conversion Specification Document CNV-2009 Material Master – QM View in S/4HANA.

The QM View in the Material Master contains quality-related settings that control how a material is handled in Quality Management processes. These settings include inspection types (e.g., goods receipt, in-process, delivery), quality control keys, certificate requirements, preferred inspection plans or material specifications, and the status of quality management activation for the material. Maintaining the QM View ensures that materials are consistently subjected to the correct inspection processes during procurement, production, and sales.

In SAP S/4HANA, the structure and usage of the Material Master QM View remain consistent with SAP ECC. The QM View is defined by material (MARA-MATNR), plant (MARC-WERKS), and the associated quality-related fields. These include inspection setup (QMAT), inspection types (QMAT-ART), active status, and assignment of task lists or material specifications.

In SAP ECC, aside from the standard fields, additional legacy configurations may exist, such as:

• Materials with inactive or obsolete inspection types still marked in the QM View.
• Materials assigned to inspection types without corresponding inspection plans or specifications.
• Redundant or duplicate plant-level QM settings for the same material.
• Materials with blocked or obsolete quality control keys.
  These cases will need to be validated and cleansed as part of the Master Data Services (MDS) process prior to migration.

This conversion aims to migrate active and relevant Material Master QM View data from existing ECC systems into S/4HANA by applying the required transformation logic using Syniti as the data migration and transformation platform. The converted records will be loaded into the target S/4HANA system using standard SAP mechanisms such as BAPIs (e.g., BAPI_OBJCL_CREATE or BAPI_MATERIAL_SAVEDATA), IDOCs, or direct table loads where applicable, ensuring that all materials in scope have consistent and accurate QM-related setup in the target system.

Conversion Scope

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

From the current system landscape, Material Master QM View data exists separately in the legacy systems (PF2 and WP2), with potential discrepancies in both systems. 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.

The data from legacy system includes: Final relevancy rule pending MDS

1. Active Material Master QM Views that are in use within the last three (3) years in inspection lots, quality certificates, or inspection plans.

2. QM Views without Deletion Flag, i.e., not blocked or obsolete.

3. QM Views assigned to plants that are in-scope for S/4HANA migration, based on the To-Be Plant Mapping.

4. Materials with at least one valid inspection type (e.g., 01, 04, 09) configured and active in the QM View.

5. Materials where control key, inspection setup, and certificate requirements are consistent with S/4HANA target design.

The data from legacy system excludes:

1. Inactive QM Views for materials not used in inspection lots or quality processes for more than three (3) years.

2. QM Views marked for deletion or with inspection types blocked in ECC.

3. QM Views belonging to plants that are out of scope or deleted as per To-Be Plant Mapping.

4. Obsolete inspection types or settings that are not supported in S/4HANA.

5. Duplicate or conflicting QM Views for the same material/plant combination, where only one harmonized record should remain.

List of source systems and approximate number of records

Additional Information

Multi-language Requirement

Not applicable

Document Management

Not applicable

Legal Requirement

Not applicable

Special Requirements

Not applicable

Target Design

With Functional input, document the technical design of the target fields that are in the scope of this document.

The technical design of the target for this conversion approach.

Data Cleansing

All data cleansing should take place in the data source system as defined in this document, unless system limitations prevent it.

If data cleansing is managed outside of the source system (e.g. Syniti Migrate, 3rd Party Vendor, DCT), the necessary documentation must be produced and appended to this deliverable for sign-off.

Conversion Process

The high-level process is represented by the diagram below:

Summarize High-Level Process. Include diagrams, where applicable. Include information supporting details of Extract, Transform and Load specific to the Data Object

Data Privacy and Sensitivity

Extraction

Extract data from a source into Syniti Migrate. There are 2 possibilities:

1. The data exists. Syniti Migrate connects to the source and loads the data into Syniti Migrate. 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 Syniti Migrate; 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 Syniti Migrate. This is to be conducted using DCT (Data Collection Template) in Syniti Migrate

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)

<Object> DCT Rules

Extraction Dependencies

List the steps that need to occur before extraction can commence

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

Identify the phase as to “when” the load for this object will occur. <Pre-Cutover, Cutover, Post Cutover> and list the steps that need to occur before the load can commence

Configuration

List the Configurations required before loading can commence

Conversion Objects

Error Handling

The table below depicts some possible system errors for this data object during data load. All data load error is to be logged as defect and managed within the Defect Management

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

Any additional key assumptions.

See also

Insert links and references to other documents which are relevant when trying to understand this decision and its implications. Other decisions are often impacted, so it's good to list them here with links. Attachments are also possible but dangerous as they are static documents and not updated by their authors.

Change log

Workflow history