Purpose

The purpose of this document is to define the conversion approach to create 1041 Inspection Plan Conversion Specification Document in S/4 HANA.

Inspection Plans are a core component of SAP Quality Management (QM) that define how materials are inspected, including inspection characteristics, sampling procedures, and inspection methods. An inspection plan contains detailed steps for quality checks and ensures that inspections are carried out in a standardized, repeatable, and compliant manner for specific materials, plants, and usage scenarios.

In SAP S/4HANA, the structure and usage of inspection plans remain largely consistent with SAP ECC, typically organized by key combinations such as material/plant, material group/plant, or multiple materials assigned to the same inspection plan via task lists. Inspection plans may also be linked to specific usage types (e.g., goods receipt, in-process inspection, final inspection) and can be maintained with reference to alternative groupings for flexibility.

In SAP ECC, aside from the standard structures, there may be inspection plans with additional variants such as multiple alternative plans for the same material/plant combination, inspection plans assigned to multiple task list groups, or plans that use reference materials. In some legacy systems, plans may also include non-standard fields or custom enhancements (pending MDS review) that will require evaluation before conversion.

This conversion aims to migrate active and relevant inspection plan master data, including associated operations, inspection characteristics, sampling procedures, and inspection methods, from existing ECC systems into S/4HANA. The migration will apply 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_INSPECTIONPLAN_CREATE), IDOCs, or direct table loads where applicable, ensuring data consistency and compliance with S/4HANA requirements

Conversion Scope

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

From the current system landscape, Inspection Plan 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:

1. Active Inspection Plans (PLKO) that are in “Released” status (STATU = 4), PLNTY = 'Q' and used in production, quality, or procurement processes within the last three (4) years.
2. Inspection Plans without deletion flag (PLKO-LOEKZ not set).
3. Plant-specific Inspection Plans that will be migrated according to the To-Be Plant Mapping (considering new plant definitions).
4. Inspection Plans assigned to valid materials via MAPL, where the material exists in the Material Master (MARA/MARC) and is in scope for migration.
5. Inspection Plans with valid Group and Group Counter (PLKO-PLNNR, PLKO-PLNAL)
6. Inspection Plans containing valid operations (PLPO) that reference existing and active work centers (CRHD).
7. Inspection Plan characteristics (PLMK) that:
   • Reference valid Master Inspection Characteristics (QPMK)
   • Reference valid Sampling Procedures (QDSV)
   • Reference valid Inspection Methods (QMTB)
8. Inspection Plans with valid validity dates (PLKO-DATUV)

The data from legacy system excludes:

1. Inactive Inspection Plans that have not been used in inspection lots for more than three (4) years
2. Inspection Plans marked for deletion (PLKO-LOEKZ = X)
3. Inspection Plans belonging to deleted or out-of-scope plants (as per To-Be Plant Mapping)
4. Inspection Plans with invalid or inconsistent references, such as:
   • Characteristics linked to deleted/inactive MICs
   • Sampling Procedures or Inspection Methods that do not exist in S/4HANA
   • Work Centers flagged for deletion or not migrated
5. Inspection Plans with invalid validity dates (Valid-From date into the future PLKO-DATUV).

Relevancy rule

Use the below rules for relevancy criteria.

1. Inspection Plans assigned to valid materials via MAPL, where the material exists in the Material Master (MARA/MARC) and is in scope for migration.

2. Active Inspection Plans (PLKO) that are in “Released” status (STATU = 4), PLNTY = 'Q' and used in production, quality, or procurement processes within the last three (4) years.

QALS-ENSTEHDAT >= (CURRENT DATE -  4 Years) AND QALS-PLNNR = PLKO-PLNNR AND QALS-PLNAL = PLKO-PLNAL AND PLKO-PLNTY = 'Q' AND

PLKO-STATU = '4' & PLKO-LOEKZ = Blank & PLPO-LOEKZ = Blank and PLKO-DATUV > CURRENT DATE

3. Inspection Plans containing valid operations (PLPO) that reference existing and active work centers (CRHD).

4. Inspection Plan characteristics (PLMK) that

• Reference valid Master Inspection Characteristics (QPMK)
• Reference valid Sampling Procedures (QDSV)
• Reference valid Inspection Methods (QMTB)

Plant Merging

Plants will be harmonized based on the To-Be Plant Mapping. As some legacy plants will be merged into one target plant, Inspection Plans will be reassigned accordingly. Plant transformation will be managed through a mapping table maintained in Syniti to ensure consistent alignment with the To-Be Plant structure.

List of source systems and approximate number of records

Additional Information

Multi-language Requirement

Inspection Plan description will be maintained in English by default.

Since multi-language support is available for Inspection Plan, users logging in with a different language will see the description displayed in their logon language, provided that the corresponding language key has been maintained in the on Inspection Plan.

Document Management

None identified. The conversion scope is limited to the migration of Inspection Plan object. No document attachments, images, or supporting files are included.

Legal Requirement

Not applicable

Special Requirements

Not applicable

Target Design

Inspection Plan strictly adheres to the Master Data Standard. The complete information of the tables and key fields that hold the Inspection Plan information follows the Master Data Standard document.

The technical design of the target for this conversion approach

Data Cleansing

Conversion Process

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

The ETL (Extract, Transform, Load) process is a structured approach to data migration and management, ensuring high-quality data is seamlessly transferred across systems. Here’s a breakdown of its key components:

1. Extraction
The process begins with extracting metadata and raw data from source systems, such as Syensqo ECC system (i.e. WP2/PF2) periodically. The extracted data is then staged for transformation.

2. Transformation
Once extracted, the data undergoes cleansing, consolidation, and governance. This step ensures data integrity, consistency, and compliance with business rules. The transformation process includes:
- Data validation to remove inconsistencies.
- Standardization to align formats across datasets.
- Business rule application to refine data for operational use.

3. Loading
The transformed data is then loaded into the target S/4HANA system. 

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)

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 Inspection Plan 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.

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

The Inspection Plan will be loaded in the pre-cutover (PreCutover 4 phase) period.

Before loading, it will have dependency on the following configuration and data objects in the S/4 HANA.

Configuration

Conversion Objects

Error Handling

Post-Load Validation

Project Team

Completeness

Accuracy

Business

Post-load validation is a critical step in data migration, ensuring that transferred data is accurate, complete, and functional within the target system.

1. Ensuring Data Integrity
After migration, data must be consistent with its original structure. Post-load validation checks for missing records, incorrect mappings, and formatting errors to prevent discrepancies.
2. Business Continuity
Faulty data can disrupt operations, leading to financial losses and inefficiencies. Validating post-load data ensures that applications function as expected, preventing downtime.
3. Error Detection and Resolution
By validating data post-migration, businesses can detect anomalies early, reducing the cost and effort required for corrections

Completeness

Accuracy

Key Assumptions

• Master Data Standard is up to date as on the date of documenting this conversion approach and data load.
• Inspection Plan is in scope based on data design and any exception requested by business.
• Data cleansing has met the required percentage threshold for the specified mock cycle and all preparation activities have been completed.
• Data entries in DCT are target-ready data unless a specific transformation rule is stated for that field in the transformation rules.

See also

Change log

Workflow history