SAP ABAP Data Element WLBWPCTRL (Share of Total Runtime that is Rollup Time (%))
Hierarchy
☛
SAP_BASIS (Software Component) SAP Basis Component
⤷
BC-CCM-MON (Application Component) Monitoring
⤷
SAPWL_FRONTEND (Package) SAP: Workload Display, Enjoy & OO Version - ST03N

⤷

⤷

Basic Data
Data Element | WLBWPCTRL |
Short Description | Share of Total Runtime that is Rollup Time (%) |
Data Type
Category of Dictionary Type | D | Domain |
Type of Object Referenced | No Information | |
Domain / Name of Reference Type | WLBWPCENT1 | |
Data Type | DEC | Counter or amount field with comma and sign |
Length | 5 | |
Decimal Places | 2 | |
Output Length | 10 | |
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 | 12 | % Rollup |
Medium | 22 | Rollup / Total Time |
Long | 36 | Rollup Time / Total Runtime (%) |
Heading | 55 | Share of Total Runtime that is Rollup Time (%) |
Documentation
Definition
If InfoCube data is changed, the affected aggregates must also be brought up to the newest status. There are a number of options for doing this:
Reconstruct: The values of the affected aggregates are completely recalculated. This method offers the best performance if a large proportion of the underlying master data has been changed (as of around 20%), or the aggregate has been newly defined.
If the affected aggregates are not completely recalculated, but are rather corrected on the basis of the changed data, this is described as rollup (changing the transaction data) or delta (changing the master data).
History
Last changed by/on | SAP | 20040312 |
SAP Release Created in | 50A |