Reexecution of Logged User Actions 

Use

In the trace tool environment, you can replay the program objects recorded in a trace, using the same transfer parameters that were saved in the system during recording.

You can use this function to inform an employee working in support about an error.

Furthermore, you can also use playing a trace for regression tests: This compares current test data with reference data that has been saved and verified as correct in order to check the correctness of the software (see CAT Tool).

Prerequisites

●      You have logged the required user actions (see Logging User Actions).

●      You have determined the required trace (see Determining a Logged Trace).

●      You have the required authorization to use the ABAP Debugger.

Features

The trace tool supports different process flows when executing a trace:

●      You can directly execute a trace. This option is suitable for regression tests, for example.

●      You can cause the play of the trace to be interrupted before particular program objects. This option is particularly useful if you want to analyze errors. The ABAP Debugger appears directly before the selected program object is called.

Since the trace tool only plays those program objects that belong to the application layer that is currently chosen, you can only select to play these objects.

On the Execution of Traces screen, the system in the Trace screen area shows the standard information for the trace (Trace GUID, Trace(ID), Description).

In the Process screen area you can select a Process Mode. This specifies how the trace is to be handled when it is played:

●      The Play Mode (Play Trace) mode causes the trace to be played. For standard traces, this is the only possible selection.

●      The Check Mode (Test Trace) mode starts the regression test. This mode is only available for CATT traces.

The following tab pages are displayed in the lower screen area:

●      On the Display Settings tab page, you can set the display mode. You can choose:

○       Debugging at Call Position: The system interrupts the execution of a trace at a recorded program object.

○       Debugging at Check Position: The system interrupts the execution of a trace at a checked program object.

●      On the Play Settings tab page, you can select from trace-type-dependent settings that influence the execution of a trace.

For traces from the application area Reporting, Planning and OLAP Technology, the following settings are made:

●        Read Mode: Read All, Read During Navigation, Read During Hierarchy/Navigation. More information: Read Mode

●        Cache Mode: Without Cache, With Cache (Initial), With Cache (Filled). For more information, see Cache Mode.

●        Aggregation Mode: Without Aggregate, With ROLAP Aggregates, with BI Accelerator Index. For more information, see Performance Optimization with SAP NetWeaver BI Accelerator and Performance Optimization with Aggregates.

Use   Execute to start the execution of a trace. The system documents the process flow step by step, using corresponding messages. The messages are displayed in a window in the lower screen area.

Activities

...

       1.      You can play a trace from the Trace or Trace Collection areas of the Trace Tool functional area. Follow these steps:

                            a.      In the navigation window, from the Trace Tool functional area, you can choose the Traces area. This allows you either to enter the name of the trace to be played in the Trace (ID) field, to select it from the input help, or to select it from the appropriate line in the History of Last Traces table to transfer it.

                            b.      In the navigation window, from the Trace Tool functional area, you can choose the Trace Collection area. This allows you to display a selection of traces that are restricted by user, application layer, and trace type. When you have specified the selection criteria, press the enter key. The system displays the traces that correspond to the selection criteria. Select the required trace.

       2.      The Execution of Traces screen appears in the following ways:

                            a.      Choosing  Execute takes you directly to the Execution of Traces screen.

                            b.      Choosing  Display or  Change takes you to the Trace Attributes screen that is used for the maintenance of a trace. Choosing  Execute takes you directly to the Execution of Traces screen.

Determine the settings for executing a trace that are described in the features section.

       3.      To execute the chosen trace, you have the following options:

                            a.      On the Execution of Traces screen, play the entire trace by choosing  Execute.

                            b.      Alternatively, on the Trace Attributes screen, on the Logged Program Objects tab page you can execute the trace directly by selecting a row in the table. The system interrupts the process flow at the program object in the selected row.