Domain catalogue Supply chain

Sourcing rules and supplier-item links

Which supplier supplies which item to which site, at what price and lead time, with quotas and validity, as one governed set of relationships.

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 SOURCING RULES AND SUPPLIER-ITEM LINKSSourcing rules and supplier-item linksone id · every source key keptREAD BYGrids, pivots and drill-downswith the transactionsAPIs, SQL and agentsone policyWrite-back to the systemsacknowledged
Where the sourcing rules and supplier-item links 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
4
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 info records, source lists and approved supplier lists disagree; a purchase proposal picks a supplier that quality blocked last month.

With Lima the sourcing rules are read where they live, matched on item + supplier + site and supplier part number + supplier, assembled field by field and published as one golden record per real sourcing rules, with every source key underneath. The orders, receipts and quality results for a link, and the contract behind its price are one click away, because the transactions sit in the same bed.

The golden record

4 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.

Linkgolden item, golden supplier, site, supplier part number, status
wins: purchasing
Termsprice with validity, currency, unit, minimum quantity, lead time
wins: purchasing and contracts
Priorityquota arrangement, preferred, blocked, valid dates
wins: purchasing and quality
Complianceapproved supplier list status, certificates, country of origin
wins: quality and compliance
How records match

The keys, in order

item + supplier + sitesupplier part number + supplier

Both ends of a link resolve to golden records, so a merged supplier keeps every source relationship.

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
Categorycategory → item → sources
Suppliersupplier → items supplied

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
Columnquota is between 0 and 100
lead time is between 0 and 365 days
Rowa preferred source has an active price
a blocked source has a reason and a date
Businessquotas for an item and site sum to 100%
every purchased item at a site has at least one approved source
no purchase proposal goes to a blocked source
What refers to it

Transactions, measures and drill-downs

Transactions in the bedRead from
Purchase ordersSAP EKPO by source
Receipts and quality resultsgoods receipts, inspections
Contractsoutline agreements
spend by sourceon-time rate by sourceprice vs contractitems with a single source

Measures above are available in the pivot on any hierarchy level, by month or week, with calculated measures beside them. Drill-down opens the orders, receipts and quality results for a link, and the contract behind its price.

Security pattern

What is masked, who edits, who reads

Default policy for the domain

Purchasing edits; quality edits the approval status; planners read. 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/source/resolve
{
  "item": "M-1183920",
  "site": "1210",
  "date": "2026-10-01"
}
response
200 OK
{
  "sources": [
    {
      "supplier": "L-00731",
      "quota": 70,
      "lead_time": 21,
      "status": "preferred"
    },
    {
      "supplier": "L-00912",
      "quota": 30,
      "lead_time": 28,
      "status": "approved"
    }
  ]
}

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 high-tech manufacturer with 58,900 item-supplier links across two ERPs found 2,140 links pointing at merged or blocked suppliers. The golden links now feed the planning system's sourcing directly.

illustrative scenario · Sourcing rules and supplier-item links
Terms on this page

Info recordSAP's record of a supplier-item relationship with price and lead time.
Quota arrangementHow demand is split between sources.
Approved supplier listQuality's list of who may supply which item.
Golden recordThe one record for a real sourcing rules, 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.