Bills of material and production versions¶

A bill of material, or BOM, states what is consumed to make a material. A production version states which process alternative can make it at a given location, resource, or routing.

Review both datasets together: a component structure without a production alternative does not generate supply, and a production version without consistent components does not represent the actual process.

Path in the platform¶

Data > Data Operations > Master Data > Materials > BOM and Versions > BOM and production versions

Grain and key¶

BOM: produced material, component, and version.
Production version: produced material, location, alternative, and validity.
Version component: production alternative and component.

Required BOM fields¶

Logical field	Meaning
`bomId`	Structure identifier
`parentMaterialId`	Material being produced
`componentMaterialId`	Material being consumed
`quantityPer`	Component quantity per produced unit
`uomId`	Unit of the component quantity

Optional BOM fields¶

Logical field	Meaning	Default Value When Not Provided
`versionId`	Structure revision or alternative	No version
`validFrom`	Start of validity	No additional initial restriction
`validTo`	End of validity	No additional final restriction
`scrapRate`	Expected component loss	No scrap factor

Required production-version fields¶

Logical field	Meaning
`productionVersionId`	Alternative identifier
`materialId`	Material being produced
`locationId`	Location where the alternative exists
`routingId`	Production routing or process

Dependencies¶

Materials for finished goods, intermediates, and components.
Locations for the production point.
Units of Measure and conversions.
Production resources and routings.
Calendar and alternative validity.

Used by¶

Supply Planning data model;
Supply Network Planning and Design;
component-requirement calculation and material explosion;
capacity planning and Supply Plan generation;
S&OE and Line Sequencing;
Supply Network Explorer and production-path validation;
production cost and Cost-to-Serve.

Validations¶

when the process uses BOM versioning, every versioned row provides versionId;
a missing scrapRate is not interpreted as zero loss unless the process rule explicitly defines that behavior;
parent and component do not form an unintended cycle;
quantity per unit is positive;
all units can be converted;
BOM, version, routing, and resource validity windows overlap;
the alternative has a location and resource able to make the material;
substitute or alternative components have explicit priority.