Select language:

BW Statistics

Architecture

BW statistics allow you to record runtime data for BW processes and events in SAP BEx, Analytic Engine and in the Data Warehouse. The system records performance-intensive processing steps (known as statistics events). It calculates the net times by calculating the runtime of an event using the difference between the start and end times (minus the times for other events called from within the event). You can also use the statistics to record the monitoring status of BW objects from the Data Warehouse.

Technical BI Content provides you with predefined BW objects for analyzing statistical data.

The BW Administration Cockpit provides you with a central point of entry for monitoring the performance of BW systems in your system landscape. Based on the technical BI Content, this allows you to analyze runtime and status for BW objects and processes in the SAP NetWeaver Portal or using SAP BusinessObjects Dashboards.

The graphic below illustrates the architecture of BW Administration Cockpit. The interaction between BW statistics, technical BI Content, and BW Administration Cockpit is based on this architecture:

Recording BW Statistics

BW statistics are recorded for the following areas:

  • BEx query runtimes (actions on the front end and in the Analytic Engine, including BW Integrated Planning)

    In Data Warehousing Workbench, you can specify which objects the system records statistics for by choosing Tools → BW Statistics Settings.

  • Runtimes of subprocesses in SAP HANA/SAP NetWeaver BWA index maintenance

    In Data Warehousing Workbench, you can specify which objects the system records statistics for by choosing Start of the navigation path Tools Next navigation step BW Statistics Settings End of the navigation path.

  • Runtimes of subprocesses of analytic indexes
  • Runtimes and status of data transfer and data processing in the Data Warehouse

    The system always records statistics on the runtimes and status of data transfer and data processing in the Data Warehouse. This is not the case for statistics for the data transfer process. These are deactivated in the default setting and can be activated in table RSDDSTATOBJLEVEL. More information: SAP Note 966964.

  • Runtimes for performing planning functions

Depending on the area, the system writes the statistics recordings to tables RSDDSTAT* or UPC_STATISTIC*. For statistical analyses in Data Warehouse processes, tables RSMDATASTATE, RSMDATASTATE_EXT, RSDDSTATDTP, RSBKREQUEST, RSBSOURCEPROP, RSPCLOGCHAIN and RSPCPROCESSLOG are used too.

Analyzing BW Statistics

You have a number of options for analyzing statistics data. These options are illustrated in the following graphic and described below:

Analysis Using the Tables or Views

You can analyze the tables and views directly in the data browser (transaction SE16).

Analysis of query runtime statistics is simplified using views RSDDSTAT_OLAP and RSSDDSTAT_DM.

When analyzing the runtimes and status for the load and maintenance processes in Data Warehouse, tables RSDDSTATWHM and RSDDSTATDTP are particularly relevant.

Runtimes of subprocesses in SAP NetWeaver BWA index maintenance are analyzed in table RSDDSTATTREX.

The runtimes of subprocesses of analytic indexes are analyzed in the RSL_STAT table.

Runtimes of planning functions are analyzed in UPC_STATISTIC* tables.

Analysis Using Technical BI Content for BW Statistics

Technical BI Content provides predefined BW objects for analyzing most statistics data.

The data is stored in the relevant InfoProviders. Queries and Web templates enable flexible analysis and differentiated display of information, for example using charts, table or graphics. While analyzing the statistics data using the technical BI Content provided is mandatory, you can define your own queries and Web templates to run analyses with. You can therefore take content from standard Web templates and combine it to make your own Web template. In the BW system, you can run technical content queries using Query Monitor (transaction RSRT).

Before using technical BI Content, you have to activate it. For more information, call Customizing and choose SAP NetWeaver → Business Warehouse → General BW Settings → Settings for the Administration Cockpit.

Analysis (Technical Content) Using the Workload Monitor (ST03)

The workload monitor contains the function BW System Load, which you can use to analyze statistics data. The analysis is based on the technical content.

Analysis (Technical Content) Using BW Administration Cockpit

BW Administration Cockpit provides you with a single point of entry for monitoring the performance of BW systems. You can perform system monitoring in the SAP NetWeaver Portal or using SAP BusinessObjects Dashboards (Xcelsius).

BW Administration Cockpit is based on technical BI Content for runtime and status data for BW objects and activities. You can navigate from BW Administration Cockpit to the corresponding BW systems, transactions or queries in order to analyze system performance or to solve problems.

The following prerequisites apply for using BW Administration Cockpit:

  • You have activated the technical content.
  • You have installed Business Package BW Administration 3.0.
  • You have made the other settings required in Customizing.

    For more information, call Customizing and choose SAP NetWeaver → Business Warehouse → General BW Settings → Settings for the Administration Cockpit.

  • You are connected to SAP BusinessObjects Dashboards using the BICS connection.
    Note

    As explained under Analysis Using Technical BI Content for BW Statistics, you can also use the InfoProviders, queries and Web templates used in BW Administration Cockpit without the portal, thus combining the standard Web templates into a Web template of your own.

Ad Hoc Analysis of Query Runtime Statistics in the Query Monitor (Transaction RSRT1)

Using the statistics data in the query monitor, you can perform an ad hoc analysis at query runtime.

  1. Select a query and choose Execute + Debug. The Debug Options dialog box appears.
  2. Select the flag for debug option Display Statistics Data and run the query.
  3. When the query is run and is displayed with the various navigation steps, press F3 (Back).

    The Statistic Data for Query Runtime screen appears. The data for the area for the front end and calculation layer of the analytic engine (Front End/Calculation Layer), and the data for the area for the aggregation layer of the analytic engine are displayed on two separate tab pages.

More information:query monitor

Ad Hoc Analysis of Web Template Runtime Statistics

You can display runtime statistics for Web applications by using URL parameter &PROFILING=X in the start URL of a Web application.

Note

We only recommend using this setting if performance problems arise for a particular Web template.

More information: Displaying BEx Query Runtime Statistics on the Web

Direct Access to Statistics Tables Using Technical Content

As well as analysis scenarios based on persistently stored data, you can also access statistics data directly.

With persistent data storage, the statistics data is extracted from the tables in scheduled processes and stored in the relevant InfoProviders. If you want to analyze the data in real time, you can use the VirtualProvider tool in the technical BI content to read the data in the tables directly from the query or Web application.

Taking query runtime statistics as an example, the graphic below illustrates how you can use a MultiProvider to read periodically loaded delta data (recommendation: daily) from the InfoCube and to read delta data that has not been loaded yet directly from the statistics tables using a VirtualProvider.

Deleting Statistics Recordings

Query runtime statistics generate a very large amount of statistics data in the BW statistics tables Depending on the (user-defined) delta statistics level, between 20 and 80 data records are written to the BW statistics tables for each single navigation step. We therefore recommend loading the statistics data into the technical content and deleting the original data from BW statistics tables RSSDDSTAT* and UPC_STATISTIC* on a regular basis.

When using technical content, deletion of statistics recording for query runtime statistics is automated. For more information about this and about manually deleting data from RSDDSTAT tables, see Maintenance of Statistics Properties.

In transaction BPS_STAT0, you can delete statistics data from the UPC_STATISTIC* tables. You can enter a date for deletion of table entries. The system then deletes all entries whose recording date is earlier than the date you entered.