The Extractor Framework (EFWK) is used to transfer ABAP statistics data to the associated BI of the SAP Solution Manager. No process chains and DataSources are used in this process; the data is writtend directly to a number DSOs by jobs.
Note
For more information about the data flow for monitoring data, see Data Flow for Monitoring Data
The BI objects of the ABAP statistics data are grouped into different InfoAreas; these largely correspond to the analysis views of the Workload Monitor. For each of these InfoAreas, there is a set of six different DSO objects, which are supplied with data by the Extractor Framework, and which contain the corresponding aggregated data in the different time resolutions.
To allow further use of the statistics data, it must be written to a number of InfoCubes. This is done by the job CCMS_ASR_AGGR_DATA_UPDATE, which runs every hour.
There are two InfoCubes with identical structures (twin Cubes) for each time resolution of the statistics data. The data is initially written to the first InfoCube in each case, until the end of retention period for the relevant resolution, as specified in the setup of the interactive reporting. More data is then written to the second Cube in each case, until the end of the set retention period is reached there, too. The first Cube is then deleted, and the cycle starts again.
Since it is not possible to determine at any particular point in time which of the twin cubes contains the desired performance data, a corresponding MultiProvider is used for queries on this data. The data of both of the twin cubes is available to this MultiProvider.
The following naming conventions apply for these InfoProviders:
Type |
Naming Convention |
Example |
---|---|---|
DSO object |
0CCM<DSO abbreviation><resolution abbreviation> |
0CCMAWDH (Time profile, hourly data) |
InfoCube (Twin cubes) |
0CCM<IC abbreviation><resolution abbreviation>1 0CCM<IC abbreviation><resolution abbreviation>2 Note In each case, there are two twin cubes, with the suffixes 1 and 2. End of the note. |
0CCMAWDH1 0CCMAWDH2 (Time profile, hourly data) |
MultiProvider (individual resolutions) |
0CCM0CCM<MP abbreviation><resolution abbreviation> |
0CCMAWDH (Time profile, hourly data) |
MultiProvider (All resolutions) |
0CCM0CCM<MP abbreviations> |
0CCMAW (Time profile, all resolutions) |
The following time resolutions exist, and have the corresponding abbreviations:
Resolution |
Resolution Abbreviation |
---|---|
Hourly data |
DH |
Daily data |
DD |
Weekly data |
WD |
Weekly data with hourly resolution |
WH |
Monthly data |
MD |
Monthly data with hourly resolution |
MH |
Note
Note that the aggregates with hourly resolution are not filled with values by default. The reason for this is the large quantity of data and the fact that these aggregates are not used in any standard reports delivered by SAP. If you require the aggregates, you can manually activate the data provision. For more information, see SAP Note 1760348.
The statistics data are grouped into different InfoAreas. The following InfoAreas exist, and have the corresponding abbreviations:
InfoArea |
DSO Object Abbreviation |
InfoCube Abbreviation |
MultiProvider Abbreviation |
---|---|---|---|
ATX |
TX |
TXC |
|
AWC |
WC |
WSC |
|
AWP |
WP |
WSP |
|
WS |
WS |
BWS |
|
DAW |
AW |
AW |
|
EX |
EX |
AEX |
|
RC |
RC |
BRC |
|
RD |
RD |
BRD |
|
RS |
RS |
BRS |
|
RT |
RT |
BRT |
|
WD |
WD |
BWD |
|
ES |
ES |
BES |
|
IQ |
IQ |
BIQ |
|
TD |
TD |
BTD |
Note
For more information about the concept of the different aggregates, see Aggregation.