Show TOC

Configuring Statistics PropertiesLocate this document in the navigation structure


When working with BEx query runtime statistics, the system can collect data for the following types of BW objects:

  • BEx Query
  • BEx Web template
  • BEx workbook
  • InfoProvider (with restrictions)

On the Maintenance of Statistics Properties screen (transaction RSDDSTAT), you can edit the statistics properties for individual objects as well as the default settings for the object types listed above.


Configuring the statistics properties of a BEx Web template or a BEx workbook only affects the creation of the corresponding front end runtimes. Conversely, configuring the statistics properties for queries (or InfoProviders) only affects runtimes in the analytic manager and in the data manager. A complete recording of the runtime data manager - analytic manager - front end) is therefore only guaranteed if the statistics properties are configured for the relevant query and front end objects.

Note that the system records a large amount of detailed runtime data as part of the BEx query runtime statistics. Recording the runtime of a navigation step for a query generates an average of 20-80 records, depending on the level of detail of the statistics. Deactivate the detailed runtime recording for all objects that performance analyses are not needed for.


From the Data Warehousing Workbench screen, you can navigate to the maintenance screen for the statistics properties by choosing Tools → Settings for BW Statistics.


Changing Statistics Properties

The various objects are located on the corresponding tab pages. You can use the sorting and filter functions for the table to preselect the objects to be changed.

  1. Select the objects you want to change.
  2. Select the required settings using the Settings selection list for the object. You can choose whether the statistics are to be switched on or off, or you can choose the default setting (D) for the object type. For queries, you can also specify the detail level for the statistics.
  3. To apply the settings to the list, choose Replace Values. The system sets the relevant flag in the Last Changed column.
  4. Choose .

Default Setting for Object Types

Every new object initially has the default setting for its object type as the statistics property.

To change this setting, choose Extras → Change Default. The dialog box with the current default settings for the object type appears. You can change the default values here. All objects of this type with "D" in the Statistics On/Off column are then treated according to the new default setting when statistics are recorded.

An exception to this rule is the Query object type. If no specific statistics property is set for a query, that is, the default value "D" is set, the system first determines the statistics property for the InfoProvider of the query. If the InfoProvider has "D" as the statistics property, the system reverts to the default setting for the query. Otherwise, it uses the InfoProvider setting (with the OLAP detail level from the InfoProvider setting).


A new query is created. It has the statistics setting "D". The default setting for the query is Statistics Off. The InfoProvider for the query explicitly has the setting Statistics On (not as default setting) however. The system then records statistics data for the query.


This derivation relates only to the InfoProvider that the query is directly based on. If this involves a MultiProvider, no additional derivation is made of the possible settings from the InfoProviders contained in the MultiProvider.

Statistics Detail Level for the Query Object Type

For queries, you also have the option of selecting a detail level for the statistics data. You can choose from the following:

  • 0 - Aggregated Data: The system aggregates all OLAP events (apart from events 3010 and 3100 that are needed to calculate the query counter) for the query in event 99999. This contains all times (cumulated) in the OLAP processing for this query. The system does not record data from the aggregation layer of the analytic manager.
  • 1 - Only Front End/Calculation Layer Data: The system records all OLAP events, but not separate data from the aggregation layer of the analytic manager. The system writes only the general data manager event 9000 in the OLAP context as well as the aggregation information.
  • 2 - All: The system records all data from the area for the front end and calculation layer as well as data from the area for the aggregation layer and aggregation information.
  • 9 - No Data: The system does not record any data from the front end and calculation layer, or even from the aggregated event 99999. However, it does record data for the BEx Web templates and workbooks, depending on the setting.

    When selecting the detail level, bear in mind that a very large amount of data is recorded when the system records data manager times.


    A Web template with four queries is executed. Each query is based on a MultiProvider containing 10 InfoProviders, each of which has data in the E table and F table. Due to specific query properties, the query is split into two parts. Each part is based on a different aggregate.

    The results are as follows: 4 queries * 10 InfoProviders * 2 parts * 2 table types = 160 records in the RSDDSTAT_DM table view (plus the records from the area for the front end and calculation layer of the analytic manager in the RSDDSTAT_OLAP table view).

InfoProvider Tab Page

In addition to the default setting described for queries of an InfoProvider, you can also change the following statistics properties for an InfoProvider:

  • Statistics data for aggregate processes (fill, roll up, change run, condense): You can switch the recording on or off.

    The recorded data is stored in table RSDDSTATAGGR.

  • Data from the aggregation layer for the external BW read interface (RSDRI): You can switch the recording on or off.

    Since queries through the external read interface do not run through the OLAP processor, for this type of request, the system records only the event 9001 (External Read Interface) with the handle type EXTN in the area for front end and calculation layer. Processing in the area for the aggregation layer does not differ from a "normal" BEx query. The relevant statistics can therefore be recorded for this.


    For InfoProviders, the statistics detail level relates to the default setting for the queries of the InfoProvider only, and not to the processes listed above.

Deleting Statistics Data

BW statistics, especially query runtime statistics, create a large amount of statistics data in the BW statistics tables We recommend loading the query statistics data in the technical content (InfoCube 0TCT_C01 - 0TCT_C03), as using the technical content for the query statistics tables causes automatic deletion and regular deletion of data from the BW statistics tables.

Deleting Statistics Data Automatically

In the standard setting, data for BEx query runtime statistics is deleted every time a delta for the query runtime statistics is loaded into the technical content. For DataSources 0TCT_DS01, 0TCT_DS02 and 0TCT_DS03 all data from the underlying statistics tables that are over 14 days old is deleted automatically. This value can be changed for specific customers using parameter TCT_KEEP_OLAP_DM_DATA_N_DAYS in table RSADMIN.


See SAP Note 891740.

Deleting Statistics Data Manually

If you choose Delete Statistical Data, a dialog box appears. Here, you can select the areas where you want to delete statistics data. You can select multiple areas.

You can delete all data or just a part of it. You can also define how old the statistics data to be deleted should be. You can delete data that is over one day old, over a week old or that is over 30 days old. Alternatively, you can enter a date of your choosing.

If you decide to delete all data, this will be executed using command TRUNCATE TABLE, and not using selective deletion in the database. This version is therefore considerably faster.

If an Up To time is specified to data that is older than a given time period, references to a number of tables might need to be resolved. This means it can take some time to delete large amounts of data. With these restrictions, however, packages of just 1000 records are deleted from the tables. This is followed by a database commit. This makes it possible to restart after a termination (from a TIMEOUT, for example), without having to redo previous work.

The deletion is performed in a dialog process.

You can also schedule deletion of statistics data using program RSDDSTAT_DATA_DELETE and run the deletion in the background. You can also use this program to delete data from the areas mentioned above, from the data transfer process and warehouse management statistics tables (RSDDSTATDTP and RSDDSTATWHM) and from the counter table for BWA usage for each InfoProvider (RSDDSTATBIAUSE).