Domain catalogue Supply chain

Contracts and agreements

Purchase and sales agreements as master data: parties, items, prices, validity and limits, linked to the orders released against them.

SOURCES, READ IN PLACESAP S/4HANAERPOracle Fusion CloudERPSalesforceCRMSnowflakelakehouseASSEMBLED1 · standardise2 · match on the domain keys3 · survive field by field4 · place in the hierarchies5 · run the column and row rules6 · publish the golden viewGOLDEN CONTRACTS AND AGREEMENTSContracts and agreementsone id · every source key keptREAD BYGrids, pivots and drill-downswith the transactionsAPIs, SQL and agentsone policyWrite-back to the systemsacknowledged
Where the contracts and agreements record comes from, how it is assembled, and who reads it. Other systems have their own page.
3 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
2
kinds of transactions that refer to it
catalogue
What it is

Today, and with the golden record

Today contracts live in a contract tool, outline agreements in the ERP and the signed PDF in a shared folder; the ERP releases orders against an expired agreement.

With Lima the contracts are read where they live, matched on agreement number per system and party + type + validity (fuzzy), assembled field by field and published as one golden record per real contracts, with every source key underneath. The orders and invoices released against an agreement, by item and month 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.

Agreementnumber, type, party (golden), owner, validity, currency
wins: contract tool and ERP
Itemsgolden items, target quantities or values, prices, lead times
wins: ERP
Limitstarget value, released value, remaining, renewal terms
wins: derived from orders
Documentssigned version, amendments, effective dates
wins: contract tool
How records match

The keys, in order

agreement number per systemparty + type + validity (fuzzy)

Release orders are transactions in the bed, so remaining value is a live measure on the agreement record.

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
Partyparty → agreements → items
Categorycategory → agreements

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
Columnvalid-to is after valid-from
target value is positive
Rowan active agreement names an active party
an agreement with items has a price per item
Businessreleased value stays under the target value or carries an approval
orders after valid-to are refused
an agreement expiring within 60 days with no renewal opens a task
What refers to it

Transactions, measures and drill-downs

Transactions in the bedRead from
Release ordersSAP EKKO with agreement reference; Oracle releases
InvoicesAP and AR
released vs targetagreements expiring by monthprice variance to agreement

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 and invoices released against an agreement, by item and month.

Security pattern

What is masked, who edits, who reads

Default policy for the domain

Commercial terms visible to purchasing, sales and finance; documents by owner; everyone reads validity. 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/agreement/lookup
{
  "party": "L-00731",
  "type": "purchase",
  "as_of": "2026-10-01"
}
response
200 OK
{
  "agreements": [
    {
      "id": "AG-4409",
      "valid_to": "2027-06-30",
      "target": 2400000,
      "released": 1710000
    }
  ]
}

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 telecom operator linked 3,100 supplier agreements to the purchase orders released against them. Orders against expired agreements stopped the week the rule went live, and renewals started 60 days earlier.

illustrative scenario · Contracts and agreements
Terms on this page

Outline agreementSAP's contract or scheduling agreement that orders are released against.
Release orderAn order that consumes an agreement's target.
Target valueThe agreed maximum an agreement covers.
Golden recordThe one record for a real contracts, 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; 3 working days to a production-grade version with rules, hierarchies, security and write-back tested.

Which industries use it most?

Industrial manufacturing, High-tech and semiconductor, Consumer goods, Telecom. 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.