Purpose

The purpose of this document is to define the conversion approach to create 1038 Material BOM (Usage 1) and Sales & Distribution BOM (Usage 5) 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.

This Conversion Specification does not include the WPX system (CUI Objects).

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 the 1038 Master Data Design Standard.

The data from legacy system includes:

• The migration of Bills of Material (BOMs) will be governed by the Material Relevancy Criteria, which serve as the foundational rule for identifying and including BOMs that are valid, active, and business-relevant for conversion to S/4HANA.
• Only BOMs linked to relevant materials are migrated initially. If these BOMs contain additional component materials, those materials and their corresponding BOMs are also brought into the migration scope. This process continues iteratively until all related BOMs and components are included, ensuring the entire BOM structure and its dependencies are fully migrated for completeness and data integrity in S/4HANA.
• 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 and Usage 5 - Sales & Distribution) 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

The data from legacy system excludes:

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

• BOMs marked for deletion in ECC.

• BOMs belonging to plants that are deleted or out of scope, based on To-Be Plant Mapping in Enterprise Structure Catalog worksheet "30. Plants".

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

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

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

Relevancy rule

1. Material/Plant with history and active production usage – Materials must be defined at global (MARA) and plant level (MARC) with valid status and assignment to active plants in scope.

2. BOMs linked to active materials – Only BOMs associated with materials that have valid usage (Usage = 1 “Production” and Usage = 5 "Sales & Distribution") and are actively used in production within the last four (4) years will be considered.

3. Production Versions referencing BOMs – Production Versions must exist and be valid, linking BOMs with corresponding Routings/Master Recipes at the plant level to ensure continuity of manufacturing execution.

4. Component materials – All components within the BOM must be valid, active materials in the Material Master and not marked for deletion.

5. Plant-specific validation – BOMs will be checked against active plant mappings (per To-Be Plant definition) to ensure only relevant BOMs are migrated.

Material/Plant Active with four (4) years production usage history ➡ defines Active BOMs (Usage = 1 “Production” and Usage = 5 "Sales & Distribution") by Plant ➡ validates Production Versions ➡ ensures accurate mapping of dependent Routings/Master Recipes.

Plant Merging

Plants will be harmonized based on the To-Be Plant Mapping. As some legacy plants will be merged into one target plant, BOMs will be reassigned accordingly. Plant transformation will be managed through a mapping table maintained in Syniti to ensure consistent alignment with the To-Be Plant structure.

Additional Information

Multi-language Requirement

BOM Header and component descriptions are are inherited from the Material Master and are not subject to migration or transformation.

Document Management

N/A

Legal Requirement

N/A

Special Requirements

N/A

Target Design

The technical design of the target for this conversion approach.

Data Cleansing

All data cleansing activities must be performed in the source systems (e.g., PF2, WP2) wherever possible, following the rules and criteria defined in this document. The objective is to ensure that only valid, active, and relevant master data is migrated to S/4HANA, while obsolete, redundant, or inconsistent records are excluded.

If certain data cleansing activities cannot be executed directly in the source systems due to system limitations, they may be managed externally (e.g., using Syniti Migrate, 3rd Party Vendor tools, or DCT processes). In such cases, proper documentation of the cleansing activity must be maintained and appended to this deliverable to support review, validation, and sign-off by stakeholders.

Conversion Process

The high-level process is represented by the diagram below:

The ETL (Extract, Transform, Load) process is a structured approach to data migration and management, ensuring high-quality data is seamlessly transferred across systems. Here’s a breakdown of its key components:

1. Extraction
The process begins with extracting metadata and raw data from source systems, such as Syensqo ECC system (i.e. WP2/PF2) periodically. The extracted data is then staged for transformation.

2. Transformation
Once extracted, the data undergoes cleansing, consolidation, and governance. This step ensures data integrity, consistency, and compliance with business rules. The transformation process includes:
- Data validation to remove inconsistencies.
- Standardization to align formats across datasets.
- Business rule application to refine data for operational use.

3. Loading
The transformed data is then loaded into the target S/4HANA system. 

For sites that are not on SAP-PF2 and WP2 systems, collection will be done manually in the data collection template.

The high-level process for DCT is represented by the diagram below:

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)

A Target-Ready Data Collection Template will be created for all required fields in the SAP PP - Material BOM except for fields that require transformation in accordance with the defined transformation rules. Each template will follow the structure and format required by the target S/4HANA Production Planning (P2F-MFG).

1. Header Level Field (MAST and STKO Table) 
   

   Table	Field Name	Field Description	Data Type	Length	Requirement	Rule
   MAST	MATNR	Material	CHAR	18	Required	Legacy Material to New Material Mapping
   MAST	WERKS	Plant	CHAR	4	Required	Legacy Plant to New Plant Mapping
   MAST	STLAN	Usage	CHAR	1	Required	Only values 1 (Production) and 5 allowed for migration
   MAST	STLAL	Alternative	CHAR	2	Conditional	Auto-generated or manually maintained
   STKO	BMEIN	Base UoM	CHAR	3	Conditional	Used for header-level base unit
   STKO	BMENG	Base Quantity	QUAN	13	Required	Required for BOM header
   STKO	LABOR	Lab/Office	CHAR	2	Conditional	Organizational field for maintenance responsibility
   STKO	LTXTSP	Long Text	CHAR	132	Conditional	BOM long text for documentation (Header Level)
   STKO	STLST	BOM Status	CHAR	2	Required	01 = In Creation 04 = Released (General)
   STKO	VALID_TO	Validity End	DATS	8	Required	Set default to 31.12.9999
   STKO	DATUV	Valid From	DATS	8	Required	Same as header; default = creation date unless changed

   
   
   
   
2. Item Level (Detail) Field (STPO Table)
   

   Table	Field Name	Field Description	Data Type	Length	Requirement	Rule
   MAST	MATNR	Material	CHAR	18	Required	Legacy Material to New Material Mapping
   MAST	WERKS	Plant	CHAR	4	Required	Legacy Plant to New Plant Mapping
   MAST	STLAN	Usage	CHAR	1	Required	Only values 1 (Production) and 5 allowed for migration
   MAST	STLAL	Alternative	CHAR	2	Conditional	Auto-generated or manually maintained
   STPO	IDNRK	Component	CHAR	18	Conditional	Required for material items; non-material items may use text or document
   STPO	POSTP	Item Category	CHAR	1	Required	T = Text, L = Material, D = Document
   STPO	POSNR	Item Number	NUMC	4	Required	Auto-generated by system (increments of 10)
   STPO	SORTF	Sort String	CHAR	10	Conditional	Used for printed layout sorting
   STPO	MEINS	Component UoM	UNIT	3	Required	Must match material base/unit conversion
   STPO	MENGE	Quantity	QUAN	13	Required	Required item quantity
   STPO	FMENG	Fixed Quantity	QUAN	13	Conditional	Only for fixed-consumption components
   STPO	AVOAU	Scrap %	DEC	5	Conditional	Used if scrap indicator is set
   STPO	NETAU	Net Indicator	CHAR	1	Conditional	Determines scrap handling (assembly scrap vs. component-level scrap)
   STPO	SANFE	Bulk Material	CHAR	1	Conditional	Always “X” for bulk items
   STPO	SANKA	Costing Relevancy	CHAR	1	Required	Always "X"; 100% relevant
   STPO	REKRS	Recursive Allowed	CHAR	1	Conditional	Required if BOM recursiveness is permitted
   STPO	ALPGR	Alternative Group	CHAR	2	Conditional	Required for alternative group
   STPO	ALPOS	Alternative Item	CHAR	2	Conditional	Required for alternative items
   STPO	EWAHR	Usage Probability	DEC	3	Conditional	% probability used in planning
   STPO	LIFNR	Supplier	CHAR	10	Conditional	For externally procured components
   STPO	PREIS	Price	CURR	11	Conditional	Purchasing price for directly procured items
   STPO	WAERS	Currency	CHAR	5	Conditional	Currency for procurement price
   STPO	PEINH	Price Unit	NUMC	10	Conditional	Price unit for procurement
   STPO	LTXSP	Item Long Text	CHAR	40	Conditional	Item-level long text (Component Level)
   STPO	POTX1	Text: Description (1)	CHAR	40	Conditional	Description for the item
   STPO	POTX2	Text: Description (2)	CHAR	40	Conditional	Description for the item
   STPO	LGORT	Storage Location	CHAR	4	Conditional	Optional overriding storage location
   STPO	KZKUP	Co-Product Indicator	CHAR	1	Conditional	Set to "2" for co-products
   STPO	ALPST	Alternative Strategy	CHAR	1	Conditional	Strategy for using alternative items
   STPO	ALPRF	Priority	CHAR	2	Conditional	Ranking of alternatives
   STPO	KZNFP	Follow-Up Item	CHAR	1	Conditional	Follow-up indicator for non-stock items
   STPO	NFGRP	Follow-Up Group	CHAR	2	Conditional	Group used for phase-out/discontinuation
   STPO	NFEAG	Discount Group	CHAR	2	Conditional	Discount group for procurement
   STPO	PRVBE	Supply Area	CHAR	10	Conditional	EWM/production supply area
   STPO	ITSOB	Special Procurement	CHAR	2	Conditional	e.g., external procurement, production, cross-plant
   STPO	BEIKZ	Indicator: Material Provision	CHAR	1	Conditional	Required for Material provision
   STPO	SCHGT	Indicator: Bulk Material	CHAR	1	Conditional	Required for Bulk material
   STPO	EKGRP	Purchasing Group	CHAR	4	Conditional	Identify for externally procured activity in BOM
   STPO	SAKTO	Cost Element	CHAR	10	Conditional	Used for directly procured material in process order

   
   Note:
   Please check the link attached for Layout:

Extraction Dependencies

Before data extraction can commence, several prerequisite steps and conditions must be met to ensure a smooth and accurate extraction process. These dependencies involve confirming system readiness, validating data structures, and ensuring that appropriate access rights and credentials are in place.

Each step must be clearly defined, assigned to responsible teams, and completed prior to extraction activities. Proper coordination across stakeholders is required to mitigate risks and avoid delays in the migration timeline.

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

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 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 (MDS) is up to date as of the date of documenting this conversion approach and BOM data load.

• Data cleansing has been completed to ensure only active, valid, and relevant Production BOMs are migrated. BOMs marked for deletion, inactive materials, or obsolete plants are excluded.

• Only BOM Usage 1 (Production BOMs) and BOM Usage 5 (Sales BOMs) are in scope for migration. Other usages (e.g., Engineering, or Plant-specific BOMs) are explicitly excluded unless approved as part of an exception process.

• Component materials used in Production BOMs are assumed to be migrated first and available in the target system (dependency on Material Master migration).

• Unit of Measure (UoM) mapping is harmonized between source and target systems, ensuring that BOM component quantities align with material master definitions in S/4HANA.

• Number ranges for Production BOMs are preconfigured in S/4HANA, and internal numbering will be applied during migration unless specified otherwise.

• Enrichment activities (such as resolving missing item categories, missing scrap factors, or obsolete components) are handled outside the automated migration process and require manual intervention or business sign-off.

• Not all legacy BOM fields (e.g., CAD indicators, document links, or legacy-specific flags) will be migrated to S/4HANA; only fields required for production planning, costing, and shop-floor execution are considered in scope.

See also

CNV-2005 Material Master - MRP Views

CNV-2006 Material Master PPDS View

CNV-2008 Material Master Work Scheduling View

CNV-2009 Material Master QM view

Change log

Workflow history