Capabilities Hierarchies

Every record in its place, in every structure it belongs to.

Levels define the shape: region, country, site; family, group, product; company, division, department.

LEGAL HIERARCHYGlobex Holdings AGlevel 1Acme Components GmbHlevel 2Acme Components Ltd (UK)level 3SALES MANAGEMENTEMEAlevel 1Germany · key accountslevel 2Acme Components GmbHlevel 3GEOGRAPHYEuropelevel 1Germany · Baden-Württemberglevel 2Böblingen sitelevel 3Acme Components GmbH · golden id L-00731one record, three places in the structure; a pivot can roll revenue up any of the three with no model change
One golden customer in three hierarchies at once. A pivot can roll revenue up any of the three with no model change.
3+
hierarchies per entity, no upper limit
product
20
levels deep on the showcase bill-of-materials explosion
showcase
1
version live at a time, with drafts validated first
product
0
facts reloaded when a hierarchy changes
product
Step by step

From levels to a live structure

Define the levelsName the levels and their order: region → country → site. A ragged hierarchy skips levels on some branches; that is allowed and stated per hierarchy.
Versions

A reorganisation is a new version, and history stays explainable

v12 · valid to 31 Mar 2026Germany reports into DACHv13 · valid from 1 Apr 2026Germany reports into Central Europedraft v14 · proposedAustria moves under Central Europeask for revenue by region as of 15 March and the old roll-up answers; as of 15 April and the new one answers; the facts stay where they area draft version is validated against the facts it will aggregate before it is promoted: orphan leaves with revenue, empty levels, double parents
Versions with validity dates; a point-in-time question picks the version valid on that date; the facts stay where they are.

When Germany moves from DACH to Central Europe on 1 April, the version valid from that date carries the new parent. Revenue by region as of 15 March rolls up the old way; as of 15 April the new way. Both are available at once for the board pack that shows the quarter under both structures.

A draft version can be compared with the live one as an aggregation diff: which nodes gain, which lose, by how much, before anyone approves it.

Valid from and toper version; one live version at a time
Draft validationorphans, empty levels, double parents, weight sums, mandatory membership
Aggregation diffwhat changes if the draft goes live, as numbers
Inherited attributesset on a node, read by descendants, versioned with the node
Crosswalknode codes per system, generated and maintained
Hierarchies by domain

The trees the catalogue defines

DomainHierarchiesTypical use
Customerlegal · sales · billing (payer, sold-to, ship-to) · industryrevenue roll-ups; credit by group; key-account coverage
Supplierlegal · purchasing (org, category, buyer) · risk · geographyspend by category and group; risk exposure
Materialproduct hierarchy · commodity · engineering (BOM) · plantplanning families; sourcing categories; where-used
Cost centrestandard hierarchy · alternative groups · profit centre treeactual vs budget by department; reorganisations as versions
GL accountfinancial statement versions · management lines · chart mappingsstatements; consolidation mappings with history
Sitelegal (company code → plant) · operational (region → cluster → site) · supply networkcapacity by region; lanes between sites
Organisationorganisation · reporting line · costapprovals; headcount; ticket routing

Product classification and cost and profit centres are the domains where hierarchies are the whole point.

In the grid and the pivot

The same structure, used

revenue by sales hierarchy · 2026v13 · valid from 1 Aprv12legal treegeography
nodeJanFebMarAprMayJun
EMEA4.82M4.61M5.04M5.11M5.30M5.48M
Central Europe2.10M2.02M2.21M3.02M3.11M3.20M
Germany · key accounts0.91M0.88M0.97M0.99M1.02M1.05M
DACH1.80M1.71M1.86M1.02M1.05M1.09M
Nordics0.92M0.88M0.97M1.07M1.14M1.19M
Total4.82M4.61M5.04M5.11M5.30M5.48M

Switch the chip and the same rows roll up the legal tree or the geography. April shows Germany's move: Central Europe gains what DACH loses, and the total is unchanged.

How master-data hubs usually do it

What is standard, and what is different here

Alternate hierarchies are common in master-data products, and hub buyers should expect them. Versioning a hierarchy with validity dates is rarer, and validating a draft against the facts it will aggregate is a planning-tool feature that the hubs lack, because the facts sit elsewhere.

Here the hierarchy is a versioned table in the same bed as the transactions, so the validation, the aggregation diff and the point-in-time roll-up are queries, and a reorganised sales hierarchy re-rolls history with no reload.

Standard everywherealternate hierarchies; drag-and-drop editing
Hereversions with dates; validation against facts; aggregation diff before go-live
Consequencehistory re-rolls under the new structure with zero reloads
Terms on this page

LevelA named layer in a hierarchy, such as region, country, site.
Ragged hierarchyA tree whose branches have different depths.
VersionA hierarchy as it stood between two dates; facts roll up under the version valid at their date.
Inherited attributeA value set on a node and read by every descendant.
Aggregation diffThe change in totals per node between two versions, computed before a draft goes live.
Questions

Can one entity be in two places in the same hierarchy?

In a strict hierarchy, one leaf per version; the validator refuses a second parent. A domain can declare a hierarchy as a network, and then the rule is per node with weights that must sum to 100%.

Who edits hierarchies?

The owning function, through a draft that the validator checks and an approver publishes. Everyone reads; the audit trail records every move.

How do planning systems get them?

Through the Backbone's planning integration, loaded as the target's own hierarchy objects with the nine checks. See planning integration.

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.