Trace Tool Environment
A trace is a self-contained quantity of logged user actions. The trace tool environment (transaction code RSTT) has special tools to log and playback traces (Trace Tool) as well as to process automatic regression tests (Computer Aided Test Tool).

The trace tool
environment replaces the OLAP trace tool (transaction codes RSRTRACE, see
OLAP Trace Tool
(Old), and RSRCATTTRACE) and provides all of the functions necessary for a
clearly enhanced 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 (see Administration).
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. Note that 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 also closes the trace.
For more information, see Logging User Actions.
The display of a trace 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 branch to the ABAP Debugger directly at this location. The latter option is recommended for a detailed analysis of the recorded processing (for example, for an error analysis).
For more information, see Execute Logged User Actions Again.
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 once 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 restricted according to 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 respective application area, use the trace tool environment in conjunction with various tools from the BI system.

In the Reporting, Planning and OLAP Technology application area, use the trace tool together with query execution.
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 |
Administration |
● Determining global settings for trace tool environment |
See also:
