Hierarchy
SAP_FIN (Software Component) SAP_FIN⤷
FI-SL-SL (Application Component) Basic Functions⤷
GBRU (Package) FI-SL rollup
Basic Data
| Data Element | HIERSET |
| Short Description | Hierarchy set |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | SETNAME | |
| Data Type | CHAR | Character String |
| Length | 24 | |
| Decimal Places | 0 | |
| Output Length | 24 | |
| Value Table |
Further Characteristics
| Search Help: Name | ||
| Search Help: Parameters | ||
| Parameter ID | ||
| Default Component name | ||
| Change document | ||
| No Input History | ||
| Basic direction is set to LTR | ||
| No BIDI Filtering |
Field Label
| Length | Field Label | |
| Short | 10 | Hier. set |
| Medium | 15 | Hierarchy set |
| Long | 20 | Hierarchy set |
| Heading | 12 | Hier. set |
Documentation
Definition
The rollup header set determines the maximum amount of data to be selected for the rollup. This data is valid for all rollup sequences. You can limit the amount of data to be selected at sequence level but you cannot, however, increase this amount of data.
For performance reasons, this set must contain at least the first four dimensions of every GLX summary table.
- Ledger (field RLDNR),
- Record type (field RRCTY),
- Version (field RVERS),
- Company code (field BUKRS or RBUKRS) for local ledgers or
Global company (field RCOMP) for global ledgers.
Description
For rollups with hierarchical summarization, the rollup header set is used to define the structure for the hierarchical summarization. A single-dimension set is used for this and it also has to be included in the rollup header set together with the above required dimensions. This single-dimension set must have a representative value for each set node; the summarized values will later be saved under this representative value. For technical reasons, each basic set in this single-dimension set must have a representative value.
When you enter a dimension in the 'Hierachy dimension' field, the system is told which set in the rollup header set is to used to define the hierarchy.
Example
A single-dimension set, that describes a business area hierarchy, could look as follows (the other required dimensions in the rollup header set needed for determining a selection range are omitted in order to provide a better overview):
:RBUSA-------: Business area
|OM-RBUSA1000| Summarization to 1000 (rep. value 1000)
:S-----------:
|
| :------------:
>---|OM-RBUSA1100| Summarization to 1100 (rep. value 1100)
| :S-----------:
| |
| | :------------:
| >---|OM-RBUSA1110| Summarization to 1110 (rep. value 1110)
| | :B-----------: 1111
| | 1112
| | 1113
| |
| | :------------:
| >---|OM-RBUSA1120| Business area 1120 (rep. value 1120)
| | :B-----------: 1120
| |
| | :------------:
| >---|OM-RBUSA1130| Business area 1130 (rep. value 1130)
| :B-----------: 1130
|
| :------------:
>---|OM-RBUSA1200| Summarization to 1200 (rep. value 1200)
| :B-----------: 1210
| 1220
|
| :------------:
>---|OM-RBUSA1300| Business area 1300 (rep. value 1300)
:B-----------: 1300
Explanation:
The basic sets OM-RBUSA1120, OM-RBUSA1130 and OM-RBUSA1300 are basic sets that contain only one value and therefore are not node business areas. For technical reasons, these sets must also have a representative value, even though they are not node business areas.
Note
You can also enter the set ID as a generic entry using the '*' character.
History
| Last changed by/on | SAP | 19970708 |
| SAP Release Created in |
