Status
Owner	SUSANTO-ext, William
Stakeholders	GERVAIS, Pascal

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 1041 Inspection Plan
 from Legacy Source Systems into S/4HANA following the TBD Master Data Design Standard.

The data from legacy system includes:

1. Data not older than 3 years of usage
2. Data  not flagged for deletion
3. Data that has material / plant relationship and material is active
4. Data is relevant for migration according with the Material/Plant mapping match with MARC table (ToBe)

The data from legacy system excludes:

1. Data older than 3 years
2. Data flagged for deletion
3. Data that has material / plant relationship and material is not active or falged for deletion
4. Data that is not material / plant relevant according to the latest MARC table definition

List of source systems and approximate number of records

Source	Scope	Source Approx No. of Records	Target System	Target Approx No. of Records
PF2
WP2

Additional Information

Multi-language Requirement

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.

Table	Field	Data Element	Field Description	Data Type	Length	Requirement
PLKO	PLNTY	PLNTY	Task List Type (Q = Inspection Plan)	CHAR	1	Mandatory
PLKO	PLNNR	PLNNR	Task List Group	CHAR	8	Mandatory
PLKO	PLNAL	PLNAL	Group Counter (alternative)	CHAR	2	Mandatory
PLKO	WERKS	WERKS_D	Plant	CHAR	4	Mandatory
PLKO	DATUV	DATUV	Valid-From Date	DATS	8	Mandatory
PLKO	VERWE	VERWE	Task List Usage (e.g., 1/5/9 – confirm in T416)	CHAR	3	Mandatory
PLKO	STATU	STATU	Task List Status (e.g., Released)	CHAR	1	Mandatory for load (set to released if required)
PLKO	KTEXT	KTEXT	Header Description	CHAR	40	Recommended
PLKO	LOEKZ	LOEKZ	Deletion Indicator	CHAR	1	Optional (leave blank for active)
PLKO	KLART	KLART	Class Type (if classification used)	CHAR	3	Optional
PLKO	KZKUP	KZKUP	Reference Indicator (Header)	CHAR	1	Optional
PLPO	PLNKN	PLNKN	Node Number (internal op ID)	NUMC	8	Mandatory
PLPO	VORNR	VORNR	Operation Number (sequence)	CHAR	4	Mandatory
PLPO	LTXA1	LTXA1	Operation Short Text	CHAR	40	Mandatory
PLPO	STEUS	STEUS	Control Key	CHAR	4	Mandatory (drives QM/confirmation behavior)
PLPO	ARBID	ARBID	Work Center (internal ID)	NUMC	8	Mandatory (or map via ARBPL/CRHD)
PLPO	WERKS	WERKS_D	Plant (Work Center Plant)	CHAR	4	Mandatory
PLPO	BMSCH	BMSCH	Base Quantity (for std values)	QUAN	13	Recommended
PLPO	VGW01	VGWRT	Standard Value 1 (e.g., Setup/Inspect time)	DEC	7	Optional
PLPO	VGE01	VGWTS	Unit for Standard Value 1	UNIT	3	Optional
PLPO	VGW02	VGWRT	Standard Value 2	DEC	7	Optional
PLPO	VGE02	VGWTS	Unit for Standard Value 2	UNIT	3	Optional
PLPO	KAPAZ	KAPAZ	Capacity Category (if used)	CHAR	3	Optional
PLPO	ARBPL	ARBPL	Work Center (external key, if you load views)	CHAR	8	Optional (derived from ARBID)
PLPO	LOEKZ	LOEKZ	Deletion Indicator (Operation)	CHAR	1	Optional
PLMK	MERKNR	MERKNR	Characteristic Number (in plan)	NUMC	4	Mandatory
PLMK	KURZTEXT	KURZTEXT	Char. Short Text	CHAR	40	Mandatory
PLMK	VORGLFNR	VORGLFNR	Op Link (operation sequence number)	NUMC	4	Mandatory (links to PLPO)
PLMK	KZREF	KZREF	Reference to Master Insp. Char. (MIC)	CHAR	1	Mandatory if using MIC
PLMK	VERWMERKM	VERWMERKM	MIC Name (Referenced Char.)	CHAR	18	Mandatory if using MIC
PLMK	VERSION	VERSION	MIC Version	NUMC	2	Mandatory if using MIC versioning
PLMK	PRUEFUMF	PRUEFUMF	Inspection Scope / Sample Procedure Link	CHAR	4	Optional (if using sampling procedures)
PLMK	STICHPRVER	STICHPRVER	Sampling Procedure	CHAR	8	Optional
PLMK	KATALGART	KATALGART	Catalog Type (for qualitative)	CHAR	3	Optional/Required for qualitative
PLMK	CODEGRP	CODEGRP	Code Group (qualitative)	CHAR	8	Optional/Required for qualitative
PLMK	AUSWMENGE	AUSWMENGE	Selected Set (qualitative)	CHAR	8	Optional
PLMK	PRUEFME	MSEHI	Unit of Measure (quantitative)	UNIT	3	Required for quantitative
PLMK	TOLKZ	TOLKZ	Tolerance Indicator	CHAR	1	Optional (quantitative)
PLMK	MWERTS	MWERTS	Target Value	DEC	15	Optional (quantitative)
PLMK	MWERTU	MWERTU	Lower Spec Limit	DEC	15	Optional/Required per spec rule
PLMK	MWERTO	MWERTO	Upper Spec Limit	DEC	15	Optional/Required per spec rule
PLMK	PRFGEB	PRFGEB	Inspection Method Assignment	CHAR	12	Optional
PLMK	PRFGVER	PRFGVER	Inspection Method Version	NUMC	2	Optional
PLMK	ANZST	ANZST	No. of Single Values / Samples	NUMC	3	Optional
PLMK	LOEKZ	LOEKZ	Deletion Indicator (Characteristic)	CHAR	1	Optional
MAPL	MATNR	MATNR	Material	CHAR	40	Mandatory (if plan is material-assigned)
MAPL	WERKS	WERKS_D	Plant	CHAR	4	Mandatory
MAPL	PLNTY	PLNTY	Task List Type	CHAR	1	Mandatory
MAPL	PLNNR	PLNNR	Task List Group	CHAR	8	Mandatory
MAPL	PLNAL	PLNAL	Group Counter	CHAR	2	Mandatory
MAPL	DATUV	DATUV	Valid-From Date	DATS	8	Mandatory
MAPL	LOEKZ	LOEKZ	Deletion Indicator	CHAR	1	Optional

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.

ID	Criticality	Error Message/Report Description	Rule	Output	Source System

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

Summarize Data Privacy and Sensitivity Requirements, if any

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

Req #	Requirement Description	Team Responsible

Selection Screen

If applicable, this section will give the details on any selection screen parameters, including the parameter type, that are required to be entered to ensure consistent data extracts.

Selection Ref Screen	Parameter Name	Selection Type	Requirement	Value to be entered/set

Data Collection Template (DCT)

Target Ready Data Collection Template will be created for Data Object data with exception of some fields which require transformation as mentioned in the transformation rule.

<Object> DCT Rules

Field Name	Field Description	Rule

Extraction Dependencies

List the steps that need to occur before extraction can commence

Item #	Step Description	Team Responsible

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

Item #	Step Description	Team Responsible

Transformation Rules

Rule #	Source system	Source Table	Source Field	Source Description	Target System	Target Table	Target Field	Target Description	Transformation Logic

Transformation Mapping

Use the exact name and reference this section in the “Transformation rules” above

Mapping Table Name	Mapping Table Description

Transformation Dependencies

List the steps that need to occur before transformation can commence

Item #	Step Description	Team Responsible

Pre-Load Validation

Project Team

The following pre-load validations will be performed by the Project Team.

Completeness

Task	Action
title	specific details of what and how the task needs to be performed e.g. which reports are being used etc.

Accuracy

Task	Action
title	specific details of what and how the task needs to be performed e.g. which reports are being used etc.

Business

The following pre-load validations will be performed by the business.

Completeness

Task	Action
title	specific details of what and how the task needs to be performed e.g. which reports are being used etc.

Accuracy

Task	Action
title	specific details of what and how the task needs to be performed e.g. which reports are being used etc.

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

Item #	Step Description	Team Responsible

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

Item #	Configuration Item

Conversion Objects

Object #	Preceding Object Conversion Approach
	list the exact title of the conversion object of only the immediate predecessor – this will then confirm the DDD (Data Dependency Diagram)

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

Error Type	Error Description	Action Taken

Post-Load Validation

Project Team

The following post-load validations will be performed by the Project Team.

Completeness

Task	Action
title	specific details of what and how the task needs to be performed e.g. which reports are being used etc.

Accuracy

Task	Action
title	specific details of what and how the task needs to be performed e.g. which reports are being used etc.

Business

The following post-load validations will be performed by the business.

Completeness

Task	Action
title	specific details of what and how the task needs to be performed e.g. which reports are being used etc.

Accuracy

Task	Action
title	specific details of what and how the task needs to be performed e.g. which reports are being used etc.

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