OLAP Trace Tool (Old) 

Purpose

The OLAP trace tool allows data to be listed that is passed on to the BI system when actions are performed in the front end. You can also trace values for variables. The OLAP log book (Trace) is stored in the BI system.

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

The log, created when an OLAP trace is created in the front-end system (SAPBEX.trc), is of little use.

Implementation Considerations

Note the following:

...

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

       2.      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 performing the following actions:

-         Changing the hierarchy

-         Changing restrictions

-         Adding or removing characteristics and key figures

-         Loading data (the trace finds nothing if there is suddenly no data available for a navigation step that was traced).

       3.      When using the OLAP trace tool to assist SAP Support in investigating a customer 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 access the OLAP trace tool from the SAP Easy Access screen, from Business Explorer → BEx Monitor → Trace Tool.

For more information about listing an OLAP trace, see Creating 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.

All Users

The system enters the entry ALLUSERS in the list. All users are now logged. However, those users that were already activated retain their own configuration.

 Deactivate User

The user selected in the table is deleted from the list. This user’s actions are no longer logged.

Configure User

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

User Logs

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

CATT Logs

All Logs

The Processing/Deletion of Logged Calls screen appears. The system displays all OLAP traces logged in the BI system.

Navigating Within Logs

The Processing/Deletion of Logged Calls screen is displayed. Each entry in the list contains the following entries for each log:

●     System

●     Log Number

●     Users

●     Date

●     Time

●     Description (if necessary)

Delete the logs you no longer need. The system restricts the number of logs. When the maximum number is reached, the system overwrites the oldest logs.

Double-clicking on a log takes you to the “Call 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 indicated by “X”, “XX” and so on, in this column.)

●     Function module

●     Parameter (for function module)

●     InfoCubes

●     Report name

●     CPU time (µs) (required by the trace).

You get back to the Set Trace Configuration screen using 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 (0. nesting depth). If a traced module with subrc <>0 is exited, a breakpoint is inserted here.

The logs can also be executed by remote login.