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:
   1. E-Equipment BOM for relevant Equipment
   2. M-Material BOM for relevant Assembly
   3. T-Functional Location BOM for relevant Functional Location
2. BOM Usage = Plant Maintenance

The data from legacy system excludes:

1. BOM where the BOM Header is Assembly and all the BOM items are Assembly

For further explanation, a Material BOM for relevant Assembly excludes BOM Assembly Header that are not assigned to Functional Location, Equipment or Task List.

Additional Information

Multi-language Requirement

BOM header description will be retrieved from PM Assembly description. Alternate language availability will depend on PM Assembly alternate language.

Document Management

Not Applicable

Legal Requirement

Not Applicable

Special Requirements

Target Design

The technical design of the target for this conversion approach.

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 . There are 2 possibilities:

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

Selection Screen

Data Collection Template (DCT)

DCT Rules

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

Transformation Mapping

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.

See also

Change log

Workflow history