The storage structure inside a site: warehouses, storage locations, zones and bins, as one hierarchy that stock movements refer to.
Today storage locations are created in the ERP, zones in the warehouse system and bin labels by the site, and a count finds stock that no system agrees on.
With Lima the storage locations are read where they live, matched on plant + storage location code and warehouse number + bin, assembled field by field and published as one golden record per real warehouse, with every source key underneath. Stock and movements per bin, zone and storage location, and the counts that touched them 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.
The hierarchy is versioned, so a re-slotting re-rolls historic movements under the old layout.
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 |
|---|---|
| Physical | site → warehouse → zone → bin |
| Logical | plant → storage location for MRP and valuation |
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 | capacity is positive temperature class is in the code list |
| Row | a bin belongs to exactly one zone a storage location marked MRP-relevant is in an active plant |
| Business | stock in a bin stays within its capacity class hazard classes in one zone are compatible stock by warehouse equals the sum of its bins |
| Transactions in the bed | Read from |
|---|---|
| Stock | SAP MARD · MCHB; warehouse stock tables |
| Movements | SAP MATDOC; warehouse tasks |
| Counts | physical inventory documents |
Measures above are available in the pivot on any hierarchy level, by month or week, with calculated measures beside them. Drill-down opens stock and movements per bin, zone and storage location, and the counts that touched them.
Site staff edit their site's structure; planners read; valuation attributes editable by finance. The twelve layers apply on every door; see security.
POST /api/v1/golden/storage/lookup
{
"plant": "1210",
"storage_location": "0001"
}200 OK
{
"golden_id": "W-1210-0001",
"warehouse": "121",
"zones": 14,
"bins": 3820,
"status": "active"
}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.
Storage location read from T001L.
Open the SAP S/4HANA page →Subinventories read from INV_SECONDARY_INVENTORIES (REST: subinventories).
Open the Oracle Fusion Cloud page →Storage location read from CONFORMED.STORAGE_LOCATION.
Open the Snowflake page →Storage location read from silver.storage_location.
Open the Databricks page →Names, places and figures are illustrative or anonymised; the pattern is the catalogue's.
A 3PL running SAP and a warehouse system for the same building governed 46,000 bins as one structure. Stock differences at count time fell by two thirds because the two systems finally described the same shelves.
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; 3 working days to a production-grade version with rules, hierarchies, security and write-back tested.
Logistics and 3PL, Consumer goods, 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.