Status
Owner	ULLAH-ext, Colin
Stakeholders	GERVAIS, Pascal

Purpose

The purpose of this document is to define the conversion approach to create 1038 Material BOM (Usage 1 & 4) in S/4 HANA.

Bills of Material (BOMs) are core master data objects in SAP that play a critical role across all manufacturing processes. They define the complete product structure by specifying the components—such as raw materials, semi-finished goods, and subassemblies—required to produce semi-finished and finished products. By providing a structured breakdown of materials, BOMs serve as the foundation for effective production planning, costing, and shop-floor execution.

BOMs take a central role in production master data, as they define the component structure required to manufacture semi-finished and finished goods. The migration of BOMs is therefore critical to ensure continuity of manufacturing activities in S/4HANA. Prior to migration, it is essential to perform exhaustive data cleansing, as some plants are currently experiencing issues with BOM consistency and validity.

In SAP, BOMs work in conjunction with the Master Recipe and Production Version to ensure consistent, controlled, and accurate manufacturing processes. Because of their central role in production master data, the migration of BOMs to S/4HANA is business-critical to safeguard continuity of operations.

Prior to migration, it is essential to perform comprehensive data cleansing. This includes validating that only active, relevant, and harmonized BOM records are carried forward. Special attention must be given to plants where inconsistencies or data quality issues have been identified, ensuring that obsolete, duplicate, or invalid BOMs are excluded. This preparation will secure a clean, reliable, and compliant BOM dataset in the target S/4HANA system.

All valid BOMS will be migrated to the S/4 HANA System, for all the relevant plants and for all the Semifinished and finished materials in scope (refer to CNV-9070).

Conversion Scope

The scope of this document covers the approach for converting active 1038 Data register for BOMS from Legacy Source Systems into S/4HANA following the1038 Master Data Design Standard.

The data The data from legacy system includes:

• Active BOMs in scope (> 3 years of use) that are linked to production orders, process orders, or costing runs
• BOMs without deletion flags, ensuring only valid and relevant records are migrated
• BOMs with active material components in active plants, ensuring alignment with migrated Material Master data
• BOMs assigned to in-scope plants, based on the To-Be Plant Mapping (considering new plant definitions)
• BOMs with valid usages (Usage 1 – Production, Usage 4 – Plant Maintenance) and valid alternative BOMs
• BOMs with valid units of measure (UoM), consistent with T006 conversion rules
• Semi-finished and finished materials covered under the migration scope (refer to CNV-9070)

The data from legacy system excludes

• Inactive BOMs not used in production or costing within the last three (3) years.

• BOMs marked for deletion in ECC.

• BOMs belonging to plants that are deleted or out of scope, based on To-Be Plant Mapping.

• BOMs containing obsolete or inactive material components that are not migrated to S/4HANA.

• Duplicate or redundant alternative BOMs, where only harmonized and validated BOMs will be retained.

• BOMs with invalid or inconsistent UoM assignments or without proper conversion maintained.

• Local or legacy-specific BOMs that are not aligned with harmonized corporate standards.

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	BOMS will be extracted from PF2 and WP2	TBD	S/4 HANA	TBD
DCT	BOMS for Plant / BOMS combination which do not have data existing from PF2 and PF2	TBD	S/4 HANA	TBD

Additional Information

Multi-language Requirement

N/A

Document Management

N/A

Legal Requirement

N/A

Special Requirements

N/A

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	MDS Field Mapping in Scope	Field Value in MDS
1	MAST	MATNR	MATNR	Material	Material Code for the target product of the BOM	18	R		Legacy Material to New material mapping
2	MAST	WERKS	WERKS_D	Plant	organisational unit used by logistic and production representing a physically independent facility where stock and activities are managed	4	R		Legacy Plant to New Plant Mapping
3	MAST	STLAN	STLAN	Usage	Indicator that defines for what this BOM is used for.	1	R		Value is either 1,2,3,4,5,8,P
4	MAST	STLNR	STNUM	BOM	Internal BOM number assigned by the system	8	S
5	MAST	STLAL	STALT	Alternative	number of the alternative BOM, in case the same material can be produced with different ones	2	S
6	MAST	LOSVN	LOSVN	From Lot Size	This BOM can be selected only if we produce at least this qty	13	S
7	MAST	LOSBS	LOSBS	To Lot Size	This BOM can be selected only if we produce no more than this qty	14	S
8	MAST	ANDAT	ANDAT	Created On	Date of BOM creation, automatically assigned by the system	8	S
9	MAST	ANNAM	ANNAM	Created by	User who created the BOM, automatically assigned by the system	12	S
10	MAST	AEDAT	AEDAT	Changed On	Date of last BOM change, automatically assigned by the system	8	S
11	MAST	AENAM	AENAM	Changed By	User who changed the BOM, automatically assigned by the system	12	S
12	MAST	CSLTY	CSLTY	Configured matl	Not relevant for Syensqo	1	NU
13	MAST	MATERIAL_BOM_KE	MATERIAL_BOM_KE	MBOM key	internal Key, automatically assigned by the system		S
14	STKO	STLTY	STLTY	BOM category	Identifier for Material/Equipment/WBS/Functional Location, Document BOM etc. Only Material BOMs are relevant here: "M"	1	S
15	STKO	STLNR	STNUM	BOM	Internal BOM number assigned by the system	8	S
16	STKO	STLAL	STALT	Alternative	number of the alternative BOM, in case the same material can be produced with different ones	2	S
17	STKO	STKOZ	CIM_COUNT	Counter	Internal counter assigned by the system	8	S
18	STKO	DATUV	DATUV	Valid From	Validity start of the BOM. It is by default the creation date of the BOM, unless differently specified by the user	8	R
19	STKO	TECHV	TECHV	Tech st from	technical start	12	NU
20	STKO	AENNR	AENNR	Change Number	Number of the object used to maintain this BOM together with other technical objects in a single engineering change. Not used in Syensqo	12	NU
21	STKO	LKENZ	LKENZ	Deletion Ind.	Indicator of deletion performed via Change Number. Not used	1	NU
22	STKO	LOEKZ	LOKNZ	Deletion flag	Mark for Deletion	1	C
23	STKO	VGKZL	VGKZL	Prev hdr countr	internal previous counter	8	S
24	STKO	ANDAT	ANDAT	Created On	Date of BOM creation, automatically assigned by the system	8	S
25	STKO	ANNAM	ANNAM	Created by	User who created the BOM, automatically assigned by the system	12	S
26	STKO	AEDAT	AEDAT	Changed On	Date of last BOM change, automatically assigned by the system	8	S
27	STKO	AENAM	AENAM	Changed By	User who changed the BOM, automatically assigned by the system	12	S
28	STKO	BMEIN	BASME	Base UoM	Unit of measure for the Base qty	3	R
29	STKO	BMENG	BASMN	Base quantity	Quantity of the target material produced using the component's quantities we will define in the items.	13	R
30	STKO	CADKZ	CADKZ	CAD Indicator	BOM created by CAD system	1	NU
31	STKO	LABOR	LABOR	Lab/Office	Identifier of the organisational structure (Laboratory, Master Data office, etc) responsible to maintain this BOM	3	C
32	STKO	LTXSP	LTXSP_CP	Long Text Lang	Long text	1	R
33	STKO	STKTX	STKTX	Alt Text	Alternative Long text	40	NU
34	STKO	STLST	STLST	BOM Status	Status of the BOM, used to restrict its usage during creation or obsolescence phases or to block it if required	2	R
35	STKO	WRKAN	WRKAN	Created in plt	Plant on which BOM has been created	4	S
36	STKO	DVDAT	DVDAT	Scheduled on	Date of Last date change of the "Valid From" field	8	S
37	STKO	DVNAM	DVNAM	Date shifted by	User who performed the last change of Valid From	8	S
38	STKO	AEHLP	CC_AEHLP	Helper Field	Date shift Hierarchy indicator	2	S
39	STKO	ALEKZ	CS_ALEKZ	ALE indicator	BOM has been created by remote system	1	NU
40	STKO	GUIDX	CS_GUIDB	Guid	Internal change status Header indicator	16	S
41	STKO	VALID_TO		to	End Validity date of the BOM. By default 31.12.9999, unless differently specified by the user	8	R		default 31.12.9999
42	STKO	ECN_TO		Change No. To	Identifier of the Change number that created a subsequent version of the BOM, from which the current one is not valid anymore. Not used		NU
43	STKO	BOM_VERSN		BOM Version	Version, not used in Syensqo		NU
44	STKO	VERSNST		BOM Version Status	Status of the version, not used		NU
45	STKO	VERSNLASTIND		Latest Rel Version	last version released. Not used		NU
46	STKO	LASTCHANGEDATET		Time Stamp	Time stamp	8	S
47	STKO	BOM_AIN_IND		BOM to AIN Handover	BOM copied to Asset Intelligent Network, not used		NU
48	STKO	BOM_PREV_VERSN		Predecessor Version	Version of the predecessor BOM, not used		NU
49	STKO	DUMMY_STKO_INCL		Ext. Include	Extension include exists		S
50	STAS	STLTY	STLTY	BOM category	STAS table is purely internal, never maintained by a user. Technical fields to manage the link between BOM header and items	1	S
51	STAS	STLNR	STNUM	BOM	STAS table is purely internal, never maintained by a user. Technical fields to manage the link between BOM header and items	8	S
52	STAS	STLAL	STALT	Alternative	STAS table is purely internal, never maintained by a user. Technical fields to manage the link between BOM header and items	2	S
53	STAS	STLKN	STLKN	Item node	STAS table is purely internal, never maintained by a user. Technical fields to manage the link between BOM header and items	8	S
54	STAS	STASZ	CIM_COUNT	Counter	STAS table is purely internal, never maintained by a user. Technical fields to manage the link between BOM header and items	8	S
55	STAS	DATUV	DATUV	Valid From	STAS table is purely internal, never maintained by a user. Technical fields to manage the link between BOM header and items	8	S
56	STAS	TECHV	TECHV	Tech st from	STAS table is purely internal, never maintained by a user. Technical fields to manage the link between BOM header and items	12	S
57	STAS	AENNR	AENNR	Change Number	STAS table is purely internal, never maintained by a user. Technical fields to manage the link between BOM header and items	12	S
58	STAS	LKENZ	LKENZ	Deletion Ind.	STAS table is purely internal, never maintained by a user. Technical fields to manage the link between BOM header and items	1	S
59	STAS	ANDAT	ANDAT	Created On	STAS table is purely internal, never maintained by a user. Technical fields to manage the link between BOM header and items	8	S
60	STAS	ANNAM	ANNAM	Created by	STAS table is purely internal, never maintained by a user. Technical fields to manage the link between BOM header and items	12	S
61	STAS	AEDAT	AEDAT	Changed On	STAS table is purely internal, never maintained by a user. Technical fields to manage the link between BOM header and items	8	S
62	STAS	AENAM	AENAM	Changed By	STAS table is purely internal, never maintained by a user. Technical fields to manage the link between BOM header and items	12	S
63	STAS	DVDAT	DVDAT	Scheduled on	STAS table is purely internal, never maintained by a user. Technical fields to manage the link between BOM header and items	8	S
64	STAS	DVNAM	DVNAM	Date shifted by	STAS table is purely internal, never maintained by a user. Technical fields to manage the link between BOM header and items	8	S
65	STAS	AEHLP	CC_AEHLP	Helper Field	STAS table is purely internal, never maintained by a user. Technical fields to manage the link between BOM header and items	2	S
66	STAS	STVKN	STVKN	Item node	STAS table is purely internal, never maintained by a user. Technical fields to manage the link between BOM header and items	8	S
67	STAS	IDPOS	CS_IDPOS	Item group	STAS table is purely internal, never maintained by a user. Technical fields to manage the link between BOM header and items	20	S
68	STAS	IDVAR	CS_IDVAR	Comp. Variant	STAS table is purely internal, never maintained by a user. Technical fields to manage the link between BOM header and items	5	S
69	STAS	LPSRT	CS_LPSRT	Sort key within a lo	STAS table is purely internal, never maintained by a user. Technical fields to manage the link between BOM header and items	4	S
70	STAS	BOM_VERSN	BOM_VERSION	BOM Version	STAS table is purely internal, never maintained by a user. Technical fields to manage the link between BOM header and items	4	S
71	STPO	STLTY	STLTY	BOM category	Identifier for Material/Equipment/WBS/Functional Location, Document BOM etc. Only Material BOMs are relevant here: "M"	1	S
72	STPO	STLNR	STNUM	BOM	Internal BOM number assigned by the system	8	S
73	STPO	STLKN	STLKN	Item node	Internal counter to identify uniquely the BOM item as a node in the system	8	S
74	STPO	STPOZ	CIM_COUNT	Counter	Internal counter to identify uniquely the BOM item in the system	8	S
75	STPO	DATUV	DATUV	Valid From	Start validity Date, it is by default the day one selected in the main screen at creation/change. By default it is the day of the creation/change, unless differently specified	8	R
76	STPO	TECHV	TECHV	Tech st from	Technical Start validity date, not used	12	NU
77	STPO	AENNR	AENNR	Change Number	Number of the object used to maintain this BOM together with other technical objects in a single engineering change. Not used in Syensqo	12	NU
78	STPO	LKENZ	LKENZ	Deletion Ind.	Indicator of deletion performed via Change Number. Not used	1	NU
79	STPO	VGKNT	VGKNT	Previous node	Identifier of the node of the item substituted by this one in a previous change of the BOM.	8	S
80	STPO	VGPZL	VGPZL	Prev item count	Identifier of the node of the item substituted by this one in a previous change of the BOM.	8	S
81	STPO	ANDAT	ANDAT	Created On	Creation date	8	S
82	STPO	ANNAM	ANNAM	Created by	User who created the item	12	S
83	STPO	AEDAT	AEDAT	Changed On	Date of the last change	8	S
84	STPO	AENAM	AENAM	Changed By	User who performed the last change	12	S
85	STPO	IDNRK	IDNRK	Component	Material code of the component used in production / subcontracting to build the target material. As per Business rule, here we will have an item for each material physically used in production line to build the product, including primary packing, monomers where they are missing, carton boxes, separator, etc. This field is required for material items, but it is not required in case of text items or document items	18	C
86	STPO	PSWRK	PSWRK	Issuing Plant	Plant from which the material is taken, in case it is different from the main plant of the BOM. Not used.	4	NU
87	STPO	POSTP	POSTP	Item Category	L = Material item T = Text Item D = Document	1	R
88	STPO	POSNR	POSNR	Item	4 digit number used to sequence the items, normally proposed by the system with a progression by 10, can be manually edited	4	R
89	STPO	SORTF	SORTP	Sort String	Free string that can be used to sort the items in printouts and specific applications	10	C
90	STPO	MEINS	KMPME	Component UoM	UoM for the Component Qty	3	R
91	STPO	MENGE	KMPMG	Quantity	Quantity required of this component to build the Header Qty of the Target material of the BOM	13	R
92	STPO	FMENG	FMNGE	Fixed Quantity	Indicator: the qty is fixed, not dependent from the qty we produce	1	C
93	STPO	AUSCH	KAUSF	Component Scrap	Scrap % for this specific component in the production/subcontracting process	5	C
94	STPO	AVOAU	AVOAU	Operation Scrap	Scrap calculated for this component in case the Net Indicator is set, instead of the Assemble Scrap from Material master	5	C
95	STPO	NETAU	NETAU	Net Indicator	Used to define that the planned scrap is calculated using the previous field instead of the Assembly Scrap from Material master	1	C
96	STPO	SCHGT	SCHGT	Bulk material	Bulk materials are directly available in the work center and the dependent requirements are purely created for information, not relevant for planning	1	C
97	STPO	BEIKZ	BEIKZ	Mat. Prov. Ind.	Material Provided by the Vendor / the Customer	1	C
98	STPO	ERSKZ	ERSKZ	Spare Part ID	Not relevant for Material BOM	1	NU
99	STPO	RVREL	RVREL	Sales	Item relevant for Sales: in case we would want BOM explosion in the Sales Order. Not used in Sy-Way	1	NU
100	STPO	SANFE	SANFE	Production	Item relevant for Production. It is always "X" for Material BOM	1	R
101	STPO	SANIN	SANIN	Plant maint.	Item relevant for Maintenance. not used in Material BOM	1	NU
102	STPO	SANKA	CS_SANKA	CostingRelevncy	Item is relevant for costing. Always "X" = 100% relevant	1	R
103	STPO	SANKO	SANKO	Engineering	Item relevant for Engineering BOM. Not used	1	NU
104	STPO	SANVS	SANVS	HL confign	Relevant for shipping area, not used	1	NU
105	STPO	STKKZ	STKKZ	PM assembly	Not relevant for Material BOM	1	NU
106	STPO	REKRI	REKRI	Recursive	Automatic indicator set by the system if this item makes the BOM recursive	1	S
107	STPO	REKRS	REKRS	Rec. allowed	Indicator required if this item makes the BOM recursive. Used for Rework or for actual recursive BOMs (even multi-level)	1	C
108	STPO	CADPO	CADPO	CAD Indicator	Filled if BOM is created by a CAD system	1	NU
109	STPO	NFMAT	CS_NFMAT	Follow-Up Matl	NOT IN USE	18	NU
110	STPO	NLFZT	NLFZT	Lead-tm offset	Offset applied to Lead Time for this material. It is used only if the materials are not properly allocated to operations, to allow a more precise date of requirement for long running productions. Not used in Sy-Way	3	NU
111	STPO	VERTI	SA_VERTI	Distribution	Key to distribute the qty across the timeline of the production that uses the material. not used	4	NU
112	STPO	ALPOS	ALPOS	Alternat. item	Indicator that this item is alternative with another one, both for planning and execution purposes	1	C
113	STPO	EWAHR	EWAHR	Usage Prob.	% of probability to use this item, in case of alternative items, for planning purposes	2	C
114	STPO	EKGRP	EKGRP	Purch. Group	Identifier of the buyer responsible to procure this material for this specific item, can overwrite the one from Material Master. Not used in Sy-Way	2	NU
115	STPO	LIFZT	LIFZT	Del time (days)	Delivery time in days, to be used in case a Purchase Requisition is triggered directly by the Process order Release (directly procured materials)	2	C
116	STPO	LIFNR	LIFNR	Supplier	Supplier, to be used in case a Purchase Requisition is triggered directly by the Process order Release (directly procured materials)	10	C
117	STPO	PREIS	CRPREI	Price	Purchasing price, to be used in case a Purchase Requisition is triggered directly by the Process order Release (directly procured materials)	11	C
118	STPO	PEINH	PEINH	Price unit	Purchasing price unit, to be used in case a Purchase Requisition is triggered directly by the Process order Release (directly procured materials)	5	C
119	STPO	WAERS	WAERS	Currency	Purchasing price currency, to be used in case a Purchase Requisition is triggered directly by the Process order Release (directly procured materials)	5	C
120	STPO	SAKTO	SAKTO	Cost element	P&L Account, to be used in case a Purchase Requisition is triggered directly by the Process order Release (directly procured materials)	10	C
121	STPO	ROANZ	ROANZ	Number Required	For Variable Size Items only, not used	13	NU
122	STPO	ROMS1	ROMS1	Size 1	For Variable Size Items only, not used	13	NU
123	STPO	ROMS2	ROMS2	Size 2	For Variable Size Items only, not used	13	NU
124	STPO	ROMS3	ROMS3	Size 3	For Variable Size Items only, not used	13	NU
125	STPO	ROMEI	ROMEI	Size unit	For Variable Size Items only, not used	3	NU
126	STPO	ROMEN	ROMEN	VSI Quantity	For Variable Size Items only, not used	13	NU
127	STPO	RFORM	RFORM	VSI Formula	For Variable Size Items only, not used	2	NU
128	STPO	UPSKZ	UPSKZ	Sub-item ID	Automatic indicator in case this item has sub-items	1	S
129	STPO	VALKZ	VALKZ	Alt ID	Automatic indicator, this item has more that one alternative	1	S
130	STPO	LTXSP	LTXSP_CP	Long Text Lang	Language of the long texts	1	C
131	STPO	POTX1	POTX1	Item Text	Long text	40	C
132	STPO	POTX2	POTX2	Item Text	Long text	40	C
133	STPO	OBJTY	OBJTY	Object Type	Internal, always "1"	1	S
134	STPO	MATKL	MATKL	Material Group	Not used	9	NU
135	STPO	WEBAZ	WEBAZ	GR proc. time	Specific GR time for this item in case of direct procurement in production	3	NU
136	STPO	DOKAR	DOKAR	Document Type	Doc. Type in case of Document Item	3	C
137	STPO	DOKNR	DOKNR	Document	Document number of DMS	25	C
138	STPO	DOKVR	DOKVR	Doc. Version	Document version of DMS	2	C
139	STPO	DOKTL	DOKTL_D	Document Part	Doc part of DMS	3	C
140	STPO	CSSTR	CSSTR	Mat. purity	Not used	5	NU
141	STPO	CLASS	KLASSE_D	Class	Class number for classification of this BOM item	3	NU
142	STPO	KLART	KLASSENART	Class Type	class type for classification	1	NU
143	STPO	POTPR	POTPR	Res. item cat.	Resulting Item Category in case it is different from the main one due to specific object type	1	NU
144	STPO	AWAKZ	AWAKZ	Sel. ind.	only for configurable BOM, not used	1	NU
145	STPO	INSKZ	INSKZ	Instance	only for configurable BOM, not used	1	NU
146	STPO	VCEKZ	VCEKZ	N.Dis.CE	only for configurable BOM, not used	1	NU
147	STPO	VSTKZ	VSTKZ	N.Dis.ST	only for configurable BOM, not used	1	NU
148	STPO	VACKZ	VACKZ	N.Dis.AC	only for configurable BOM, not used	1	NU
149	STPO	EKORG	EKORG	Purchasing Org.	only for configurable BOM, not used	4	NU
150	STPO	CLOBK	CLOBK	Reqd Component	only for configurable BOM, not used	1	NU
151	STPO	CLMUL	CLMULT	Multiple Sel.	only for configurable BOM, not used	1	NU
152	STPO	CLALT	CLALT	Altern. display	only for configurable BOM, not used	1	NU
153	STPO	CVIEW	ABTEILUNG	Org.area	only for configurable BOM, not used	10	NU
154	STPO	KNOBJ	KNOBJ	Assgmt no.	only for configurable BOM, not used	18	NU
155	STPO	LGORT	CSLGO	StorageLocation	Issue storage Location for Production, used to overwrite the one from material master in case it is different for this specific BOM	4	C
156	STPO	KZKUP	KZKUP	Co-product	Indicator that this item is a Co-product. To be used in case of negative qty and if we want to manage costing and / or planning for this item likewise a target material of the BOM	1	C
157	STPO	INTRM	INTRM	Intra Material	String to identify an intra-material, not stock managed, that temporarly exists during the process. Not used.	18	NU
158	STPO	TPEKZ	TPEKZ	Restr.	only for configurable BOM, not used	1	NU
159	STPO	STVKN	STVKN	Item node	INernal node set by the system.	8	S
160	STPO	DVDAT	DVDAT	Scheduled on	Date of the last date shift (change in validity dates)	8	S
161	STPO	DVNAM	DVNAM	Date shifted by	User who made the last date shift	12	S
162	STPO	DSPST	CS_DSPST	Explosion type	This is used to control the explosion of an item when determining dependent requirements. E.g. Phantom, Direct Production, Direct Procurement, etc.	2	S
163	STPO	ALPST	CS_ALPST	Strategy	Strategy to be used to select items in case of alternative items: - accordingly with % probability of usage - 100% withdrawal if available	1	C
164	STPO	ALPRF	CS_ALPRF	Priority	Ranking order for alternative items	2	C
165	STPO	ALPGR	CS_ALPGR	AltItemGroup	Group of alternative items this item belongs to	2	C
166	STPO	KZNFP	CS_KZNFP	Follow-Up Item	This item is a follow-up, it is used instead of the original item if the stock of the discontinued material is not available	1	C
167	STPO	NFGRP	CS_NFGRP	Follow-up group	Group of items identified together for the discontinuation functionality. Follow up group of the item that is to be used and discontinuation group of the item that is expiring must have the same value	2	C
168	STPO	NFEAG	CS_NFEAG	Discont. group	Group of items identified together for the discontinuation functionality. Follow up group of the item that is to be used and discontinuation group of the item that is expiring must have the same value	2	C
169	STPO	KNDVB	CS_KNDVB	Manual change	Used for Sales Order BOM only. Not used	1	NU
170	STPO	KNDBZ	CS_KNDBZ	Obj.dep.change	Used for Sales Order BOM only. Not used	1	NU
171	STPO	KSTTY	CS_KSTTY	BOM category	Used for Sales Order BOM only. Not used	1	NU
172	STPO	KSTNR	CS_KSTNR	BOM	Used for Sales Order BOM only. Not used	8	NU
173	STPO	KSTKN	CS_KSTKN	Item node	Used for Sales Order BOM only. Not used	8	NU
174	STPO	KSTPZ	CS_KSTPZ	Counter	Used for Sales Order BOM only. Not used	8	NU
175	STPO	CLSZU	CS_CLSZU	Classification	Used for Sales Order BOM only. Not used	8	NU
176	STPO	KZCLB	CS_KZCLB	as sel. cond.	Used for Sales Order BOM only. Not used	1	NU
177	STPO	AEHLP	CC_AEHLP	Helper Field	Hierarchy indicator for Date shift	2	NU
178	STPO	PRVBE	PRVBE	Supply Area	Production Supply Area where this item is used in production, relevant for EWM.	10	C
179	STPO	NLFZV	CS_NLFZV	Oper. LT offset	Relevant only for Plant Maintenance and project system, not used	3	NU
180	STPO	NLFMV	CS_NLFMV	Oper. LTO unit	Relevant only for Plant Maintenance and project system, not used	3	NU
181	STPO	IDPOS	CS_IDPOS	Item group	Used only in case of ECN	20	NU
182	STPO	IDHIS	CS_IDHIS	History counter	Used only in case of ECN	5	NU
183	STPO	IDVAR	CS_IDVAR	Comp. Variant	Used only in case of ECN	5	NU
184	STPO	ALEKZ	CS_ALEKZ	ALE indicator	Indicator that this BOM item has been created / changed via distribution from another system	1	S
185	STPO	ITMID	CS_ITMID	Item ID	Item Identifier	8	NU
186	STPO	GUID	CS_CHAR22	Not used	Not used	22	S
187	STPO	ITSOB	CS_SOBSL	SpecProcurement	Special procurement key for this item (e.g. procurement from another plant, to direct production, etc.)	2	C
188	STPO	RFPNT	CS_RFPNT	Reference point	Used only for network activities. Not relevant for Sy-Way	20	NU
189	STPO	GUIDX	CS_GUID	Guid	Internal ID change item status	16	S
190	STPO	SGT_CMKZ		Seg. maintained	Automatically maintained value by the system if segmentation is relevant		S
191	STPO	SGT_CATV		Seg. Value	Requirements Segment of Stock Segment to be used for this item		NU
192	STPO	VALID_TO		to	Valid to date for this item. It is defined by the system when an item is substituted, based on the validity dates on the main screen	8	S
193	STPO	VALID_TO_RKEY		to	Not used		NU
194	STPO	ECN_TO		Change No. To	Only in case of ECN, Change number To		NU
195	STPO	ECN_TO_RKEY		Change No. To	Only in case of ECN, Change number To		NU
196	STPO	ABLAD		Unloading Point	Free string to specify the unloading point for this material		NU
197	STPO	WEMPF		Recipient	Free string to specify the recipient for this material in this BOM		NU
198	STPO	STVKN_VERSN		Item node	Internal counter to identify uniquely the BOM item as a node in the system		S
199	STPO	LASTCHANGEDATET		Time Stamp	Time Stamp	8	S
200	STPO	PRELIMINARY_MAT		Description	Preliminary description for the material		NU
201	STPO	SFWIND		Software component	Indicator: this item is a SW component		NU
202	STPO	DUMMY_STPO_INCL		Ext. Include	Not used (maintenance)		NU
203	STPO	CUFACTOR		NoCUInstances	Number of compatible units. Not used		NU
204	STPO	/SAPMP/MET_LRCH		Length Calc. Method	Only for Variable Length calculation		NU
205	STPO	/SAPMP/MAX_FERT		Max. Prod. Length	Only for Variable Length calculation		NU
206	STPO	/SAPMP/FIX_AS_J		Fix.Scrap Any Length	Only for Variable Length calculation		NU
207	STPO	/SAPMP/FIX_AS_E		FixedScrap FirstLgth	Only for Variable Length calculation		NU
208	STPO	/SAPMP/FIX_AS_L		Fix.Scrap Last Lngth	Only for Variable Length calculation		NU
209	STPO	/SAPMP/ABL_ZAHL		No. R-I Lengths	Only for Variable Length calculation		NU
210	STPO	/SAPMP/RUND_FAK		Rounding Value	Only for Variable Length calculation		NU
211	STPO	FSH_VMKZ		Dev.vals maint.	Only for Variable Length calculation		NU
212	STPO	FSH_PGQR		Qty Distr. prof.	Qty distribution profile, not used		NU
213	STPO	FSH_PGQRRF		Qty Distr.Prof.Ref.	Qty distribution profile, not used		NU
214	STPO	FSH_CRITICAL_CO		Critical Component	Critical component to be considered in feasibilty analysis for Order Allocation.		NU
215	STPO	FSH_CRITICAL_LE		Critical Level	Level of criticality for critical components in Order allocation		NU
216	STPO	FUNCID		Function ID	Only for Maintenance, not used		NU
217	STPO	SERVICEDURATION		Service Duration	Only for Maintenance, not used		NU
218	STPO	SERVICEDURATION		Serv. Dur. Unit	Only for Maintenance, not used		NU
219	STPO	PRODUCTTYPE		Product Type Group	to identify Services in case of usage of Service Entry Sheet, Not relevant for material BOMs		NU

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
1040-001	C1	Invalid, Inactive or no material component created for the plant/material combination	Bill of Material as per Relevancy Criteria within a plant assigned with a Component which does not belong below: 1. Material Master (S2P) as per Relevancy Criteria within the same plant as BOM	Material	PF2/WP2
1001-002	C1	Invalid or Inactive Document Info Record linked to Bill of Material	Bill lof Material as per Relevancy Criteria assigned with a Document Info Record which does not belong below: 1. Document Info Record as per Relevancy Criteria	Document Info Record	PF2/WP2
1001-003	C1	BOM Base Unit of Measure Missing / incorrect.	BOM Base Unit of Measure as per Relevancy Criteria with no UoM Assigned or Invalid UoM (T006)	Unit of Measure	PF2/WP2
1001-004	C1	BOM Component UOM Missing / incorrect.	Bill lof Material Component as per Relevancy Criteria with no UoM Assigned or Invalid UoM (T006)	Unit of Measure	PF2/WP2
1001-005	C2	BOM Component Quantity is Zero or Negative.	Bill lof Material Component as per Relevancy Criteria with Value <= 0.	Component Quantity	PF2/WP2
1001-006	C1	Functional Location or Equipment BOM not used for Plant Maintenance	Bill of Material with below BOM Equipment (E) and Functional Location (T) BOM Categories and with no Deletion Indicator but are not used in Plant Maintenance*. * BOM Usage (4) - Plant Maintenance in MAST, EQST, TPST	BOM Category, Usage	PF2/WP2
1001-007	C1	BOM with Plant Maintenance Usage but not used by Materials, Equipment or Functional Location	BOM as per Relevancy Criteria however not assigned to below: 1. Materials as per Relevancy Criteria 2. Equipment as per Relevancy Criteria 3. Functional Location as per Relevancy Criteria	BOM Category, Usage	PF2/WP2
1001-008	C1	BOM (PM Assemblies) without BOM Components.	Bill lof Material Component as per Relevancy Criteria with 0 Components assigned.	BOM Component	PF2/WP2
1001-009	C1	BOM Plant incorrect.	BOM as per Relevancy Criteria with Invalid Plants (T001W)	Plant	PF2/WP2
1001-010	C1	BOM Language Key incorrect.	BOM as per Relevancy Criteria with Invalid Language Key (T001)	Language Key	PF2/WP2
1001-011	C1	BOM Laboratory/office for material incorrect.	BOM as per Relevancy Criteria with Invalid Laboratory/office for material (T024L)	Laboratory/office for material	PF2/WP2
1001-012	C1	BOM Bill of Material Status incorrect.	BOM as per Relevancy Criteria with Invalid XXXX (T415S)	Bill of Material Status	PF2/WP2

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
Conversion Accuracy	SyWay Data Team to verify that all fields below meet pass the checks: Mandatory Fields Field and Value Mapping Correctness Null Checks 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

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

Completeness

Task	Action
Verify Record Count	Business Data Owner/s to verify that the total number of relevant records from the the DCT is equal to the total number of records in the Preload and Load Sheets.

Accuracy

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

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
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	Load 3 records for < > to validate if data is loaded successfully without errors	SyWay Data Team
4	Proceed with full load if steps 2 and 3 are validated	SyWay Data Team
5	Validate few records loaded by accessing standard transactions from S/4HNA eg. CRC3	SyWay Data Team
6	Generate post load report if step 5 is validated	SyWay Data Team

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
Verify Count	SyWay S2P Data Team to verify the record count created in target S/4 HANA by accessing post load reports in dspMigrate or standard reports from S/4 HANA.

Accuracy

Task	Action
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.).

Business

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

Completeness

Task	Action
Verify Count	Download Post Load Reports from dspMigrate 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 Resource 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.
• 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