OLAP Trace Tool (SAP Library - Performance Optimization)

OLAP Trace Tool

Purpose

The OLAP Trace tool allows you to trace data transferred to the BW system as a result of actions made in the frontend. You can also trace values for variables. The OLAP trace is stored in the BW system.

You can use the OLAP trace to reproduce activities in the frontend. The OLAP trace tool is particularly useful when testing and when examining frontend activities involving SAP support.

The log itself, created when an OLAP trace is created in the frontend system, is of little use.

Implementation Considerations

Note the following:

Keep the trace as short as possible. It may be useful to log the problem with several traces.

The trace is no longer valid once the query for which the trace was set is changed. In particular, the trace loses its validity when carrying out the following actions:

Changing the hierarchy
Changing restrictions
Adding or removing characteristics and key figures
Reading data (The trace finds nothing if the data for a navigation step that was traced is all of a sudden no longer there).

When using the OLAP trace tool to assist SAP Support in investigating a problem, you also need to make sure that the test user you make available to SAP Support has the necessary authorizations.

Authorization for executing the query with all navigation steps and data requests.
Authorization for the OLAP trace tool (RSRTRACE or RSRCATTTRACE)

Integration

As of BW 3.0A SP11 = BW 3.0B SP04, you can reach the OLAP trace tool from the SAP Easy Access screen, from Business Explorer ® BEx Monitor ® Trace Tool.

Further information about setting an OLAP trace can be found under Setting an OLAP Trace.

Features

The following functions are available in the OLAP trace tool toolbar:

Activate User

The user from the User field is added to the list. This user’s actions are logged.

Note

All users

The system puts the entry ALLUSERS into the list. All users are now logged. Those users that were already activated retain their own configuration however.

Deactivate User

The user selected in the table is deleted from the list. This user’s actions are not logged any more.

Configure User

You get to the Set Trace Configuration screen. Enter a standard description for the active log process. You can also choose topic areas and individual routines that you should look at in greater detail. You can also activate the Detailed Runtime Analysis.

User Logs

The Processing/Deletion of Logged Callups screen appears. The system displays the logs that belong to the current user.

CATT Logs

All Logs

The Processing/Deletion of Logged Callups screen appears. The system displays all OLAP traces set in the BW system.

Navigating within Logs

You are in the Processing/Deletion of Logged Callups screen. Each entry in the list contains the following entries for each log:

System
Log No.
User
Date
Time
Description (If necessary)

Caution

Delete the logs you no longer need. The number of logs is restricted by the system. When the maximum number is reached, the system starts to delete the oldest logs.

Double-clicking on a log takes you to the "Call up tree" Each entry in the list can contain entries for the following characteristics for the log considered in greater detail:

SUB (The nesting depth is displayed with an "X" or "XX" in this column).
Function module
Parameter (for function module)
InfoCube
Report name
CPU time (µs) (required by the trace).

Note

You get back to the Set Trace Configuration screen via Configuration. You can enter a description of the current log here.

Double-clicking on a row takes you to the ABAP Debugger. The log is executed up until the function module is called up (0 nesting depth). If a module with subrc <>0 that was also described is to be exited, a breakpoint is inserted here.

Note

The logs can also be executed via remote login.