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 multiple alternative BOMs exist
5. BOM Component (STPO-IDNRK) for relevant Material / Assembly 
6. BOM Component (STPO-IDNRK) for non-Assembly is extended to the relevant plant based on the BOM Header Plant (TPST-WERKS/EQST-WERKS/MAST-WERKS)
7. BOM Component (STPO-IDNRK) for non-Assembly, only Material Type (MARA-MTART) with the following to-be values based on Material Type Mapping:

• ZIND
• NLAG
• UNBW

The data from legacy system excludes:

1. BOM with BOM Item where there is no relevant Material / Assembly in the Component field (STPO-IDNRK)
2. BOM where the BOM Header (MAST-MATNR) is Assembly and all the BOM items (STPO-IDNRK) are Assembly
3. BOM Header with deletion indicator checked (STKO-LKENZ="X")
4. BOM Header with deletion flag checked (STKO-LOEKZ="X")
5. BOM Item with deletion indicator checked (STPO-LKENZ="X")
6. 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.

Scenarios for Migration for Legacy (PF2,WP2)

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

The technical design of the target for this conversion approach.

1. BOM Header

2. BOM Item

Data Cleansing

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

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

Selection Screen

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.

Delta Data Management: Initial collection will be done via the report and one-time load to the DCT will be performed. Any delta after the initial collection within the DCT will require business to take due diligence to ensure any subsequent delta cleansing is verified and aligned within the DCT.

Note: All rules specified below should be documented as a tooltip in the DC Page.

Format:

• Line 1: Mandatory / Conditional
• Line 2: Remaining text

1. BOM Header Data Construction Rules

2. BOM Item Data Construction Rules

Note: List of DCTs is maintained here: Conversion Specs Register (DCT & Cleansing Report)

Extraction Dependencies

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

Transformation Rules

** TAKE NOTE:

1. UOM difference
2. Component after dedupe

Transformation Mapping

List of Transformation Mappings with additional details is maintained here: Transformation Mappings

Transformation Dependencies

Pre-Load Validation

Project Team

Completeness

Accuracy

Business

Completeness

Accuracy

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

Load Phase and Dependencies

Pre-Cutover

Configuration

Conversion Objects

Error Handling

Post-Load Validation

Project Team

Completeness

Accuracy

Business

Completeness

Accuracy

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.

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

• Data entries in DCT are target-ready data unless a specific transformation rule is stated for that field in the transformation rules.

See also

Change log

Workflow history