The trees that group products for sales, planning, sourcing and reporting, kept as versioned hierarchies with one leaf per golden item.
Today the sales hierarchy in the CRM, the product hierarchy in the ERP and the category tree in the web shop share nothing but the intent; a reorganisation takes a quarter.
With Lima the classification hierarchies are read where they live, matched on node code per hierarchy and name within a parent (fuzzy), assembled field by field and published as one golden record per real product classification, with every source key underneath. From any node to its leaves, to the items, to the transactions of those items, 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.
A leaf can sit in several hierarchies at once; each hierarchy has its own version history.
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 |
|---|---|
| Sales | division → family → line → product |
| Planning | planning family → planning group |
| Sourcing | category → sub-category |
| Statutory | commodity codes and tariff chapters |
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 | a level is between 1 and the hierarchy's depth a node code is unique within a hierarchy version |
| Row | every node except the root has exactly one parent per version a node with children has no direct leaves in a strict hierarchy |
| Business | every active item sits in exactly one leaf of each mandatory hierarchy revenue by node equals the sum of its children's revenue a moved node keeps its history under the old version |
| Transactions in the bed | Read from |
|---|---|
| Sales by item | invoiced lines |
| Forecast by planning group | planning system |
| Spend by category | purchase order lines |
Measures above are available in the pivot on any hierarchy level, by month or week, with calculated measures beside them. Drill-down opens from any node to its leaves, to the items, to the transactions of those items, under any version.
Hierarchy edits by the owning function; everyone reads; planning parameters by node editable by planners. The twelve layers apply on every door; see security.
POST /api/v1/golden/hierarchy/product-sales/nodes
{
"as_of": "2026-04-15",
"node": "PWR-SUP"
}200 OK
{
"version": "v13",
"children": 6,
"leaves": 412,
"revenue_ytd": 18240000
}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.
Product hierarchy read from T179 · T179T.
Open the SAP S/4HANA page →Catalogs and categories read from EGP_CATALOGS · EGP_CATEGORIES_B (REST: itemCatalogs).
Open the Oracle Fusion Cloud page →Product family read from Product2.Family (picklist) · custom hierarchy objects.
Open the Salesforce page →Hierarchy node read from CONFORMED.PRODUCT_HIERARCHY.
Open the Snowflake page →Names, places and figures are illustrative or anonymised; the pattern is the catalogue's.
A consumer-goods company moved 1,200 products between families for a new go-to-market. The new version went live on a Monday; reports for the previous quarter still rolled up the old way, and the board pack showed both.
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; 3 working days to a production-grade version with rules, hierarchies, security and write-back tested.
Consumer goods, High-tech and semiconductor, Industrial manufacturing, 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.