Hierarchy
SAP_BASIS (Software Component) SAP Basis Component⤷
BC-CCM-MON (Application Component) Monitoring⤷
SMOI (Package) CCMS: Monitoring Architecture
Basic Data
| Data Element | ALPFPOLKEY |
| Short Description | Name of a CPH Collection and Reorganization Schema |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | CHAR40 | |
| Data Type | CHAR | Character String |
| Length | 40 | |
| Decimal Places | 0 | |
| Output Length | 40 | |
| 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 | Schema |
| Medium | 15 | C/R Schema |
| Long | 25 | Collect./Reorg. Schema |
| Heading | 35 | Collection/Reorganization Schema |
Documentation
Definition
Collection and reorganization schemata belong to the Central Performance History (CPH) of the monitoring architecture. A schema of this type specifies how long data that is assigned to this schema is to be stored in the CPH, and in what resolution.
Data in the CPH is stored in different Aggregates and Resolutions.
Use
You specify the retention period of the different aggregates in a collection and reorganization schema, depending on its resolution - values with a resolution of minutes are usually not stored as long as values with a resolution of days. The main reason for this is the enormous storage requirement that long-term storage in a fine resolution requires. Values in a very fine resolution (such as minutes) are also not especially well suited to analysis over a longer period of time, since with a coarser resolution, the number of measurements per measuring point increases, ensuring better statistics.
Dependencies
Example
History
| Last changed by/on | SAP | 20040312 |
| SAP Release Created in |
