Hierarchy
SAP_FIN (Software Component) SAP_FIN⤷
FI-SL-SL (Application Component) Basic Functions⤷
GBRU (Package) FI-SL rollup
Basic Data
| Data Element | ROLLUPN |
| Short Description | Rollup (new) |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | ROLLUPN | |
| Data Type | CHAR | Character String |
| Length | 8 | |
| Decimal Places | 0 | |
| Output Length | 8 | |
| Value Table | T807H |
Further Characteristics
| Search Help: Name | ||
| Search Help: Parameters | ||
| Parameter ID | GRJ | |
| Default Component name | ||
| Change document | ||
| No Input History | ||
| Basic direction is set to LTR | ||
| No BIDI Filtering |
Field Label
| Length | Field Label | |
| Short | 10 | Rollup |
| Medium | 15 | Rollup |
| Long | 20 | Rollup |
| Heading | 8 | Rollup |
Documentation
Description
Rollups enable you to summarize data from one or more ledgers to one or more rollup ledgers. This type of summarization could, for example, be useful if you want to repeatedly create cumulated overviews using the Report Writer, but the data in the source ledger is too detailed for this. In this case, the Report Writer would always have to read the detailed data from the source ledger in order to be able to summarize it again. This would adversely affect processing time. If, however, you have summarized this detailed source data in a rollup ledger beforehand using a rollup, and the Report Writer creates reports using the summarized data in this rollup ledger, system performance is improved considerably.
In addition to this, rollups also allow you to copy a certain amount of data (e.g. specific accounts) from a source ledger to a rollup ledger, to substitute certain data (e.g. products are summarized into a product group), and to summarize data of a ledger with, for example, 12 periods into a rollup ledger that only has 4 periods.
Summarization types
For the rollup, there are two basic types of summarization:
- Standard rollup with single-level summarization
Here you can enter several sequences per rollup which are then processed in order of sequence number. Thus, you can, for example, update several rollup ledgers according to the summarization rules you have defined by copying or substituting data from the source ledger(s), or by simply omitting fields.
- Rollup with hierarchical (multi-level) summarization
The rollup with hierarchical summarization allows you to summarize data from a source ledger according to a hierarchy structure you have defined (e.g. cost center hierarchy). If, for example, the data in the source ledger for the individual end cost centers is detailed, the rollup ledger only stores the data for the node cost centers in summarized form after the rollup has been executed.
Definition
The following information is stored in a rollup definition:
- Valid for all sequences
- Authorization group
- Sender table
The sender table contains the source data to be summarized.
When you execute the rollup, the data from this table is read and processed further. - Receiver table
The receiver table contains the rollup ledger(s) into which the summarized data is to be rolled up. - User exit
Using this user exit, you can carry out separate validations before the processing of the database records, for example, to check the execution date entered. - Reset set
Before you actually roll up the data, you can reset specific data in the rollup ledger(s) to zero in order to guarantee consistent data before the rollup. In this set you define the data that is to be reset. - Rollup header set
The rollup header set determines the maximum amount of data to be selected from the source ledger(s) for the rollup. You can limit this amount of data using individual rollup sequence sets, but cannot however increase this amount of data.
The rollup header set has a special function in hierarchical summarization:
Here it also determines the hierarchy structure used for the bottom-up summarization. - Hierarchy dimension
The dimension you enter in this field determines the single-dimension set in the rollup header set which specifies the hierarchy structure. - Default values that determine whether values are to be accumulated, whether blank records are to be inserted or line items are to be written, and whether the internal business volume is to be eliminated in hierarchical summarization or whether a partner summarization is to be executed.
- Per rollup sequence
- Sequence set
With the sequence set, you can further limit the maximum amount of data to be selected by the rollup header set per sequence. If you enter a sequence set, the relevant sequence can only read those database records that satisfy both the rollup header set and the sequence set when you execute the rollup. - Activity grouping code
The activity grouping code allows you to further limit the amount of data selected. It further qualifies the selection made by a set (e.g. OR conditions). - Field movement
With the field movement you determine which fields are to be transferred to the receiver table in addition to the fixed fields defined in T800M. The field movement thus allows you to control how the summarization is to be carried out:
If you do not transfer fields to the receiver table, these fields are summarized (example: the source ledger stores the combination "account/cost center", but only the field "account" is transferred to the rollup ledger. The cost centers are thus summarized for each account).
With field movements, you can also carry out substitutions, for example, if you want to summarize certain products under a product group. You do so using substitution activities which you assign direct to the respective field movement. - Ledger
Here you enter the ledger to which you want to roll up the data.
Procedure for defining a rollup
- Create rollup ledger (if one does not already exist)
The data is later summarized into the rollup ledger. Here you must define amongst other things which company codes/global companies are to be assigned to the ledger and which field groups the ledger is to store. - Create reset set for receiver table (as required)
The reset set must at least contain the dimensions "ledger", "record type", "version" and "company code"/"global company". - Create rollup header set for sender table
The rollup header set must at least contain the dimensions "ledger", "record type", "version" and "company code"/"global company". For a rollup with hierarchical summarization, you must also create a single-dimension set to define the hierarchy that is to be summarized. You must include this single-dimension set in your rollup header set. If you enter the dimension of the single-dimension set in the field 'Hierarchy dimension', the system recognizes that this set is to be used in the rollup header set to determine the hierarchy structure.
When you execute the rollup, the summarized values will then be stored under the name of the representative value of the relevant set. When defining such a hierarchy set, you should make sure that each basic set also has a representative value even if it does not represent an area (see below: basic set OM-RBUSA-1300).
Example of a hierarchy set:
:RBUSA-------: Business area
|OM-RBUSA1000| Summarization to 1000
:S-----------: (rep. value 1000)
|
| :------------:
>---|OM-RBUSA1100| Summarization to 1100
| :S-----------: (rep. value 1100)
| |
| | :------------:
| >---|OM-RBUSA1110| Summarization to 1110
| | :B-----------: 1111 (rep. value 1110)
| | 1112
| | 1113
| |
| | :------------:
| >---|OM-RBUSA1120| Business area 1120
| | :B-----------: 1120 (rep. value 1120)
| |
| | :------------:
| >---|OM-RBUSA1130| Business area 1130
| :B-----------: 1130 (rep. value 1130)
|
| :------------:
>---|OM-RBUSA1200| Summarization to 1200
| :B-----------: 1210 (rep. value 1200)
| 1220
|
| :------------:
>---|OM-RBUSA1300| Business area 1300
:B-----------: 1300 (rep. value 1300) - Define sequence sets for the sender table (if required)
For each sequence, you can further limit the amount of data to be selected (only for rollups with single-level summarization). - Define selection rule for table 'GLU1' (if required)
You should only use a selection rule if you cannot limit the amount of data you want to roll up using a set (only for rollups with single-level summarization). - Define field movements for sender and receiver table
When defining the field movements, you should take into account which fields the rollup ledger(s) is (are) to store and how the summarization is to be carried out. For example, if you want to summarize certain accounts under
History
| Last changed by/on | SAP | 19930713 |
| SAP Release Created in | 470 |
