One governed structure per product per plant: components, quantities, effectivity, alternates and phantoms, consistent with the golden materials.
Today engineering's BOM, the ERP BOM and the plant's spreadsheet disagree on quantities and effectivity dates, and a costing run finds out last.
With Lima the bills of materials are read where they live, matched on parent item + plant + usage + alternative and component item + position, assembled field by field and published as one golden record per real bill of materials, with every source key underneath. The explosion to every level, the where-used tree, the production orders that consumed the structure, and the change records behind each effectivity date are one click away, because the transactions sit in the same bed.
Survivorship is per field; the winning source below is the usual one, and a steward's verified edit outranks it.
Components resolve to golden materials first, so every component points at the golden item.
Pairs above the merge line merge; pairs between the lines go to the steward with the two records side by side and the transactions of each; the rest stay apart. Every merge can be undone. The golden records page explains the steps.
Several structures for the same record, each kept as versions with dates.
| Hierarchy | Levels and use |
|---|---|
| Structure | multi-level explosion, up to 20 levels on the showcase estate |
| Where-used | the reverse tree from any component |
A pivot can roll the record's measures up any of them; a draft version is validated against the facts before it goes live. See hierarchies.
Written in one language, tested on live rows before they are saved.
| Level | Rules |
|---|---|
| Column | quantity is greater than zero unit is convertible to the component's base unit valid-to is after valid-from |
| Row | a phantom assembly has its own BOM an active BOM has an active parent at that plant a component with scrap has a percentage under 100 |
| Business | the sum of by-product quantities stays under the base quantity no component is its own ancestor every active made item has exactly one production BOM per plant and alternative |
| Transactions in the bed | Read from |
|---|---|
| Production orders | SAP AFKO · RESB; Oracle work orders and material requirements |
| Costing runs | SAP CK11N results |
| Engineering changes | PLM change records |
Measures above are available in the pivot on any hierarchy level, by month or week, with calculated measures beside them. Drill-down opens the explosion to every level, the where-used tree, the production orders that consumed the structure, and the change records behind each effectivity date.
Engineering edits the design BOM; the plant edits quantities and alternates for its plant; costing sees all, edits none. The twelve layers apply on every door; see security.
POST /api/v1/golden/bom/explode
{
"item": "M-1183920",
"plant": "1000",
"levels": 3,
"as_of": "2026-10-01"
}200 OK
{
"levels": 3,
"components": 142,
"phantoms": 6,
"version": "v41",
"changes_since": "2026-08-12"
}The same call creates the record when nothing matches; related facts are expanded through the cross-reference; page sizes and limits are published per endpoint. See the headless API.
The objects with their real names, the keys in that system's fields, the write interface and what to set up first.
BOM header read from STKO · MAST.
Open the SAP S/4HANA page →Structure read from EGP_BOM_STRUCTURES_B (REST: itemStructures).
Open the Oracle Fusion Cloud page →BOM header read from CONFORMED.BOM. 2 objects, the keys in Snowflake fields, the write path and the prerequisites.
Open the Snowflake page →BOM header read from silver.bom. 2 objects, the keys in Databricks fields, the write path and the prerequisites.
Open the Databricks page →Names, places and figures are illustrative or anonymised; the pattern is the catalogue's.
An industrial group compared PLM and ERP BOMs for 18,000 products and found 2,900 quantity differences. The rule that flags them now runs on every change, and costing runs stopped surprising the plants.
The golden record is a governed view over rows read in place; a governed replica in your lake is used only where a source is too slow or too limited to query live, and the column says so.
One working day for the first two sources; 5 working days to a production-grade version with rules, hierarchies, security and write-back tested.
High-tech and semiconductor, Industrial manufacturing, Life sciences. The industry pages show the domains each starts with.
Bring two systems that hold the same customers, suppliers or materials. In one working day we connect them, run the match on live rows, review the queue with your steward and publish the first golden view with its API.