Domain catalogue Locations

Plant and site

One record per physical site: plant, distribution centre, office, store or lab, with its codes in every system and its calendar, address and roles.

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

Today, and with the golden record

Today a plant is a four-character code in SAP, an inventory organisation in Oracle, a location in Workday and a site in ServiceNow, and a new site is created four times.

With Lima the sites are read where they live, matched on geocode and address (standardised) and site name and country (fuzzy), assembled field by field and published as one golden record per real plant, with every source key underneath. Stock, orders, production and headcount at the site, and every system's code for it 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.

Identitysite id, name, type, address, geocode, time zone
wins: ERP and facilities
Codesplant, inventory org, company code, location codes per system
wins: crosswalk
Rolesmanufacturing, storage, sales, service, office; capabilities
wins: operations
Operating datacalendar, shifts, capacity classes, languages
wins: ERP and HR
Lifecycleplanned, opening, active, closing, closed
wins: operations and finance
How records match

The keys, in order

geocode and address (standardised)site name and country (fuzzy)plant code per system in the crosswalk

Two site records with the same geocode and a different role are one site with two roles, and the rules keep them together.

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

3 hierarchies

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

HierarchyLevels and use
Legalcompany code → plant
Operationalregion → cluster → site
Supply networksource site → destination site lanes

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
Columntime zone is a valid IANA name
country matches the address
Rowan active manufacturing site has a factory calendar
a closing site has a closing date and a successor for open stock
a site with a sales role has a sales organisation
Businessevery open order names an active site
one site per company code per address
capacity by region equals the sum of its sites
What refers to it

Transactions, measures and drill-downs

Transactions in the bedRead from
Stock by siteSAP MARD; Oracle on-hand
Orders by sitesales and purchase orders
Productionproduction orders
HeadcountHR
throughput by site and monthstock valueheadcounton-time shipment

Measures above are available in the pivot on any hierarchy level, by month or week, with calculated measures beside them. Drill-down opens stock, orders, production and headcount at the site, and every system's code for it.

Security pattern

What is masked, who edits, who reads

Default policy for the domain

Site facts readable by all; codes and lifecycle editable by the operations data owner; addresses verified before publication. 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/site/lookup
{
  "name": "Böblingen",
  "country": "DE",
  "role": "manufacturing"
}
response
200 OK
{
  "golden_id": "S-0114",
  "confidence": 0.98,
  "xref": {
    "sap_plant": "1210",
    "oracle_inv_org": "BOB1",
    "workday": "LOC-338"
  },
  "calendar": "DE-BW",
  "status": "active"
}

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 logistics group with 214 sites in five systems found 31 sites created twice and 6 closed sites still receiving orders. The golden site list became the reference for every new system rollout.

illustrative scenario · Plant and site
Terms on this page

PlantSAP's unit for a location that holds stock or makes products.
Inventory organisationOracle's equivalent of a plant.
Factory calendarThe working days and shifts a site runs.
Golden recordThe one record for a real plant, 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; 2 working days to a production-grade version with rules, hierarchies, security and write-back tested.

Which industries use it most?

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