The code lists every system needs, kept once: countries and regions, Incoterms, payment terms, languages, and the crosswalk to each system's local codes.
Today each system has its own list of countries and payment terms; a new Incoterm is added to four systems on four dates.
With Lima the code lists are read where they live, matched on list + code and standard code (ISO), assembled field by field and published as one golden record per real countries, regions, with every source key underneath. The fields and rows using a code, across systems 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.
A code list is a small master-data domain with the same history, rules and security as the big ones.
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 |
|---|---|
| Geography | continent → country → region |
| Standard | standard → list → code |
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 | ISO codes match the standard valid-to is after valid-from |
| Row | a retired code names its replacement every code has a name in the default language |
| Business | every field bound to a list holds only active codes as of the row's date each local code maps to exactly one golden code |
| Transactions in the bed | Read from |
|---|---|
| Documents using the codes | orders, invoices, deliveries |
Measures above are available in the pivot on any hierarchy level, by month or week, with calculated measures beside them. Drill-down opens the fields and rows using a code, across systems.
Reference owner edits; everyone reads; a retirement needs an approval. The twelve layers apply on every door; see security.
POST /api/v1/golden/codes/incoterms
{
"as_of": "2026-10-01"
}200 OK
{
"version": "2020",
"codes": 11,
"crosswalks": {
"sap": "INCO1",
"oracle": "FOB lookup",
"salesforce": "Incoterm__c"
}
}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.
Countries and regions read from T005 · T005T · T005S.
Open the SAP S/4HANA page →Territories and geographies read from FND_TERRITORIES · HZ_GEOGRAPHIES (REST: geographies).
Open the Oracle Fusion Cloud page →Picklists and state/country read from State and Country Picklists · custom code objects.
Open the Salesforce page →Choice lists read from sys_choice. 2 objects, the keys in ServiceNow fields, the write path and the prerequisites.
Open the ServiceNow page →Code list read from CONFORMED.CODE_LIST. 3 objects, the keys in Snowflake fields, the write path and the prerequisites.
Open the Snowflake page →Names, places and figures are illustrative or anonymised; the pattern is the catalogue's.
A global manufacturer governs 84 code lists in one place. When a country changed its regions, one change reached the ERPs, the CRM and the ticketing tool, with the old codes readable in history.
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; 1 working days to a production-grade version with rules, hierarchies, security and write-back tested.
Logistics and 3PL, Consumer goods, Industrial manufacturing, High-tech and semiconductor, Telecom. 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.