The pivot is a data-entry screen as well as a view. A planner types a quarter's target at a region and the platform disaggregates it to the countries and the months by a chosen method: last year's mix, equal shares, a time profile, or weights kept as master data.
| node | Oct | Nov | Dec | Q4 |
|---|---|---|---|---|
| EMEA | 4,080 | 3,960 | 3,960 | 12,000 |
| Germany | 1,836 | 1,782 | 1,782 | 5,400 |
| France | 1,020 | 990 | 990 | 3,000 |
| Italy | 816 | 792 | 792 | 2,400 |
| Nordics | 408 | 396 | 396 | 1,200 |
The typed cell is outlined; the split cells are italic until saved; Nordics is locked, so its share stays and the other three absorb the change. Hover a split cell to see the weight that produced it.
| Method | How the children get their share | When it fits |
|---|---|---|
| Proportional | each child's share of a reference measure (last year's actuals, current forecast, headcount) | targets that should follow the current mix |
| Equal | the same value to each child | new products or regions with no history |
| Time-phased | a profile from the calendar or a reference measure spreads a value across weeks or months | seasonal demand, promotions |
| Weighted | weights kept as master data on the hierarchy node, versioned and approved | allocation keys that finance owns |
Methods combine: a weighted split across countries, then a time-phased split across weeks. The audit entry records both.
Planning tools own disaggregation; master-data products own governance. Because the entry grid sits on the bed, the typed numbers are governed values from the first keystroke: survivorship ranks them against feeds, rules check them, security limits who may enter at which node, and the audit trail keeps the intent (who typed what, at which node, with which method), which planning tools usually discard.
Weights are master data too: an allocation key changes through a versioned hierarchy attribute with an approval, and every split after the change uses the new key.
Yes, through the API and SQL, as a version; the Backbone's planning integration loads them into the target's model.
Entries are per version with cell-level history; a conflict shows both values and asks; the audit trail keeps both.
Yes: a weight can be a calculated measure (share of revenue), recomputed on a schedule and versioned like an entered weight.
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.
