Lesson 2 of 6
Hierarchies and cost center groups
10 min
Listen to this lesson
Fifty cost centers are a list; managers need a structure. SAP gives two kinds: one standard hierarchy that every cost center must belong to, and any number of cost center groups for other views. Both drive reporting and allocations, so both belong in the test plan.
The standard hierarchy
SAP's learning material is precise about it: the standard hierarchy name is specified when the controlling area is created, and it is a structure to which all cost centers within the controlling area must be assigned. Each node is itself a cost center group. Because every cost center sits somewhere in it, the top node always totals the whole controlling area, which makes it the natural basis for completeness checks: if the top node does not equal the total of all cost center postings, something is unassigned or posted outside the structure.
Alternative groups
Cost center groups outside the standard hierarchy give other views: all production cost centers across plants, all cost centers of one manager, the senders of the monthly IT allocation. SAP notes that groups summarize master data for analysis, planning and allocation, and can be hierarchical themselves. Groups can also use selection variants, which make them dynamic (for example, all cost centers of category Production), although SAP notes that groups without selection variants perform better.
| Standard hierarchy | Alternative cost center group | |
|---|---|---|
| How many | Exactly one per controlling area | As many as needed |
| Completeness | Every cost center must be assigned | Contains only the cost centers you choose |
| Typical use | Organizational reporting, completeness checks, default structure | Cross-plant views, allocation senders and receivers, planning scopes |
| Time-dependent? | Assignment is not time-dependent | Not time-based; copy with a suffix to keep history |
| Contoso example | CMC_STD | ALLOC_IT_RECEIVERS, PRODUCTION_ALL |
Hierarchies in SAP Fiori reporting
In SAP S/4HANA, groups and hierarchies for Fiori analytics are handled with the Manage Global Hierarchies app, and groups are maintained in Manage Cost Center Groups. SAP's material points out a trap: groups maintained in Manage Cost Center Groups are not directly selectable in Fiori reporting. They need to be imported into a global hierarchy, or set as report relevant (Set Report Relevancy app) and replicated as runtime hierarchies (Replicate Runtime Hierarchy app). A key user who changes a group and sees no change in a Fiori report has often found this step.
- Is the structure the organization's official responsibility tree?Yes → maintain it in the standard hierarchy · No → continue
- Is it needed for an allocation or planning scope?Yes → create an alternative group named for its purpose · No → continue
- Should membership follow an attribute such as category?Yes → a group with a selection variant, accepting slower performance · No → a static group
- Must Fiori reports use it?Yes → import it into a global hierarchy or replicate it as a runtime hierarchy
How hierarchies drive allocations
Allocation cycles name their senders and receivers, often as groups. Contoso's monthly IT allocation uses IT Services as sender and the group ALLOC_IT_RECEIVERS as receivers, weighted by headcount (a statistical key figure). If a new cost center is created but not added to that group, it receives no IT costs, and the remaining receivers carry its share. The master data change is correct; the allocation result is wrong. That is why every cost center creation at Contoso has a checklist that includes "which groups must it join?"
What would you do?
A new cost center, 17101103 Detroit Quality, is created in period 5. In period 5 it shows no IT costs after the allocation, while other Detroit cost centers received slightly more than planned. What is the most likely cause?
- One standard hierarchy per controlling area; every cost center must be assigned; nodes are groups.
- Alternative groups serve analysis, planning and allocation; selection variants make them dynamic.
- For Fiori reporting, use Manage Global Hierarchies, or set report relevancy and replicate runtime hierarchies.
- Allocation results depend on group membership: add new cost centers to the right groups.
- Groups are not time-based; copy with a suffix before restructuring.
Check your understanding · not graded
Lesson check
1. Which cost centers must be assigned to the standard hierarchy?
2. What does a selection variant do for a cost center group?
3. A group changed in Manage Cost Center Groups does not appear in a Fiori report. What step is likely missing?
4. Why check that the top node of the standard hierarchy equals total postings?