The organisation as governed master data: units, positions, their managers and cost centres, versioned so every system shows the same structure on the same day.
Today HR keeps the org chart, the ERP keeps a copy for approvals, the ticketing tool keeps a third for routing, and a reorganisation lands in each on its own schedule.
With Lima the organisation units are read where they live, matched on unit code and position id, assembled field by field and published as one golden record per real organisation units, with every source key underneath. Positions, holders, approvals and tickets for a unit under any version are one click away, because the transactions sit in the same bed.
Survivorship is per field; the winning source below is the usual one, and a steward's verified edit outranks it.
Positions link to golden employees and cost centres, so an approval route, a headcount plan and a ticket queue read one structure.
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.
Several structures for the same record, each kept as versions with dates.
| Hierarchy | Levels and use |
|---|---|
| Organisation | company → division → department → team → position |
| Reporting | manager chain |
| Cost | unit → cost centre |
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.
Written in one language, tested on live rows before they are saved.
| Level | Rules |
|---|---|
| Column | valid-to is after valid-from |
| Row | an active unit has a manager position a position sits in exactly one unit per version |
| Business | units with headcount above plan carry an approval every approval group in the ERP maps to an active unit no unit closes with active positions |
| Transactions in the bed | Read from |
|---|---|
| Headcount and moves | HR |
| Approvals routed | ERP workflows |
| Tickets by group | ITSM |
Measures above are available in the pivot on any hierarchy level, by month or week, with calculated measures beside them. Drill-down opens positions, holders, approvals and tickets for a unit under any version.
HR edits; managers read their subtree; finance reads all. The twelve layers apply on every door; see security.
POST /api/v1/golden/org-unit/lookup
{
"code": "DEP-441",
"as_of": "2026-10-01"
}200 OK
{
"name": "Item data",
"manager": "E-19822",
"positions": 14,
"cost_centres": [
"CC-4410",
"CC-4411"
],
"version": "v13"
}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.
The objects with their real names, the keys in that system's fields, the write interface and what to set up first.
Supervisory organisations read from Get_Organizations (Human Resources).
Open the Workday page →Organisation units and positions read from HRP1000 · HRP1001.
Open the SAP S/4HANA page →Departments and organisations read from HR_ALL_ORGANIZATION_UNITS_F (REST: organizations · departments).
Open the Oracle Fusion Cloud page →Departments read from cmn_department. 2 objects, the keys in ServiceNow fields, the write path and the prerequisites.
Open the ServiceNow page →Names, places and figures are illustrative or anonymised; the pattern is the catalogue's.
A financial services company runs reorganisations as versions: HR publishes the structure with an effective date, and the ERP's approval routes and the ticketing groups change on that date, together.
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.
One working day for the first two sources; 2 working days to a production-grade version with rules, hierarchies, security and write-back tested.
Telecom, Industrial manufacturing, Financial services, High-tech and semiconductor. The industry pages show the domains each starts with.
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.