SAP ABAP Data Element RSDDCALLS (Number of call-ups of an aggregate)
Hierarchy
☛
SAP_BW (Software Component) SAP Business Warehouse
⤷ BW-BEX-OT (Application Component) OLAP Technology
⤷ RSDDK (Package) BW Aggregates
⤷ BW-BEX-OT (Application Component) OLAP Technology
⤷ RSDDK (Package) BW Aggregates
Basic Data
Data Element | RSDDCALLS |
Short Description | Number of call-ups of an aggregate |
Data Type
Category of Dictionary Type | Direct Type Entry | |
Type of Object Referenced | No Information | |
Domain / Name of Reference Type | ||
Data Type | INT4 | 4-byte integer, integer number with sign |
Length | 10 | |
Decimal Places | 0 | |
Output Length | 11 | |
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 | Calls |
Medium | 18 | No. of call-ups |
Long | 20 | Number of call-ups |
Heading | 7 | Calls |
Documentation
Definition
Number of callups for the Aggregate. The counter is counted up if a Query is reading the data from the aggregate or if another aggregate is made out of it.
When optimizing the aggregate selection, also enter the number for how often the aggregate would have been used had it already been created and filled.
Be aware that for repeated execution of analyses (for queries or statistics), the number is counted up again. If you carry out the same optmization twice, one after another, the number of callups, for example, is then doubled.
Use
With this figure, you can recognize whether an aggregate has been used at all.
You should deactivate, or delete, aggregates that are unused, since the data must be constantly updated by active, filled aggregates.
History
Last changed by/on | SAP | 20140117 |
SAP Release Created in |