Status	Update in progress
Owner	CASTRO MONCAYO-ext, Jose Luis ULLAH-ext, Colin
Stakeholders	GERVAIS, Pascal

Purpose

The purpose of this document is to define the conversion approach to create1039 - Master Recipe in S/4 HANA.

Master recipes are assigned to a plant and are part of a plant-independent recipe group.

In the recipe header, master recipes used for production are linked to the materials to be produced. The production versions of the materials also link them to the alternative BOM required for production.

Master recipes are used as the basis for process orders. The business object master recipe is the description of an enterprise-specific process in process industries, that does not relate to a specific order. The master recipe is used for the manufacture of products. In all Manufacturing plants that are using SAP PP-PI ( Production Planning for process Industries), This is the most important Master Data, This Master Data includes BOM, Resources, Formulas, Costing Data and others, relevant for creating Process Orders.

Conversion Scope

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

The data from legacy system includes:

Active Master Recipes, used in Process Orders for the last 3 years
Active Master Recipes valid for active materials
Active Master Recipes valid for Material / Plant Combination (according with the latest Plant Mapping)

The data from legacy system excludes:

Active Master Recipes NOT used for the last three years
Master recipes with deletion flag
Master Recipes for materials flagged for deletion
Master Recipes for materials without active status
Master recipes for Material / Plant combination that are Out of Scope

List of source systems and approximate number of records

Source	Scope	Source Approx No. of Records	Target System	Target Approx No. of Records
PF2	Master Recipes will be extracted from PF2	15,000	S/4 HANA	10,000
WP2	Master Recipes will be extracted from WP2	15,000	S/4 HANA	12,000
DCT	We will use a DCT for data conversion from Specific Routing to Master Recipe, for plants are still using Discrete Manufacturing	3000	S/4 HANA	1500

Additional Information

Multi-language Requirement

Document Management

N/A

Legal Requirement

N/A

Special Requirements

N/A

Target Design

The technical design of the target for this conversion approach.

Table	Field	Data Element	Field Description	Data Type	Length	Requirement
PLKO	PLNTY	PLNTY	Key which classifies task lists according to their functionality. In Syensqo production context this value is defaulted to "2"	CHAR	1	R : For PP PI the master recipe is a task list with type "2" In case of Rate routing value from As Is = "R" will be mapped to value "2"
PLMZ	RGEKZ	RGEKZ	Backflush	CHAR	1
PLKO	PLNTY	PLNTY	Key which classifies task lists according to their functionality. In Syensqo production context this value is defaulted to "2"	CHAR	1	R : For PP PI the master recipe is a task list with type "2" In case of Rate routing value from As Is = "R" will be mapped to value "2"
PLKO	PLNNR	PLNNR	Key that uniquely identifies a recipe group.	CHAR	8	S
PLKO	PLNAL	PLNAL	Key that identifies a master recipe within a recipe group.	CHAR	2	S
PLKO	DATUV	DATUV	Date from which the recipe object is valid.	DATS	8	R : By default the system date but the user can enter a valid from date
PLKO	VALID_TO	DATUV	End of the validity period of the recipe object.	DATS	8	R
PLKO	AENNR	AENNR	Key for the change master record or engineering change order that the chosen change status of the recipe object was created with.	CHAR	12	NU
PLKO	VERWE	PLN_VERWE	Key indicating what the recipe is used for, such as production or plant maintenance. for Syensqo production scope the value used will be "1"	CHAR	3	R : Syensqo production scope the value used will be "1"
PLKO	WERKS	WERKS_D	Plant of the material to be produced.	CHAR	4	R
PLKO	STATU	PLNST	Status key to indicate the processing status of a recipe. For example, indicate whether the recipe is still in the creation phase or has already been released.	CHAR	3	R
PLKO	PLNME	PLNME	Unit of measure of the charge quantity	UNIT	3	R
PLKO	LOSVN	LOSGRVON	Lower limit of the charge quantity range for which the recipe is valid.	QUAN	13	C : If a value is entered, then the recipe can be used only for process orders with quantity superior to the minimum lot size
PLKO	LOSBS	LOSGRBIS	Upper limit of the charge quantity range for which the recipe is valid.	QUAN	13	C : If a value is entered, then the recipe can be used only for process orders with quantity inferior to the maximum lot size
PLKO	VAGRP	VAGRP	Key of the planner group responsible for maintaining the recipe.	CHAR	3	C : Business rule. If reporting is needed by planner group for the master recipe this field need to be populated. Empty is a valid value
PLKO	KTEXT	PLANTEXT	Describes the recipe	CHAR	40	R
PLKO	TXTSP	SPRAS	Language key	LANG	1	S
PLKO	LOEKZ	LKENZ	Indicator set if the recipe to be completely deleted at the next reorganization run, with all its change states.	CHAR	1	S
PLKO	PROFIDNETZ	PROFID_STD	A profile is a collection of default values and settings for maintenance of routings or master recipes or standard networks.	CHAR	7	R
PLKO	BMSCH	BMSCH	Quantity of the material to be produced to which the standard values of the operation refer.	QUAN	13	R
PLKO	QKZRASTER	QKZRASTER	Identifier for Inspection Point Field Combination, Inspection points are used as reference objects for recording inspection results below operation level. If a value is entered for the inspection point, this value is copied to the inspection lots.	CHAR	1	NU
PLKO	PPKZTLZU	QPPKZTLZU	Partial Lot Assignment in an Inspection During Production he entry in this list field to set the detail levels for the assignment of manufactured quantities. In the first and most detailed level ("Partial lots not defined"), the manufactured partial quantities are assigned to inspection points for which inspection results are also recorded. In the second detail level ("Partial lot for each inspection point"), the partial quantities, to which the inspection points are assigned, are combined into partial lots. In the third detail level ("Partial lot and batch for each inspection point"), partial lots are combined into batches.	CHAR	1	NU
PLKO	QPRZIEHVER	QPRZIEHVER	A master data object in QM sample management that contains instructions for a sample drawing.	CHAR	8	NU
PLKO	QDYNHEAD	QDYNHEAD	Identifies the level at which the decision for inspection stages is made and the quality level maintained.	CHAR	1	NU
PLKO	QDYNREGEL	QDYNREGEL	Contains the definition of inspection stages and the conditions that lead to changes in inspection stages.	CHAR	3	NU
PLKO	CHRULE	R_CHRULE	Key that specifies which change procedure must be used for recipe or inspection plan editing.	CHAR	1	C : If change numbers are not activated this value is defaulted as "Empty"
MAPL	PLNNR	PLNNR	Key that uniquely identifies a recipe group.	CHAR	8	S
MAPL	PLNAL	PLNAL	Key that identifies a master recipe within a recipe group.	CHAR	2	S
MAPL	MATNR	MATNR	Material Number for witch the receipe is created	CHAR	18	R
MAPL	WERKS	WERKS_D	Plant	CHAR	4	R
PLPO	DATUV	DATUV	Valid from date	DATS	8	R
PLPO	DATUB	DATUV	Valid to date	DATS	8	R
PLPO	VORNR	VORNR	Determines in which order the operations of a sequence are carried out.	CHAR	4	S
PLPO	PHFLG	PHFLG	ndicator for phases as opposed to operations.	CHAR	1	S
PLPO	PVZNR	PVZNR	Key of the operation to which the phase is subordinated. This field is used for phases but not for operations.	CHAR	1	S
PLPO	ARBID	OBJEKTID	Ressource used to perform the activity	NUMC	8	R : PLPO-ARBID = CRHD-OBJID that represent the ressource CRHD-ARBPL
PLPO	STEUS	STEUS	Determines which business transactions should be executed for the object that belongs to the task list or order (for example scheduling or costing).	CHAR	4	R : Value mapping to be completed during remaining detailed design phase
PLPO	LTXA1	LTXA1	Operation Short Text	CHAR	40	R
PLPO	SPRAS	SPRAS	Language Key	CHAR	2	S
PLPO	BMSCH	BMSCH	Quantity of the material to be produced to which the standard values of the operation refer.	QUAN	13	R
PLPO	MEINH	VORME	Unit of measure used in the operation for the material to be produced.	UNIT	3	R
PLPO	WERKS	WERKS_D	Plant	CHAR	4	R
PLPO	UMREN	CP_UMREN	Denominator for Converting Routing and Operation UoM	DEC	5	C : If Recipe unit of measure (PLKO-PLNME) is different from phase unit of measure (PLPO-MEINH) this field need to be populated
PLPO	UMREZ	CP_UMREZ	Numerator for Converting Routing and Operation UoM	DEC	5	C : If Recipe unit of measure (PLKO-PLNME) is different from phase unit of measure (PLPO-MEINH) this field need to be populated
PLPO	ZMERH	DZMERH	Break Time	QUAN	9	R (If empty = 0)
PLPO	ZEIER	DZEIER	Unit for a Break Time	UNIT	3	R
PLPO	LAR01	LSTAR	Activity Type	CHAR	6	C : If an activity type is used for the ressource used in an operation this field is requiered
PLPO	VGE01	VGWRTEH	Unit of Measurement of Standard Value	UNIT	3	C : If an activity type is used for the ressource used in an operation this field is requiered
PLPO	VGW01	VGWRT	Standard Value	QUAN	9	C : If an activity type is used for the ressource used in an operation this field is requiered
PLPO	LAR02	LSTAR	Activity Type	CHAR	6	C : If an activity type is used for the ressource used in an operation this field is requiered
PLPO	VGE02	VGWRTEH	Unit of Measurement of Standard Value	UNIT	3	C : If an activity type is used for the ressource used in an operation this field is requiered
PLPO	VGW02	VGWRT	Standard Value	QUAN	9	C : If an activity type is used for the ressource used in an operation this field is requiered
PLPO	LAR03	LSTAR	Activity Type	CHAR	6	C : If an activity type is used for the ressource used in an operation this field is requiered
PLPO	VGE03	VGWRTEH	Unit of Measurement of Standard Value	UNIT	3	C : If an activity type is used for the ressource used in an operation this field is requiered
PLPO	VGW03	VGWRT	Standard Value	QUAN	9	C : If an activity type is used for the ressource used in an operation this field is requiered
PLPO	LAR04	LSTAR	Activity Type	CHAR	6	C : If an activity type is used for the ressource used in an operation this field is requiered
PLPO	VGE04	VGWRTEH	Unit of Measurement of Standard Value	UNIT	3	C : If an activity type is used for the ressource used in an operation this field is requiered
PLPO	VGW04	VGWRT	Standard Value	QUAN	9	C : If an activity type is used for the ressource used in an operation this field is requiered
PLPO	LAR05	LSTAR	Activity Type	CHAR	6	C : If an activity type is used for the ressource used in an operation this field is requiered
PLPO	VGE05	VGWRTEH	Unit of Measurement of Standard Value	UNIT	3	C : If an activity type is used for the ressource used in an operation this field is requiered
PLPO	VGW05	VGWRT	Standard Value	QUAN	9	C : If an activity type is used for the ressource used in an operation this field is requiered
PLPO	LAR06	LSTAR	Activity Type	CHAR	6	C : If an activity type is used for the ressource used in an operation this field is requiered
PLPO	VGE06	VGWRTEH	Unit of Measurement of Standard Value	UNIT	3	C : If an activity type is used for the ressource used in an operation this field is requiered
PLPO	VGW06	VGWRT	Standard Value	QUAN	9	C : If an activity type is used for the ressource used in an operation this field is requiered
PLPO	ZERMA	DZERMA	Key which controls how the standard values are calculated (for example, using CAPP or comparison).	CHAR	5	NU
PLPO	LOANZ	LOHNANZ	Number of confirmation slips to be printed for an operation or an activity	DEC	3	NU
PLPO	RFGRP	RUEFAGRP	Classification which combines setup group keys in groups.	CHAR	10	C : If a value in set up activity type is entered in standard value this field is requiered.
PLPO	RFSCH	RUEFASCHLU	Key that specifies who sets up a recipe (for example, machine servicer, setup person or a setup crew). The value from the ressource is the default in the recipe.	CHAR	10	C : If a value in set up activity type is entered in standard value this field is requiered
PLPO	AUFAK	AUSCHUFAK	Scrap factor.	DEC	5	C : If scrap factor is related to an operation and will flow to the process order this field is requiered to be populated
PLPO	UEMUS	UEMUSKZ	Indicator which specifies that overlapping is required. During scheduling the system determines from the minimum send-ahead quantity and the minimum overlap time. Whether the operations can overlap An overlap is only permissible, if the time the operations overlap is larger than the minimum overlap time. When is the start date of the following operation If operations overlap, the next operation can start when the minimum send-ahead quantity has been produced. If a move is necessary, this is taken into account with the minimum move time. The following operation is scheduled so that no interruptions occur.	CHAR	1	C : If operation overlap is permited and requiered to be taken into account during the detailed scheduling process. this field need to be populated. other wise the field is empty
PLPO	UEKAN	UEKANKZ	Indicator which specifies that the operation can be overlapped with the next one if the execution time is to be reduced.	CHAR	1	C : If operation overlap is permited and can be taken into account during the detailed scheduling process to reduce operation time. this field need to be populated. other wise the field is empty
PLPO	ZEIMU	DZEIMU	Unit for the Minimum Overlap Time	UNIT	3	C if PLPO-UEKAN or PLPO-UEMUS is not empty this field need to be populated
PLPO	ZMINU	DZMINU	Shortest time the operation must overlap with the next operation if overlapping is to be economical. The minimum overlap time is taken into account during lead time scheduling.	QUAN	9	C : If overlap is permited or requiered only after a given time. this filed need to be populated
PLPO	SPMUS	SPLITTUNG	Splitting Required	CHAR	1	C : If operation splititng is riquired by the business a value need to be entered. Empty is a valid value
PLPO	SPLIM	SPLITTANZ	Maximum Number of Splits	DEC	3	C : if a value is entered in Splitting this field needs to be populated
PLPO	ZMINB	DZMINB	Minimum Processing Time	QUAN	9	C : if a value is entered in Splitting this field needs to be populated
PLPO	ZLMAX	DZLMAX	Maximum wait time	QUAN	9	C : if not defined by business and there is more than one operation in the recipe this field take the value 1 sec
PLPO	ZLPRO	DZLPRO	Minimum Wait Time	QUAN	9	NU
PLPO	ZWNOR	DZWNOR	Standard Queue Time	QUAN	9	NU
PLPO	ZWMIN	DZWMIN	Minimum Queue Time	QUAN	9	NU
PLPO	ZTNOR	DZTNOR	Standard Move Time	QUAN	9	NU
PLPO	ZTMIN	DZTMIN	Minimum Move Time	QUAN	9	NU
PLPO	ABLIPKZ	ABLIPKZ	Teardown and Wait Occur in Parallel	CHAR	1	NU
PLPO	RSTRA	RSTRA	Reduction Strategy per Operation	CHAR	2	C : Business rule If a reduction strategy is used by business this field need to be populated. Empty is a valid value
PLPO	LIFNR	LIFNR	Supplier number	CHAR	10	C : If the operation is performed at an external partner the subcontractor number need to be entered in this field
PLPO	PLIFZ	PLIFZ	Planned Delivery Time in Days	DEC	3	C : If the operation is performed at an external partner the delivery time in days is to be entered in this field to update planning
PLPO	PREIS	IPREI	Net Price in Purchasing Info Record	CURR	11	C : If the operation is performed at an external partner the operation price need to be entered in this field
PLPO	PEINH	EPEIN	Price unit	DEC	5	C : If the operation is performed at an external partner the operation price unit need to be entered in this field
PLPO	SAKTO	KSTAR	Cost Element	CHAR	10	C : If subcontracting flag in the ressource is entred this field is requiered
PLPO	WAERS	WAERS	Currency Key	CUKY	5	C : If a subcontracting price is entered the price currency is to be entered in this field
PLPO	INFNR	INFNR	Number of purchasing info record	CHAR	10	C : If the operation is subcontracted and a Purchase Info Record exist and to be used for this operation then the PIR number need to be populated in this field
PLPO	ESOKZ	ESOKZ	Purchasing info record category	CHAR	1	C : In case of subcontracting (PLPO-FRDLB) is not empty, value is "3" Otherwise "Empty"
PLPO	EKORG	EKORG	Purchasing Organization	CHAR	4	C : C : If the operation is subcontracting this field need to be populated. Mapping to be provided to link As Is values with To be purch org
PLPO	EKGRP	VG_EKGRP	Purchasing Group for External Processing Activity	CHAR	3	C : If the operation is subcontracting this field need to be populated. Mapping to be provided to link As Is values with To be purch group
PLPO	KZLGF	KZLGF	Indicator: Lot-Size-Independent External Processing	CHAR	1	NU
PLPO	DAUMI	DAUMIN	Minimum activity duration	QUAN	5	NU
PLPO	DAUME	DAUMINE	Unit for the minimum duration	UNIT	3	NU
PLPO	DDEHN	DAUDEHN	Indicator: flexible duration	CHAR	1	C : If the operation duration can be extended this field is marked. empty is valid value
PLPO	ANFKO	ANFKO	Requesting Cost Center	CHAR	10	NU
PLPO	CKSELKZ	CK_SELKZ	Indicator for Relevancy to Costing	CHAR	1	C : If the operation is not relevant for costing this field is empty, otherwise the value is "X"
PLPO	PHFLG	PHFLG	Indicator: Phase	CHAR	1	S
PLPO	FRDLB	CO_FRDLB	Indicator: External Processing Operation with Subcontracting	CHAR	1	C : If an operation is subcontracted this field need to be populated
PLPO	BMVRG	BMVRG	Order Quantity	QUAN	13	C : If the operation quantity/ Unit of measure is different from the header quantity/ unit of measure a conversion factor needs to be populated in this field
PLPO	ANZMA	ANZMS	Nb Of employees	DEC	5	C : If the information is relevant to plan the activities or to send to planning system a value needs to be populated as information
PLPO	DAUNO	DAUNOR	Normal duration	QUAN	5	NU
PLPO	DAUNE	DAUNORE	Normal duration unit	UNIT	3	NU
PLPO	ARBEIT	ARBEIT	Work involved in the activity	CHAR	1	NU
PLPO	ARBEITE	ARBEITE	Unit for work	CHAR	3	NU
PLPO	ANZKAP	ANZKAP	Number of capacities required	CHAR	2	NU
PLPO	BURKS	BURKS	Company code	CHAR	4	NU
PLPO	KALID	WFCID	Factory calendar	CHAR	2	S
PLPO	AUFKT	AFAKT	Execution factor	DEC	3	NU
PLPO	ANZZL	ANZKAP	Number of individual capacities	INT1	3	NU
PLPO	SLWID	SLWID	Key word ID for user-defined fields	CHAR	7	C : If business use user fields to store additional informations this field need to be populated
PLPO	USR00	USRCHAR20	User field with 20 characters	CHAR	20	C : If business use user fields to store additional informations this field need to be populated
PLPO	USR01	USRCHAR20	User field with 20 characters	CHAR	20	C : If business use user fields to store additional informations this field need to be populated
PLPO	USR02	USRCHAR10	User Field with 10 Characters	CHAR	10	C : If business use user fields to store additional informations this field need to be populated
PLPO	USR03	USRCHAR10	User Field with 10 Characters	CHAR	10	C : If business use user fields to store additional informations this field need to be populated
PLPO	USR04	USRQUAN13	User field for quantity (length 10.3)	QUAN	13	C : If business use user fields to store additional informations this field need to be populated
PLPO	USE04	USRUNIT	User field: Unit for quantity fields	UNIT	3	C : If business use user fields to store additional informations this field need to be populated
PLPO	USR05	USRQUAN13	User field for quantity (length 10.3)	QUAN	13	C : If business use user fields to store additional informations this field need to be populated
PLPO	USE05	USRUNIT	User field: Unit for quantity fields	UNIT	3	C : If business use user fields to store additional informations this field need to be populated
PLPO	USR06	USRCURR13	User field for quantity (length 10.3)	CURR	13	C : If business use user fields to store additional informations this field need to be populated
PLPO	USE06	USRCUKY	User field: Unit for quantity fields	CUKY	5	C : If business use user fields to store additional informations this field need to be populated
PLPO	USR07	USRCURR13	User field for quantity (length 10.3)	CURR	13	C : If business use user fields to store additional informations this field need to be populated
PLPO	USE07	USRCUKY	User field: Unit for quantity fields	CUKY	5	C : If business use user fields to store additional informations this field need to be populated
PLPO	USR08	USRDATE	User field for date	DATS	8	C : If business use user fields to store additional informations this field need to be populated
PLPO	USR09	USRDATE	User field for date	DATS	8	C : If business use user fields to store additional informations this field need to be populated
PLPO	USR10	USRFLAG	User-defined field: Indicator for reports	CHAR	1	C : If business use user fields to store additional informations this field need to be populated
PLPO	USR11	USRFLAG	User-defined field: Indicator for reports	CHAR	1	C : If business use user fields to store additional informations this field need to be populated
PLPO	ERFSICHT	QERFSICHT	The recording view is used to specify different characteristic overview screens, which are called up after entering the results recording function	CHAR	2	C : If result recoring is activated and business requiered special characteristic overview screens this field need to be populated. Empty is a valid value
PLMZ	PLNTY	PLNTY	Task List Type	CHAR	1	R
PLMZ	PLNNR	PLNNR	Group	CHAR	8	S
PLMZ	ZAEHL	CIM_COUNT	Counter	NUMC	8	S
PLMZ	ZUONR	ZUONR	Allocation number	CHAR	3	R
PLMZ	DATUV	DATUV	Valid from	DATS	8	R
PLMZ	AENNR	AENNR	Change Number	CHAR	12	NU
PLMZ	LOEKZ	LKENZ	Deletion Indicator	CHAR	1	S
PLMZ	PLNAL	PLNAL	Group Counter	CHAR	2	R
PLMZ	PLNFL	PLNFL	Sequence	CHAR	3	NU
PLMZ	PLNKN	PLNKN	Task list node	NUMC	8	R
PLMZ	STLTY	STLTY	BOM category	CHAR	1	R
PLMZ	STLNR	STNUM	Bill of Material	CHAR	8	R
PLMZ	STLAL	STLAL	Alternative BOM	CHAR	2	R
PLMZ	STLKN	STLKN	Nodes of the BOM item assigned	CHAR	4	R
PLMZ	WERKS_STL	WERKS_STL	Plant	CHAR	4	R
PLMZ	IMENG	IMENG	Component Quantity	NUMC	10	R
PLMZ	IMEIN	KMPME	Component UoM	UNIT	3	S
PLMZ	ANDAT	ANDAT	Created On	DATS	8	S
PLMZ	ANNAM	ANNAM	Created by	CHAR	12	S
PLMZ	AEDAT	CIM_AEDAT	Changed on	DATS	8	S
PLMZ	AENAM	AENAM	Changed By	CHAR	12	S
PLMZ	RGEKZ	RGEKZ	Backflush	CHAR	1	S
PLMZ	PLNTY	PLNTY	Task List Type	CHAR	1	R
PLMZ	PLNNR	PLNNR	Group	CHAR	8	S
PLMZ	ZAEHL	CIM_COUNT	Counter	NUMC	8	S
PLMZ	ZUONR	ZUONR	Allocation number	CHAR	3	R
PLMZ	DATUV	DATUV	Valid from	DATS	8	R
PLMZ	AENNR	AENNR	Change Number	CHAR	12	NU
PLMZ	LOEKZ	LKENZ	Deletion Indicator	CHAR	1	S
PLMZ	PLNAL	PLNAL	Group Counter	CHAR	2	R
PLMZ	PLNFL	PLNFL	Sequence	CHAR	3	NU
PLMZ	PLNKN	PLNKN	Task list node	NUMC	8	R
PLMZ	STLTY	STLTY	BOM category	CHAR	1	R
PLMZ	STLNR	STNUM	Bill of Material	CHAR	8	R
PLMZ	STLAL	STLAL	Alternative BOM	CHAR	2	R
PLMZ	STLKN	STLKN	Nodes of the BOM item assigned	CHAR	4	R
PLMZ	WERKS_STL	WERKS_STL	Plant	CHAR	4	R
PLMZ	IMENG	IMENG	Component Quantity	NUMC	10	R
PLMZ	IMEIN	KMPME	Component UoM	UNIT	3	S
PLMZ	ANDAT	ANDAT	Created On	DATS	8	S
PLMZ	ANNAM	ANNAM	Created by	CHAR	12	S
PLMZ	AEDAT	CIM_AEDAT	Changed on	DATS	8	S
PLMZ	AENAM	AENAM	Changed By	CHAR	12	S
PLMZ	RGEKZ	RGEKZ	Backflush	CHAR	1	S
PLAB	PLNTY	PLNTY	Task List Type	CHAR	1	R
PLAB	PLNAL	PLNAL	Group counter	CHAR	2	S
PLAB	PLNNR	AOB_PLNNR	Number of the Standard Network	CHAR	8	R
PLAB	PLNRN	PLNRN	Group Counter	?	?	R
PLAB	PLNKN	PLNKN	Number of the Task List Node	NUMC	8	R
PLAB	PLNRN	AOB_PLNRN	Number of the Standard Network	CHAR	8	R
PLAB	ALNRN	PLNAL	Group Counter	CHAR	2	R
PLAB	KNNRN	PLNKN	Number of the Task List Node	NUMC	8	R
PLAB	AOBAR	AOBAR	Type of relationship	CHAR	2	R
PLAB	MIMAX	DAUMIMAX	Indicates whether maximum time interval will be considered	CHAR	1	R
PLAB	ZAEHL	CIM_COUNT	Internal counter	NUMC	8	S
PLAB	DATUV	CIM_DATE	Valid-from date	DATS	8	R
PLAB	TECHV	TECHV	Technical status from	CHAR	12	NU
PLAB	AENNR	AENNR	Change Number	CHAR	12	NU
PLAB	ZEINH	AOBDAUEH	Unit for the time interval between relationships	UNIT	3	R
PLAB	DAUER	AOBDAUER	Time Interval Between Relationships	QUAN	5	R
PLAB	DAUKZ	AOBDAUKZ	Indicator for the duration of the relationship	CHAR	1	R
PLAB	VORNC	VORG_NACH	Indicator: maintained after successor	CHAR	1	R
PLAB	NCVOR	NACH_VORG	Indicates whether data after predecessor is maintained	CHAR	1	R
PLAB	LOEKZ	LOEKZ	Asset class marked for deletion	CHAR	1	S
PLAB	KALID	WFCID	Factory Calendar	CHAR	2	S
PLAB	PRZNT	AOB_PRZNT	% used to calc. time interval between predecessor/successor	NUMC	3	C : Business rule if time integrval is calculated this field is populated/ Empty is a valid value
PLAB	PROVG	AOB_PROVG	Key for defining time intervals in a relationship	CHAR	1	C : Business rule if time integrval is calculated this field is populated/ Empty is a valid value
PLAB	WERKS	WERKS_D	Plant	CHAR	4	R
PLAB	ANDAT	ANDAT	Date Record Created On	DATS	8	S
PLAB	ANNAM	ANNAM	User who created record	CHAR	12	S
PLAB	DAUERMAX	AOBDAUERMAX	Maximum time interval for relationship	QUAN	5	R
PLAB	VALID_TO		Valid-to date	DATS	8	R
PLAB	LOEKZ_INHERITED		Deletion Indicator	CHAR	1	S
PLMK	PLNTY	PLNTY	Task List Type	CHAR	1	R
PLMK	PLNNR	PLNNR	Key for Task List Group	CHAR	8	S
PLMK	PLNKN	PLNKN	Number of the Task List Node	NUMC	8	S
PLMK	KZEINSTELL	QKZEINSTMK	Characteristic Type : Quantitative or Qualitative	CHAR	1	S
PLMK	MERKNR	QMERKNRP	Inspection Characteristic Number	NUMC	4	R
PLMK	ZAEHL	CIM_COUNT	Internal counter	NUMC	8	S
PLMK	GUELTIGAB	DATUV	Valid-From Date	DATS	8	R
PLMK	SERNV	TECHV	Technical status from	CHAR	12	S
PLMK	LOEKZ	LKENZ	Deletion Indicator	CHAR	1	S
PLMK	PARKZ	PARKZ	Indicator: inactive changes	CHAR	1	R
PLMK	AENDERGNR	AENNR	Change Number	CHAR	12	NU
PLMK	ERSTELLER	ANNAM	User who created record	CHAR	12	S
PLMK	ERSTELLDAT	ANDAT	System Date on Which Data Record Was Created	DATS	8	S
PLMK	AENDERER	QAENDERER	Name of User Who Last Changed Data Record	CHAR	12	S
PLMK	AENDERDAT	QDATUMAEND	System Date on Which Data Record Was Changed	DATS	8	S
PLMK	STEUERKZ	QMKCONTROL	Cntrl Indicator String for Insp. Char./Master Insp. Char.	CHAR	30	S
PLMK	QMTB_WERKS	Q_METH_PLANT	Plant for Inspection Method	CHAR	4	S
PLMK	PMETHODE	QPMETHODE	An inspection method describes how to inspect an inspection characteristic.	CHAR	8	S
PLMK	PMTVERSION	QVERSNRPM	Version Number of Inspection Method	CHAR	6	S
PLMK	QPMK_REF	QKZ_REF	Reference to Master Insp. Characteristic in Task List	CHAR	1	R
PLMK	QPMK_ZAEHL	QZAEHLER	Plant for Master Inspection Characteristic	CHAR	4	R
PLMK	VERWMERKM	QMERKNR	An inspection characteristic describes what is to be inspected	CHAR	8	R
PLMK	MKVERSION	QVERSNRMK	Version Number of Master Inspection Characteristic	CHAR	6	S
PLMK	MKVERSDAT	QVERSDAT	Key Date for Version Selection	DATS	8	S
PLMK	MERKGEW	QMERKGEW	Classification of inspection characteristics according to their weighting (importance).	CHAR	2	S
PLMK	PROBENR	QPROBEPL	Partial Sample No. for Inspection Charac. in Task List	NUMC	3	NU
PLMK	PRUEFQUALI	QPRQUALIF	Qualification that an inspector must have and, if necessary, validate in order to be able to conduct an inspection.	CHAR	5	S
PLMK	TOLERANZSL	QTOLERANZ	Tolerance Key	CHAR	4	S
PLMK	KURZTEXT	QTXT_CHA	Short Text for Inspection Characteristic	CHAR	40	S
PLMK	LTEXTKZ	QLTEXTKZ	Inspection Characteristic Long Text Exists	CHAR	1	S
PLMK	LTEXTSPR	SPRAS	Language Key	LANG	1	S
PLMK	LTEXTEKZ	QKZPRZIEH	Sample-Drawing Text Exists	CHAR	1	S
PLMK	LTXTENTSPR	SPRAS	Language Key	LANG	1	S
PLMK	STELLEN	QSTELLEN	define the accuracy (number of decimal places), to which the value is calculated.	INT1	3	S
PLMK	MASSEINHSW	QMASSEH	Unit of Measurement in Which Quantitative Data Is Stored	UNIT	3	S
PLMK	SOLLWERT	QSOLLWERTE	Value of a quantitative characteristic, from which the actual value of the inspection characteristic should deviate as little as possible.	FLTP	16	R
PLMK	SOLLWNI	QNINITIAL	Value Not Initial If Set	CHAR	1	S
PLMK	TOLERANZOB	QTOLOB	Upper limit value for the actual value of an inspection characteristic.	FLTP	16	C : This field represent the upper limit of the characteristic value for the test results. business need to define the value
PLMK	TOLOBNI	QNINITIAL	Value Not Initial If Set	CHAR	1	S
PLMK	TOLERANZUN	QTOLUN	Lower limiting value for the actual value of an inspection characteristic.	FLTP	16	C : This field represent the lower limit of the characteristic value for the test results. business need to define the value
PLMK	TOLUNNI	QNINITIAL	Value Not Initial If Set	CHAR	1	S
PLMK	KLASANZAHL	QKLASSZAHL	Number of Value Classes for Inspection Results	INT1	3	NU
PLMK	KLASBREITE	QKLASSBR	Class Width	FLTP	16	NU
PLMK	KLASBRNI	QNINITIAL	Value Not Initial If Set	CHAR	1	NU
PLMK	KLASMITTE	QKLASSMIT	Class Midpoint	FLTP	16	NU
PLMK	KLASMINI	QNINITIAL	Value Not Initial If Set	CHAR	1	NU
PLMK	GRENZEOB1	QGRENZOB1	Upper limit value of a user-specified limit, for example, a warning limit. The system does not use the contents of this field. This field provides a place to store a user-specified limit value that is relevant	FLTP	16	NU
PLMK	GRENZOB1NI	QNINITIAL	Value Not Initial If Set	CHAR	1	NU
PLMK	GRENZEUN1	QGRENZUN1	Lower limiting value of a user-specified limit, for example, a warning limit The system does not use the contents of this field. This field provides a place to store a user-specified limit value that is relevant for a quantitative characteristic.	FLTP	16	NU
PLMK	GRENZUN1NI	QNINITIAL	Value Not Initial If Set	CHAR	1	NU
PLMK	GRENZEOB2	QGRENZOB2	Upper limit value of a user-specified limit, for example, a warning limit. The system does not use the contents of this field. This field provides a place to store a user-specified limit value that is relevant	FLTP	16	NU
PLMK	GRENZOB2NI	QNINITIAL	Value Not Initial If Set	CHAR	1	NU
PLMK	GRENZEUN2	QGRENZUN2	Lower limiting value of a user-specified limit, for example, a warning limit The system does not use the contents of this field. This field provides a place to store a user-specified limit value that is relevant for a quantitative characteristic.	FLTP	16	NU
PLMK	GRENZUN2NI	QNINITIAL	Value Not Initial If Set	CHAR	1	NU
PLMK	PLAUSIOBEN	QPLAUSIOB	Maximum plausible value of a plausibility limit.It protects against the recording and processing of invalid or improbable values	FLTP	16	C : if an additional control is needed to ensure that the users don't enter values that not make sens. this field need to be populated
PLMK	PLAUSIOBNI	QNINITIAL	Value Not Initial If Set	CHAR	1	S
PLMK	PLAUSIUNTE	QPLAUSIUN	Minimum plausible value of a plausibility limit.This field is used only for results recording of quantitative characteristics. It protects against the recording and processing of invalid or improbable values.	FLTP	16	C : if an additional control is needed to ensure that the users don't enter values that not make sens. this field need to be populated
PLMK	PLAUSIUNNI	QNINITIAL	Value Not Initial If Set	CHAR	1	S
PLMK	TOLERWEIOB	QTOLWOB	Amount by which the specification limit is temporarily increased or decreased.	FLTP	16	NU
PLMK	TOLWOBNI	QNINITIAL	Value Not Initial If Set	CHAR	1	S
PLMK	TOLERWEIUN	QTOLWUN	Amount by which the specification limit is temporarily increased or decreased.	FLTP	16	NU
PLMK	TOLWUNNI	QNINITIAL	Value Not Initial If Set	CHAR	1	S
PLMK	TOLERWAB	QTOLWAB	Date from Which the Tolerance Change Is Valid	DATS	8	C : If PLMK-TOLERWEIOB or PLMK-TOLERWEIUN is not empty this field need to be populated;
PLMK	TOLERWBIS	QTOLWBIS	Date Until Which the Tolerance Change Is Valid	DATS	8	C : If PLMK-TOLERWEIOB or PLMK-TOLERWEIUN is not empty this field need to be populated;
PLMK	STICHPRVER	QSTICHVERF	Sampling Procedure in Inspection Characteristic	CHAR	8	R
PLMK	FAKPLANME	QUMREN	Factor for Converting MatUnitOfMeasure to SampUnitOfMeasure	FLTP	16	S
PLMK	FAKPROBME	QUMRENPME	Factor for Converting SampUnitOfMeasure to MatUnitOfMeasure	FLTP	16	S
PLMK	PROBEMGEH	QPROBME	Sample Unit of Measure	UNIT	3	S
PLMK	PRUEFEINH	QPROBEFAK	Sample Quantity Factor for Sample(Mult. Sample Unit of Msr.)	DEC	5	NU
PLMK	DYNKRIT	QDYNSTRING	String for Dynamic Modification Criteria (Database Relevant)	CHAR	10	NU
PLMK	FORMELSL	QFORMELSL	Check and Calculate Formula in QM	CHAR	1	NU
PLMK	FORMEL1	QFORMEL	Formula Field	CHAR	60	NU
PLMK	FORMEL2	QFORMEL	Formula Field	CHAR	60	NU
PLMK	CODEGR9U	QCODEGRPU	Code from a code group in the defect catalog (catalog type 9) that has been assigned to a quantitative characteristic with a lower specification limit.	CHAR	8	C : If a set of values is defined for the lower value and the user need to be forced with those values an entry need to be populated
PLMK	CODE9U	QCODEU	Code from a code group in the defect catalog (catalog type 9) that has been assigned to a quantitative characteristic with a lower specification limit.	CHAR	4	C : If a set of values is defined for the lower value and the user need to be forced with those values an entry need to be populated
PLMK	CODEVR9U	QVERSNR	Version Number	CHAR	6	S
PLMK	CODEGR9O	QCODEGRPO	Code group from the defect catalog (catalog type 9) that has been assigned to a quantitative characteristic with an upper specification limit.	CHAR	8	NUC : If a set of values is defined for the upper value and the user need to be forced with those values an entry need to be populated
PLMK	CODE9O	QCODEO	Code group from the defect catalog (catalog type 9) that has been assigned to a quantitative characteristic with an upper specification limit.	CHAR	4	NUC : If a set of values is defined for the upper value and the user need to be forced with those values an entry need to be populated
PLMK	CODEVR9O	QVERSNR	Version Number	CHAR	6	S
PLMK	KATAB1	QKTTAB	Catalog Entry Is a Selected Set	CHAR	1	C : Depending on the entries in the defect code group
PLMK	KATALGART1	QKATAUSW	Main category by which code groups and codes are classified according to their contents (e.g. characteristic attributes, defect types, usage decisions).	CHAR	1	C : Depending on the entries in the defect code group
PLMK	AUSWMENGE1	QCGRAUSW	Assigned Code Group or Selected Set	CHAR	8	S
PLMK	AUSWMGWRK1	QWERKAUSW	Plant of the Assigned Selected Set	CHAR	4	S
PLMK	AUSWVERS1	QVERSNR	Version Number	CHAR	6	S
PLMK	AUSWDAT1	QVERSDAT	Key Date for Version Selection	DATS	8	S
PLMK	KATAB2	QKTTAB	Catalog Entry Is a Selected Set	CHAR	1	C : Depending on the entries in the defect code group
PLMK	KATALGART2	QKATAUSW	Catalog Type of Assigned Code Group or Selected Set	CHAR	1	C : Depending on the entries in the defect code group
PLMK	AUSWMENGE2	QCGRAUSW	Assigned Code Group or Selected Set	CHAR	8	S
PLMK	AUSWMGWRK2	QWERKAUSW	Plant of the Assigned Selected Set	CHAR	4	S
PLMK	AUSWVERS2	QVERSNR	Version Number	CHAR	6	S
PLMK	AUSWDAT2	QVERSDAT	Key Date for Version Selection	DATS	8	S
PLMK	KATAB3	QKTTAB	Catalog Entry Is a Selected Set	CHAR	1	C : Depending on the entries in the defect code group
PLMK	KATALGART3	QKATAUSW	Catalog Type of Assigned Code Group or Selected Set	CHAR	1	C : Depending on the entries in the defect code group
PLMK	AUSWMENGE3	QCGRAUSW	Assigned Code Group or Selected Set	CHAR	8	S
PLMK	AUSWMGWRK3	QWERKAUSW	Plant of the Assigned Selected Set	CHAR	4	S
PLMK	AUSWVERS3	QVERSNR	Version Number	CHAR	6	S
PLMK	AUSWDAT3	QVERSDAT	Key Date for Version Selection	DATS	8	S
PLMK	KATAB4	QKTTAB	Catalog Entry Is a Selected Set	CHAR	1	C : Depending on the entries in the defect code group
PLMK	KATALGART4	QKATAUSW	Catalog Type of Assigned Code Group or Selected Set	CHAR	1	C : Depending on the entries in the defect code group
PLMK	AUSWMENGE4	QCGRAUSW	Assigned Code Group or Selected Set	CHAR	8	S
PLMK	AUSWMGWRK4	QWERKAUSW	Plant of the Assigned Selected Set	CHAR	4	S
PLMK	AUSWVERS4	QVERSNR	Version Number	CHAR	6	S
PLMK	AUSWDAT4	QVERSDAT	Key Date for Version Selection	DATS	8	S
PLMK	KATAB5	QKTTAB	Catalog Entry Is a Selected Set	CHAR	1	C : Depending on the entries in the defect code group
PLMK	KATALGART5	QKATAUSW	Catalog Type of Assigned Code Group or Selected Set	CHAR	1	C : Depending on the entries in the defect code group
PLMK	AUSWMENGE5	QCGRAUSW	Assigned Code Group or Selected Set	CHAR	8	S
PLMK	AUSWMGWRK5	QWERKAUSW	Plant of the Assigned Selected Set	CHAR	4	S
PLMK	AUSWVERS5	QVERSNR	Version Number	CHAR	6	S
PLMK	AUSWDAT5	QVERSDAT	Key Date for Version Selection	DATS	8	S
PLMK	DUMMY10	QTXT10	This field is used to store information only. The system does not use the contents of this field. Its only purpose is to provide a place to store information that is relevant to an object	CHAR	10	C : If text information is requiered this field can be populated
PLMK	DUMMY20	QTXT20	This field is used to store information only. The system does not use the contents of this field. Its only purpose is to provide a place to store information that is relevant to an object	CHAR	20	C : If text information is requiered this field can be populated
PLMK	DUMMY40	QTXT40	This field is used to store information only. The system does not use the contents of this field. Its only purpose is to provide a place to store information that is relevant to an object	CHAR	40	C : If text information is requiered this field can be populated
PLMK	CHARACT_ID1	QCHARACT_ID1	Characteristic Description for Quality Data Exchange	CHAR	40	NU
PLMK	QERGDATH	QERGDATHPL	Planned Results Data Origin	CHAR	2	NU
PLMK	EEANTVERF	QEANTVERF	Fraction Calculation	CHAR	2	NU
PLMK	QDYNREGEL	QDYNREGEL	Dynamic Modification Rule	CHAR	3	NU
PLMK	DYNMERKREF	QMERKDYN	Characteristic (in Plan) whose Q-Level Will Be Copied	NUMC	4	NU
PLMK	PZLFH	QPZLFH	Assigned Test Equipment	NUMC	8	NU
PLMK	CODEGRQUAL	QCODEGRPQL	Defect Code Group for General Rejection	CHAR	8	NU
PLMK	CODEQUAL	QCODEQL	Defect Code for Rejection: General	CHAR	4	NU
PLMK	SPCKRIT	QSPCKRIT	SPC Criterion	CHAR	3	NU
PLMK	INPPROC	QINPPROC	Parameters for Input Processing in QM Results Recording	CHAR	3	NU
PLMK	RES_PLAN	QP_RESPLAN	Response Plan	CHAR	3	NU
PLMK	CTRMETH	QP_CTRMETH	Control Method	CHAR	3	NU
PLMK	CHAORIG	QP_CHAORIG	Inspection Characteristic Origin	CHAR	3	NU
PLMK	CHAORIG_GUID	QP_CHAORIG_GUID	Reference to Characteristic That Was Adopted	RAW	16	NU
PLMK	CHAR_RELEVANCE		Relevance of Characteristic for Inspection			NU
PLMK	QP_CHAORIG_ID	QMIP_CHAORIG_ID	Original Identification for Characteristic	CHAR	40	NU
PLMK	CHARGROUP		Characteristic Group			S
PLMK	CHARGROUP_CREF		Source Characteristic of Characteristic Group Division			NU
PLMK	DIVISIONINT		Internal Division ID			NU
PLMK	VALID_TO_ON_DB		Valid-to date			S
PLMK	VERSN		Routing Version			NU
PLMK	VERSN_SOURCE		Source Routing Version			NU
PLMK	VERSN_SOURCE_PLNKN		Task List Version: Number of source list node			NU
PLMK	VERSN_SOURCE_ME		Task List Version: Souce Inspection Characteristic Number			NU

Data Cleansing

ID	Criticality	Error Message/Report Description	Rule	Output	Source System
1039-1	C1	Master Recipe has a flag for deletion	NO Master recipes with flag for deletion won't be migrated	Deletion Flag for master recipe	PF2/WP2
1039-2	C1	Inactive status (source system might have various statuses to identify)	Inactive Master recipes won't be migrated	Mark all inactive Master recipe	PF2/WP2
1039-3	C1	Not a part of any active FG BOM . Here data cleansing would be necessary or this could be a case of outsourced/subcontracting SFG BOM.	SFG Active Master Recipe, only for active FG	SFG active and part of the FG PDS must be considered to migrate	PF2/WP2
1039-4	C1	If all the parent part/s are inactive, then this SFG is not relevant for migration.	SFG part of inactive FG not considered for migration	SFG is part of a Inactive FG	PF2/WP2
1039-5	C1	No usage in the past 3 years.	Master recipes not used for the last 3 years are not considered to migrate	Remove all Master Recipes with no usage for the last three years	PF2 / WP2
1039-6	C1	BOM status is inactive	Master Recipe to include a inactive BOM not to be considered	BOM is inactive	PF2/WP2

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:

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

Req #	Requirement Description	Team Responsible
1	Extract data from source system based on relevancy rule	Data Team
2	Google Sheet report pre-populated with PF2 and WP2 information to be generated based on relevancy criteria.	Data Team
3	Sinity Extraction in SQL / Excel to check the result	Sinity/ Data Team

Selection Screen

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 with exception of some fields which require transformation as mentioned in the transformation rule.

DCT Rules

Field Name	Field Description	Rule

Extraction Dependencies

Item #	Step Description	Team Responsible
1	Source System Availability Ensure that the source database or application is accessible. Confirm that necessary credentials and permissions are granted	Syensqo IT
2	Data Structure Identify relationships between tables, views, and stored procedures.	Syniti
3	Referential Integrity Ensure dependent records are extracted together.	Syniti
4	Extraction Methodology Define whether extraction is full, incremental, or delta-based. Establish batch processing schedules for large datasets.	Syniti
5	Performance and Scalability Considerations Optimize extraction queries to prevent system overload. Ensure network bandwidth supports data transfer volumes.	Syniti
6	Security and Compliance Adhere to regulatory standards for sensitive information if applicable	Syniti
7	Data cleansing of legacy Master Recipe If standardization within the DCT begins using relevant data from PF2 and WP2 before the cleansing is finalized, it is understood that the business will take due diligence to ensure any subsequent delta cleansing is verified and aligned within the DCT.	Business

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:

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
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
1	Obtain DCT Sign-off from Business	SyWay Data Team
2	<Add steps from Syniti Migrate here>	SyWay Data Team
3	Review and Validate Error and Preload Reports	SyWay Data Team
4	Generate Load Files	SyWay Data Team

Transformation Rules

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

Transformation Mapping

Mapping Table Name	Mapping Table Description

Transformation Dependencies

List the steps that need to occur before transformation can commence

Item #	Step Description	Team Responsible
1	Ensure DCT tables completeness	SyWay Data Team
2	Value Mappings are according to the latest design - <List of Value Mappings>	SyWay Data Team

Pre-Load Validation

Project Team

Completeness

Task	Action
Verify Record Count	Data team to verify that the total number of relevant records from the source systems is equal to the total number of records in the Preload and Load Sheets.

Accuracy

Task

Action

Conversion Accuracy

Data team to verify that all fields below meet pass the checks:

1. Mandatory Fields

2. Field and Value Mapping Correctness

3. Null Checks

4. Text Length Checks

Review error reports

Review and correct the errors. Achieve a zero-error record count as much as possible. Raise defects for data remediated and requiring a correction in the source data.

Business

Completeness

Task	Action
Verify Record Count	Business team to verify that the total number of relevant records from the source systems is equal to the total number of records in the Preload and Load Sheets.

Accuracy

Task	Action
Conversion Accuracy	Business to verify that all the data in the load table/file is accurate as per endorsed transformation/mapping rules (and signed-off data)

Load

The load process includes:

Execute the automated data load into target system using load tool or product the load file if the load must be done manually
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
1	Go to <Load Tool>	SyWay Data Team
2	Load 3 records for < > to validate if data is loaded successfully without errors	SyWay Data Team
3	Proceed with full load if steps 2 and 3 are validated	SyWay Data Team
4	Validate few records loaded by accessing standard transactions from S/4HNA eg. MDO4	SyWay Data Team
5	Generate post load report if step 5 is validated	SyWay Data Team

Load Phase and Dependencies

Configuration

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

Error Type	Error Description	Action Taken

Post-Load Validation

Project Team

Completeness

Task	Action
Verify Count	Data team to verify the record count created in target S/4 HANA by accessing post load reports in Sinity Migrate or standard reports from S/4 HANA.
Verify Logs	Check if there is data that failed to load and perform the necessary actions (e.g. register as post load issue, or attempt to load the record again, etc.).

Accuracy

Task	Action
Conversion Accuracy	Data team to verify that the Measuring Point data in target S/4 HANA were loaded correctly via Sinity Migrate post load reports or standard reports from S/4 HANA.

Business

Completeness

Task	Action
Verify Count	Download Post Load Reports from Sinity Migrate and verify that the record count loaded in the target S/4 HANA is the same count as of the endorsed load file.

Accuracy

Task	Action
Conversion Accuracy	Verify that the Measuring Point data in target S/4 HANA were loaded correctly via dspMigrate post load reports or standard reports from S/4 HANA.

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.

Change log

Version	Published	Changed By
CURRENT (v. 9)	Apr 29, 2026 08:28	ULLAH-ext, Colin
v. 86	Apr 28, 2026 09:59	ULLAH-ext, Colin
v. 85	Apr 22, 2026 14:34	ULLAH-ext, Colin
v. 84	Apr 22, 2026 06:52	ULLAH-ext, Colin
v. 83	Apr 21, 2026 11:54	ULLAH-ext, Colin
v. 82	Apr 17, 2026 08:27	ULLAH-ext, Colin
v. 81	Apr 14, 2026 13:50	ULLAH-ext, Colin
v. 80	Mar 26, 2026 11:14	ULLAH-ext, Colin
v. 79	Feb 26, 2026 16:18	ULLAH-ext, Colin
v. 78	Feb 24, 2026 11:55	ULLAH-ext, Colin

Go to Page History

Workflow history

Title	Last Updated By	Updated	Status
There are no pages at the moment.

From Mar 26, 2026 to Apr 29, 2026	Actor	Type	Activity	Version
Update in progress	ULLAH-ext, Colin	Edit	updated the page at 11:14 am
Mar 18, 2026
	WENNINGER-ext, Sascha	State	changed state to Update in progress at 5:51 pm	v79
From Nov 13, 2025 to Feb 26, 2026
Edited following Tech Review	ULLAH-ext, Colin	Edit	updated the page at 5:37 pm
Nov 10, 2025
	AIT OUAKLI-ext, Amine	Comment	commented 10:41 am The purchasing view is not a mandatory perquisite to create a master recipe. Only for the cases of subcontracting
	AIT OUAKLI-ext, Amine	Comment	commented 10:40 am The PPDS view is not a mandatory perquisite. Most likely some materials will not have a PPDS view. One example is recipes for mass balance process.
	ULLAH-ext, Colin	Edit	updated the page at 10:31 am

Workflow history

Space shortcuts

Page tree

CNV-1039 Master Recipe

Purpose

Conversion Scope

Additional Information

Multi-language Requirement

Document Management

Legal Requirement

Special Requirements

Target Design

Data Cleansing

Conversion Process

Data Privacy and Sensitivity

Extraction

Extraction Run Sheet

Selection Screen

Data Collection Template (DCT)

Extraction Dependencies

Transformation

Transformation Run Sheet

Transformation Mapping

Transformation Dependencies

Pre-Load Validation

Project Team

Completeness

Accuracy

Business

Completeness

Accuracy

Load

Load Run Sheet

Configuration

Conversion Objects

Error Handling

Post-Load Validation

Project Team

Completeness

Accuracy

Business

Completeness

Accuracy

Key Assumptions

See also

Change log

Workflow history