Levels define the shape: region, country, site; family, group, product; company, division, department.
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.
| Domain | Hierarchies | Typical use |
|---|---|---|
| Customer | legal · sales · billing (payer, sold-to, ship-to) · industry | revenue roll-ups; credit by group; key-account coverage |
| Supplier | legal · purchasing (org, category, buyer) · risk · geography | spend by category and group; risk exposure |
| Material | product hierarchy · commodity · engineering (BOM) · plant | planning families; sourcing categories; where-used |
| Cost centre | standard hierarchy · alternative groups · profit centre tree | actual vs budget by department; reorganisations as versions |
| GL account | financial statement versions · management lines · chart mappings | statements; consolidation mappings with history |
| Site | legal (company code → plant) · operational (region → cluster → site) · supply network | capacity by region; lanes between sites |
| Organisation | organisation · reporting line · cost | approvals; headcount; ticket routing |
Product classification and cost and profit centres are the domains where hierarchies are the whole point.
| node | Jan | Feb | Mar | Apr | May | Jun |
|---|---|---|---|---|---|---|
| EMEA | 4.82M | 4.61M | 5.04M | 5.11M | 5.30M | 5.48M |
| Central Europe | 2.10M | 2.02M | 2.21M | 3.02M | 3.11M | 3.20M |
| Germany · key accounts | 0.91M | 0.88M | 0.97M | 0.99M | 1.02M | 1.05M |
| DACH | 1.80M | 1.71M | 1.86M | 1.02M | 1.05M | 1.09M |
| Nordics | 0.92M | 0.88M | 0.97M | 1.07M | 1.14M | 1.19M |
| Total | 4.82M | 4.61M | 5.04M | 5.11M | 5.30M | 5.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.
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.
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%.
The owning function, through a draft that the validator checks and an approver publishes. Everyone reads; the audit trail records every move.
Through the Backbone's planning integration, loaded as the target's own hierarchy objects with the nine checks. See planning integration.
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.