Domain catalogue Reference data

Units of measure

Units and their conversions as one governed list, with the item-specific conversions that purchasing, sales and planning rely on.

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 UNITS OF MEASUREUnits of measureone id · every source key keptREAD BYGrids, pivots and drill-downswith the transactionsAPIs, SQL and agentsone policyWrite-back to the systemsacknowledged
Where the units of measure record comes from, how it is assembled, and who reads it. Other systems have their own page.
1 days
of configuration to a production-grade version
estimate
4
attribute groups in the golden record
catalogue
2
match keys
catalogue
1
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 one ERP calls it EA, another PC and the supplier catalogue says pcs; a conversion typed as 12 in one place and 10 in another moves the wrong quantity.

With Lima the units are read where they live, matched on ISO code and code per system in the crosswalk, assembled field by field and published as one golden record per real units of measure, with every source key underneath. The items and orders using a unit, and the conversions that were applied 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.

Unitcode, name, dimension (count, mass, length, volume, time), ISO code
wins: reference owner
Global conversionsfactor and offset between units of a dimension
wins: reference owner
Item conversionsper item: pallet = 48 cases, case = 12 each
wins: ERP item data, validated
Mappingscodes per system and per trading partner
wins: crosswalk
How records match

The keys, in order

ISO codecode per system in the crosswalk

Item-specific conversions are validated against the global ones, so a case always weighs at least its contents.

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

1 hierarchies

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

HierarchyLevels and use
Dimensiondimension → base unit → derived units

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
Columnfactor is positive
ISO code exists
Rowa derived unit names its base unit
an item conversion uses units of the same dimension or an item-specific link
Businessconversions are consistent around a cycle (each → case → pallet → each)
every item's base unit is in the list
What refers to it

Transactions, measures and drill-downs

Transactions in the bedRead from
Order linesquantities in order units
Stockquantities in base units
items per unitconversion errors caughtunits in use per system

Measures above are available in the pivot on any hierarchy level, by month or week, with calculated measures beside them. Drill-down opens the items and orders using a unit, and the conversions that were applied.

Security pattern

What is masked, who edits, who reads

Default policy for the domain

Reference owner edits; everyone 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/uom/convert
{
  "item": "M-1183920",
  "from": "PAL",
  "to": "EA",
  "qty": 3
}
response
200 OK
{
  "qty": 1728,
  "path": "PAL → CS (48) → EA (12)"
}

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 consumer-goods company found 218 units in use across three systems for 41 real ones. The golden list and the cycle-consistency rule ended a class of shipping errors that had been treated as normal.

illustrative scenario · Units of measure
Terms on this page

DimensionWhat a unit measures: count, mass, length, volume, time.
Base unitThe unit an item's stock is counted in.
Cycle consistencyConverting around a loop of units returns the starting quantity.
Golden recordThe one record for a real units of measure, 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; 1 working days to a production-grade version with rules, hierarchies, security and write-back tested.

Which industries use it most?

Consumer goods, Industrial manufacturing, Logistics and 3PL, 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.