Status
Owner	PUN-ext, Eddy
Stakeholders	ERGUIZA-ext, Pinky Love TEE-ext, Paul  JOSHI-ext, Aditya VILARES, ines LEIGHTON-ext, DeanSARUKAN-ext, Ayse  STEFANESCU-ext, Aurelia  MOUSSA-ext, Eva HUSSAN-ext, Nishin

Purpose

The purpose of this document is to define the conversion approach to create Bill of Material in S/4 HANA.

In Syensqo’s SAP S/4HANA environment, the Bill of Materials (BOM) defines the structured list of components required to perform a specific maintenance task, build an assembly, or manufacture a product. Each BOM represents a hierarchical breakdown of items - materials, assemblies, or parts - along with their respective quantities and usage context.

In the maintenance and asset management domain, three types of BOMs are utilized:

• Functional Location BOM – Linked to a specific technical location, outlining the parts typically required for maintenance activities at that location.
• Equipment BOM – Associated with a particular equipment asset, detailing spare parts and components relevant to its structure or maintenance.
• Material BOM – Tied to a material number, commonly used in manufacturing or for assemblies that are consumed or produced.

For rotable materials—such as repairable or reusable components—always refer to the corresponding Equipment or Functional Location Bill of Materials (BOM). Only components that are specific to that individual Equipment or Functional Location and not commonly used across other similar assets, should be included. This ensures that the BOM accurately reflects asset-specific configurations and supports targeted maintenance planning.

Conversion Scope

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

A Bill of Materials (BOM) is a structured list of components, spare parts, or assemblies required for maintenance activities on technical objects like equipment or functional locations. It helps streamline maintenance planning, spare parts procurement, and work order execution.

The data from legacy system includes:

1. BOM Category (STKO-STLTY):
   1. E-Equipment BOM (EQST-EQUNR) for relevant Equipment
   2. M-Material BOM  (MAST-MATNR) for relevant Assembly
   3. T-Functional Location BOM (TPST-TPLNR) for relevant Functional Location
2. BOM Usage (EQST-STLAN/MAST-STLAN/TPST-STLAN) = Plant Maintenance
3. BOM Item Category (STPO-POSTP) = I, L, N or T
4. Material BOM with the latest Alternative BOM (MAST-STLAL), if applicable

The data from legacy system excludes:

1. BOM where the BOM Header (MAST-MATNR) is Assembly and all the BOM items (STPO-IDNRK) are Assembly
2. BOM Header with deletion indicator checked (STKO-LKENZ="X")
3. BOM Header with delecton flag checked (STKO-LOEKZ="X")
4. BOM Item with deletion indicator checked (STPO-LKENZ="X")
5. Previous Alternative BOM (MAST-STLAL) for Material BOM with more than one Alternative BOM

For further explanation, a Material BOM for relevant Assembly excludes BOM Assembly Header (MAST-MATNR) that are not assigned to Functional Location (IFLOT-SUBMT), Equipment (EQUZ=SUBMT) or Task List (PLKO-ISTRU).

The following are not in scope for BOM Conversion:

1. Document Info Record
2. Long Text

List of Tables to extract for this object is maintained here: Extract Table Register.

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	Relevant BOM will be extracted from PF2 and WP2	10,000	S/4 HANA	10,000
DCT	BOM for plants which do not have data existing from PF2 and PF2 Additional BOM originating from PF2 and WP2 (if required).	10,000	S/4HANA	10,000

Additional Information

Multi-language Requirement

Direct update of short text ,  log text in desired language i.e User log on language.

Document Management

Not Applicable

Legal Requirement

Not Applicable

Special Requirements

Not Applicable

Target Design

With Functional input, document the technical design of the target fields that are in the scope of this document.

The technical design of the target for this conversion approach.

Table	Field	Data Element	Field Description	Data Type	Length	Requirement
MARA	MATNR	MATNR	Material Number	CHAR	18	Mandatory

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
1001-001	C1	Invalid, Inactive or no Component linked to Bill of Material	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	BOM Header, Plant, BOM Item Number, Material	PF2/WP2
1001-002	C2	BOM Component Quantity is Zero or Negative.	Bill lof Material Component as per Relevancy Criteria with Value <= 0.	BOM Header, Plant, BOM Item Number, Material, Component Quantity	PF2/WP2
1001-003	C3	Functional Location BOM assigned to non-relevant Functional Location	Bill of Material for relevant Plant with BOM Category (T-Functional Location) and with no Deletion Indicator but are assigned to non relevant Functional Location	Functional Location, Plant, BOM Category, Usage	PF2/WP2
1001-004	C3	Equipment BOM assigned to non-relevant Equipment	Bill of Material for relevant Plant with BOM Category (E-Equipment) and with no Deletion Indicator but are assigned to non relevant Equipment	Equipment, Plant, BOM Category, Usage	PF2/WP2
1001-005	C1	Functional Location BOM with blank Plant	Bill of Material with BOM Category (T-Functional Location) assigned to relevant Functional Location with blank Plant	Functional Location, Plant, BOM Category, Usage	PF2/WP2
1001-006	C1	Equipment BOM with blank Plant	Bill of Material with BOM Category (E-Equipment) assigned to relevant Equipment with blank Plant	Equipment, Plant, BOM Category, Usage	PF2/WP2
1001-007	C3	Material BOM with previous Alternative BOM not migrated	Bill of Material with BOM Category (M-Material) with more than 1 Alternative BOM, report all the previous Alternative BOM except for the latest	Material, Plant, BOM Category, Usage, Alternative BOM	PF2,WP2

Conversion Process

The high-level process is represented by the diagrams below.

The following represents the high-level process for Source System Extraction:

The following represents the high-level process for DCT:

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

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

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
1	Only BOM linked to relevant Functional Location should be extracted.	Data Team
2	Only BOM linked to relevant Equipment should be extracted.	Data Team
3	Only BOM linked to relevant Assembly should be extracted.	Data Team

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
1	Ensure all mapping tables are up to date.	Syniti
2	In dspMigrate, select the wave –R3 S4/HANA – Plant Maintenance	Syniti
3	Go to Process Area Launch and Process the Object – BOM	Syniti
4	Review and Validate Error and Preload Reports	Syniti
5	Execute the transformation to prepare the target tables	Syniti
6	Validate data from pre-load and invalid reports by region	Business/Data owner
7	Generate export(load) file (If load tool is not dspIntergrate)	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

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

The following pre-load validations will be performed by the 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:

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

Pre-Cutover

Configuration

List the Configurations required before loading can commence

Item #	Configuration Item
1	T001W-Plants/Branches
2	T006-Units of Measurement
3	T415S-Bill of Material Status

Conversion Objects

Object #	Preceding Object Conversion Approach
1003	Functional Location
1002	Equipment
2010	Material - General Plant Data / SLoc Data
1010	Construction Type

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	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.
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 dspMigrate post load reports or standard reports from S/4 HANA.

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 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.
• Data Object is in scope based on data design and any exception requested by business.

• Data cleansing has met the required percentage threshold for the specified mock cycle and all preparation activities have been completed.

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