Start of Content Area

Background documentation Data Flow  Locate the document in its SAP Library structure

When transferring data from the Central Performance History (CPH) to the Business Warehouse, a central monitoring system with a release status of SAP Web AS 6.40 SP 1 or above acts as the data source. This system contains the monitoring architecture and the CPH. The monitoring data itself originally comes from satellite systems that are defined as monitored systems in the monitoring architecture.

The connection to the Business Warehouse is created by the PI BASIS Plug-In as of 2004.1 6.40. This contains the extraction function modules and an infrastructure for delta management and for generic data transfer to the BW system.

In the BW system (BI Content as of 3.52 Add-On), there is, finally, a range of data containers for the monitoring data. Queries for creating reports are defined in relation to these data containers.

This graphic is explained in the accompanying text

Structure of the InfoCubes

Queries for CPH data in the Business Warehouse first use the MultiCube 0CPH_ALL, which contains all of the CPH performance data available in the Business Warehouse. In turn, this VirtualCube contains the following InfoCubes:

·        InfoCubes of the CPH data that is stored in the Business Warehouse, separated by resolutions. This distribution of the performance values to different InfoCubes achieves a better performance when requesting data in the Business Warehouse. It is usually the case that only data in one resolution is requested during the course of a query, meaning that less data must therefore be read. In detail, these are the InfoCubes:

¡        CPH Minute Performance Values

¡        CPH 15 Minute Performance Values

¡        CPH Hour Performance Values

¡        CPH Day Performance Values

·        The InfoCube CPH Online Data, which allows you to access performance data in the Business Warehouse that is not yet stored in the BW. This is usually data for the current day. The data includes all resolutions.

This graphic is explained in the accompanying text

Data Flow for a Request Due to a Query

If a query is performed in the Business Warehouse, the system automatically performs the following steps, depending on where the requested performance values are already available:

...

       1.      If the requested data is already available in the Business Warehouse, this data is used to respond to the request.

       2.      If the data is not yet available in the Business Warehouse (we recommend that the job that transfers the data runs once a day; see CCMS: Creating InfoPackages and Process Chains), the request is forwarded directly to the CPH. If the requested data is available in the CPH, this data is used to respond to the request.

       3.      If the data is not yet available in the CPH (there are jobs for transferring data for which the periods are between 13 minutes and 10 hours, depending on the requested resolution; see Collecting and Reorganizing Performance Values), the data is transferred directly from the monitored satellite systems.

 

Reorganizing the Performance Data in the Business Warehouse

Both the data in the CPH and the corresponding data in the Business Warehouse must be regularly reorganized, so that the quantity of data does not exceed all limits in the long term.

The ODS Object for CPH Reorganization Data exists so that the retention period is defined for every data record that was transferred from the CPH to the BW. The ABAP program CCMSBI_CPHDATA_REORG should be called by process chain every time that reorganization data from the CPH is reported in this ODS object (see CCMS: Creating InfoPackages and Process Chains). This program reorganizes the performance data for the following objects:

·        InfoCubes for minutes, 15 minutes, hours, and day values (see above)

·        ODS Object for CPH Data

·        ODS Object for Time-Dependent Master Data of MTEs

This graphic is explained in the accompanying text Monitoring Performance Data start page

 

End of Content Area