Data Flow 
With IT Performance Reporting, you can centrally display the development over time of the most important performance data for your monitored systems in the SAP Solution Manager to identify potential problems early, and to obtain an overview of the utilization and performance of your systems. More information about this is available in the SAP Solution Manager documentation.
The transfer of the statistics data to the associated BI of the SAP Solution Manager is performed using the Extractor Framework (EFWK). Only the aggregates of the statistics records are stored in BI, not the individual records themselves.
Note
The transfer of the statistics data is performed as follows, depending on the release status of the managed systems:
If the managed system has a release as of SAP Web AS 6.20, and has the SAP Solution Tools Plug-In ST-PI with a release as of 2008_1, the aggregates of the statistics data are calculated in the managed systems and only these aggregates are transferred to the SAP Solution Manager system. This has the advantage that the volume of transferred statistics data is much smaller and therefore generates a correspondingly lower system workload and network load.
If the managed system does not fulfill the above prerequisites, but does have a release as of SAP Basis 4.6D, the individual records are transferred to the SAP Solution Manager system, and are aggregated there in the EFWK, before the aggregates are saved in BI.
Statistics data from managed systems with a release prior to SAP Basis 4.6D cannot be saved in BI.
The transfer of the ABAP statistics data to the associated BI of the SAP Solution Manager is performed using the Extractor Framework (EFWK). No process chains and DataSources are used in this process; the data is writtend directly to a number DSOs by jobs. In BI, there are various InfoAreas (path 
Computing Center Management System 
Statistics Data 
), each of which represents an aspect of the statistics data. Many of these InfoAreas are based on Analysis Views of the Workload Monitor (transaction ST03). There are currently the following InfoAreas:
For each InfoArea, there are six different DSOs, each of which contain data in a particular resolution. To make it easier to differentiate between them, the technical names of these DSOs follow the naming convention 0CCM<InfoArea abbreviation><resolution suffix>. In detail:
To allow further use of the ABAP statistics data, it must be written to a number of InfoCubes. This is done by the job CCMS_ASR_AGGR_DATA_UPDATE, which runs once an hour.
There are two InfoCubes with identical structures (twin Cubes) for each time resolution of the statistics data. The data is iitially written to the first InfoCube in each case, until the end of retention period for the relevant resolution, as specified in the IT Performance Reporting setup. 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.
Note
The IT Performance Reporting setup is described in the Implementation Guide for the SAP Solution Manager under Scenario-Specific Settings System Monitoring Reporting .
For each of the six resolutions listed above, there are two InfoCubes for each InfoArea. The technical names of these InfoCubes follow the naming convention 0CCM<InfoArea abbreviation><resolution suffix><1|2>. In detail:
Resolution |
Suffix |
Example (Response Time Distribution) |
|---|---|---|
Hourly data |
DH1, DH2 |
|
Daily data |
DD1, DD2 |
|
Weekly data |
WD1, WD2 |
|
Monthly data |
MD1, MD2 |
|
Weekly data with hourly resolution |
WH1, WH2 |
|
Monthly data with hourly resolution |
WD1, WD2 |
Since it is undetermined at any particular time which of the twin cubes contains the desired statistics data, use the relevant MultiCube in each case for your own queries or Web templates. For each of the resolutions listed, there is a MultiCube with the naming convention 0CCM<InfoArea abbreviation><resolution suffix>, and there is also another MultiCube for each InfoArea that contains the data for all available resolutions (naming convention 0CCM<InfoArea abbreviation>). In detail: