Lead times, lot sizes, safety stocks, planning strategies and horizons per item and site, governed with rules and history so the plan runs on numbers somebody owns.
Today planning parameters are set once at item creation and left untouched; a lead time from 2019 still drives purchase proposals.
With Lima the planning parameters are read where they live, matched on item + site and item + site + parameter + valid-from, assembled field by field and published as one golden record per real planning parameters, with every source key underneath. The proposals, receipts and stock movements a parameter influenced, and its change history 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.
Parameters are time-phased values, so a lead time change on 1 November leaves October's plan explainable.
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 |
|---|---|
| Planning family | family → group → item for parameter defaults |
| Site | region → site |
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 | lead time is between 0 and 365 days service level is between 50 and 99.9 |
| Row | a made item has an in-house production time and a routing a bought item has a delivery time and an active source |
| Business | safety stock at a site stays under 12 weeks of average demand or carries an approval planned delivery time is within 20% of the last 12 months of actual receipts or carries a reason every item in the active plan has a controller |
| Transactions in the bed | Read from |
|---|---|
| Purchase proposals | planning system |
| Actual receipts | goods receipts |
| Stock and demand | ERP and planning |
Measures above are available in the pivot on any hierarchy level, by month or week, with calculated measures beside them. Drill-down opens the proposals, receipts and stock movements a parameter influenced, and its change history.
Planners edit their controller's items; planning leads approve exceptions; everyone else reads. The twelve layers apply on every door; see security.
POST /api/v1/golden/planning/parameters
{
"item": "M-1183920",
"site": "1210",
"as_of": "2026-10-01"
}200 OK
{
"lead_time_days": 21,
"lot_size": "fixed 5000",
"safety_stock": 12000,
"strategy": "40",
"last_change": "2026-08-30",
"actual_lead_time_p50": 19
}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.
Plant data read from MARC.
Open the SAP S/4HANA page →Organisation item attributes read from EGP_SYSTEM_ITEMS_B (REST: itemsV2, planning attributes).
Open the Oracle Fusion Cloud page →Planning parameter read from CONFORMED.MATERIAL_PLANT.
Open the Snowflake page →Planning parameter read from silver.material_plant.
Open the Databricks page →Names, places and figures are illustrative or anonymised; the pattern is the catalogue's.
A $75B semiconductor equipment maker governs planning parameters for 2.9 million item-site combinations. The lead-time rule compares each parameter with actual receipts and queues the outliers for the planner every Monday.
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; 4 working days to a production-grade version with rules, hierarchies, security and write-back tested.
High-tech and semiconductor, Industrial manufacturing, Consumer goods, 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.