Show TOC

Background documentationPassing ABAP Statistics Data to the Business Warehouse


Note Note

This section is part of the technical documentation of the ABAP statistics data reporting scenario. It is the continuation of the section Getting the ABAP Statistics Data for Reporting Applications

End of the note.

When the ABAP statistics data has been obtained, the extractor framework forwards it to the Business Warehouse for long-term storage.

A data loader passes the data to BW. This function module is called in the Business Warehouse system. The data loader in the reporting scenario is ASRSTAT_BI_DATALOADER. It is called after the primary extractor by the secondary extractors E2E_LUW_ECL_<Profil> from the SAP Solution Manager system. The data loader writes the values obtained by the primary extractors into BW.

The data loader is called via the default RFC connection to the BW system.

You specify this connection in the SAP Solution Manager Configuration (transaction SOLMAN_SETUP) in Start of the navigation path Basis Configuration Next navigation step Automatic Configuration End of the navigation path in the activity Create RFC Connection to BW. The default name of the destination is BI_CLNT<Mandant>, where <Mandant> is the client number of the BW system.

ABAP Statistics Data Flow in Business Warehouse

The data loader writes the data in various data store objects (DSOs) in BW. The data is then written from the DSOs into InfoCubes by jobs. Twin Cubes are used.

Twin Cubes are two InfoCubes with the same structure. The data is initially written to the first InfoCube, until the end of retention period for the resolution specified in the configuration. Data is then written to the second Cube, until the end of its retention period. The first cube is then deleted, and the cycle is repeated. A MultiProvider connects the two twin cubes.

Note Note

You specify the lifetime of the ABAP statistics data in BW depending on the time resolution, in the configuration of Technical Monitoring, in the transaction SOLMAN_SETUP. This is in the step Start of the navigation path Configure Infrastructure Next navigation step Periodic Tasks End of the navigation path, in the group box BI Data Lifetime for Each Granularity.

One advantage of this concept is to avoid the resource-intensive selective deletion of obsolete data records. The deletion of all data in an InfoCube when the active cube changes, is much quicker than the selective deletion of obsolete data records.

End of the note.

Queries and web templates use a MultiProvider over the twin cubes, because they do not know which of the twin cubes contains the desired data at a particular time.

For a detailed dewscription of the data flow, see Statistics Data Flow.