Domain catalogue Supply chain

Planning parameters

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.

SOURCES, READ IN PLACESAP S/4HANAERPOracle Fusion CloudERPSnowflakelakehouseDatabrickslakehouseASSEMBLED1 · standardise2 · match on the domain keys3 · survive field by field4 · place in the hierarchies5 · run the column and row rules6 · publish the golden viewGOLDEN PLANNING PARAMETERSPlanning parametersone id · every source key keptREAD BYGrids, pivots and drill-downswith the transactionsAPIs, SQL and agentsone policyWrite-back to the systemsacknowledged
Where the planning parameters record comes from, how it is assembled, and who reads it. Other systems have their own page.
4 days
of configuration to a production-grade version
estimate
5
attribute groups in the golden record
catalogue
2
match keys
catalogue
2
hierarchies the record sits in
catalogue
3
kinds of transactions that refer to it
catalogue
What it is

Today, and with the golden record

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.

The golden record

5 attribute groups, and which source usually wins each

Survivorship is per field; the winning source below is the usual one, and a steward's verified edit outranks it.

Supplyprocurement type, planned delivery time, in-house production time, goods receipt time
wins: ERP plant data, owned by the planner
Lot sizinglot size procedure, minimum and maximum lot, rounding, fixed lot
wins: planner
Stock policysafety stock, safety time, reorder point, service level target
wins: planner and rules
Strategyplanning strategy, MRP type, controller, horizon, consumption mode
wins: planner
Validityvalid dates, reason, approver
wins: workflow
How records match

The keys, in order

item + siteitem + site + parameter + valid-from

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.

Where it sits

2 hierarchies

Several structures for the same record, each kept as versions with dates.

HierarchyLevels and use
Planning familyfamily → group → item for parameter defaults
Siteregion → 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.

Rules at three levels

Sample rules from the template

Written in one language, tested on live rows before they are saved.

LevelRules
Columnlead time is between 0 and 365 days
service level is between 50 and 99.9
Rowa made item has an in-house production time and a routing
a bought item has a delivery time and an active source
Businesssafety 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
What refers to it

Transactions, measures and drill-downs

Transactions in the bedRead from
Purchase proposalsplanning system
Actual receiptsgoods receipts
Stock and demandERP and planning
lead time vs actualsafety stock valueparameters changed per monthitems with stale parameters

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.

Security pattern

What is masked, who edits, who reads

Default policy for the domain

Planners edit their controller's items; planning leads approve exceptions; everyone else reads. The twelve layers apply on every door; see security.

The lookup API

Pass the keys you know, get the golden record

request
POST /api/v1/golden/planning/parameters
{
  "item": "M-1183920",
  "site": "1210",
  "as_of": "2026-10-01"
}
response
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.

On your systems

One page per system

The objects with their real names, the keys in that system's fields, the write interface and what to set up first.

A day with it

Illustrative

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.

illustrative scenario · Planning parameters
Terms on this page

Planned delivery timeThe lead time an ERP assumes for a purchased item.
Safety stockStock held against variability; a rule caps it against demand.
Time-phased parameterA value with a valid-from date, so old plans stay explainable.
Golden recordThe one record for a real planning parameters, assembled from the source records, with every value carrying its source, rule and time.
Cross-referenceThe list of source keys that belong to one golden record.
Questions

Does this domain copy data out of the systems?

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.

How long to the first golden view?

One working day for the first two sources; 4 working days to a production-grade version with rules, hierarchies, security and write-back tested.

Which industries use it most?

High-tech and semiconductor, Industrial manufacturing, Consumer goods, Life sciences. The industry pages show the domains each starts with.

See your first domain built on your data

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.