Show TOC

Trace Tool EnvironmentLocate this document in the navigation structure


A trace is a self-contained quantity of logged user actions. The trace tool environment (transaction RSTT) has special tools to log and play back traces (trace tool) and to process automatic regression tests (computer aided test tool).

Application area

The application area encompasses a particular part of the BI system where user actions can be logged. Assigning to a particular application area is user-dependent (seeAdministration).

Logging and Playing Back Traces

It is useful to log a trace in the following cases:

  • to conserve and analyze errors and questionable process flows
  • to repeatedly execute selected navigation sequences (such as query navigations)

Users who want to record a trace must be activated before recording starts recording and be deactivated again after recording. The lifetime of a trace depends on the lifetime of the session of the processes to be recorded. As soon as a session is ended, the system closes the trace too.

More information:Logging User Actions.

How traces are displayed depends on the controlled execution of the recorded sequence of program calls. A user can either execute the trace completely or stop execution at a given location, in order to call the ABAP Debugger directly. The latter option is recommended for detailed analysis of the recorded processing (for troubleshooting for example).

More information:Reexecution of Logged User Actions.

Processing of Automatic Regression Tests

With automatic regression tests, you can monitor the quality of the system over a longer period of time (for example during the cycle of a support package).

A wizard helps you to create automatic tests (called CATT traces). Users are guided through the individual definition steps: They make decisions regarding the storage of the test reference data and the assignments for the data structures to be tested, and store descriptions of the navigation steps.

When the tests are executed, the CATT traces are executed internally, and the current results are compared with the test reference data stored in the definition. If the traces are displayed successfully and the current results values agree with those of the test reference data, the test was successful. In all other cases, the test was not successful. The system provides a user interface for displaying the tested data contents.

To combine a larger number of CATT traces, test packages can be generated that can be refined using certain selection criteria. Test packages can be scheduled as repeatable test jobs for background processing. The system stores logs relating to the state of the test run in log files (job log and application log). The system writes the results of the tests directly to InfoObjects or InfoProviders as master data or transaction data and immediately makes them available for reporting.


Depending on the application area that you are working in, you can use the trace tool environment in conjunction with various tools from the BW system.


In Reporting, Planning and OLAP Technology, you use the trace tool when executing queries.


The trace tool environment allows you to work with traces, test packages and test jobs. It includes the following functions:

  • Activating or deactivating users for logging traces
  • Analyzing, editing or deleting traces
  • Playing traces
  • Using traces as a CATT trace
  • Logging reference data
  • Performing regression tests
  • Creating, editing or deleting test packages
  • Creating, editing or deleting test jobs

You access the interfaces of the individual task areas using the navigation window. These are assigned to the following areas:

Functional areas for the trace tool environment

Area Use

Trace Tool

  • General user activation
  • Managing traces
  • Collectively displaying multiple traces

CAT tool (Computer Aided Test Tool)

  • Managing CATT traces, test packages and test jobs


  • Specifying global settings for trace tool environment

See also:

Trace Tool

CAT Tool