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.

BOMS are actually used for all the Production process. All materials related with manufacturing activities have a Product Structure created by BOM/Master Recipe & Production Version. BOM takes a relevant part of the structure, where the components are defined to produce the Semi Finished and Finished products. The aim prior to migrate is to have a exhaustive data cleansing for BOM, as we know that some plants are having issues with them.

All valid BOMS will be migrated to the S4 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 from legacy system includes:

1. BOMS > 3 years
2. BOMS w/o Deletion flags
3. BOMS with active Materials in active Plants
4. BOMS that will be migrated to the To-Be Plant Mapping (Take in consideration the To-Be definition of Plants)

The data from legacy system excludes

1. BOMS inactive in the last 3 years
2. BOMS marked for deletion
3. BOMS with Inactive Materials in inactive Plants
4. BOMS belonging to Deleted plants (New plant Definition according with the To-Be Plant mapping)

List of source systems and approximate number of records

Source	Scope	Source Approx No. of Records	Target System	Target Approx No. of Records
F2, 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 activties 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 asisgned 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 asisgned 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 Materila 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	techincal start	12	NU
20	STKO	AENNR	AENNR	Change Number	Number of the object used to maintain this BOM together with other techical objects in a single engineerign 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 asisgned 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 asisgned 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 organsational 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 Vlaid 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 Canghe 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. Techincal 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. Techincal 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. Techincal 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. Techincal 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. Techincal 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. Techincal 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. Techincal 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. Techincal 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. Techincal 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. Techincal 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. Techincal 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. Techincal 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. Techincal 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. Techincal 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. Techincal 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. Techincal 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. Techincal 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. Techincal 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. Techincal 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. Techincal 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. Techincal fields to manage the link between BOM header and items	4	S

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