SAP reference for bills of material and production versions¶

This reference translates the current public Community/Enterprise contracts. The legacy planning-* codebase is not a mapping authority; confirm final availability in the deployed edition and OpenAPI.

This page translates common SAP ECC and SAP S/4HANA concepts into the bills of material and production versions contract. The OpsFactor page remains the final reference for grain and required fields.

Bills of material¶

OpsFactor	Nearby SAP field	Common SAP tables	Note
`bomId`	`MATNR` + `STLAN` + `STLAL`	`MAST`, `STKO`	Material, BOM usage, and alternative form a reproducible identifier
`parentMaterialId`	`MATNR`	`MAST`	Material being produced
`componentMaterialId`	`IDNRK`	`STPO`	BOM component
`quantityPer`	`MENGE`, interpreted against `BMENG`	`STPO`, `STKO`	Component quantity relative to the header base quantity
`uomId`	`MEINS` or the corresponding item unit	`STPO`	Convert to a code accepted by OpsFactor
BOM item	`POSNR`	`STPO`	Can distinguish repeated components in the same structure
validity	`DATUV` and applicable change controls	`STKO`, `STPO`	Validate effective dating during extraction

An official SAP integration pattern identifies a BOM by concatenating material, BOM usage, and alternative. A natural bomId is therefore:

MAT-001-1-01

representing MATNR=MAT-001, STLAN=1, and STLAL=01. If the same combination can represent different structures by plant within the integrated scope, include WERKS, for example 1000-MAT-001-1-01, to preserve the global uniqueness required by OpsFactor.

Do not use STLNR alone as an external ID without assessing its stability and scope. It is SAP's internal BOM number, while the functional combination is easier to reproduce from source master data.

Production versions¶

OpsFactor	Nearby SAP field	Common SAP table	Note
`productionVersionId`	`MATNR` + `WERKS` + `VERID`	`MKAL`	The SAP version is identified in a material-and-plant context
`materialId`	`MATNR`	`MKAL`	Material being produced
`locationId`	`WERKS`	`MKAL`	Usually mapped to the production location
selected BOM	`STLAN` + `STLAL`	`MKAL`	Connects the version to BOM usage and alternative
`routingId`	`PLNNR` + `PLNAL`	`MKAL`	Connects the version to routing group and group counter
validity	`ADATU` and `BDATU`	`MKAL`	Start and end of alternative validity

To prevent VERID=0001 from colliding across materials or plants, build an ID such as MAT-001-1000-0001. Preserve leading zeroes.

Nearby SAP transactions¶

CS01, CS02, and CS03: create, change, and display a material BOM;
C223: manage production versions;
CS11, CS12, and CS13: BOM explosion and reports that can validate the extracted structure.

In SAP S/4HANA, Fiori apps, CDS views, and APIs may replace direct extraction from these tables. The names above identify the functional analogy; they do not mandate an integration mechanism.

SAP references¶

Return to bills of material and production versions or the SAP index.