Start of Content Area

Function documentationSystem Trace  Locate the document in its SAP Library structure


If you want to record the internal SAP system activities, use the function SAP System Trace. Recording the processes in your application server enables you to monitor the system and facilitates troubleshooting.


The system trace is primarily used when an authorization trace is to be used. The System Log or the Developer Trace are recommended for system monitoring and problem analysis.


The following components can be monitored using the SAP system trace:

        Authorization checks

        Kernel functions

        Kernel module

        Database accesses (SQL trace)

        Table buffer

        RFC calls

        Lock operations (client side)

The last 4 components can also be monitored using Performance Analysis (transaction ST05). For documentation on this, see Performance Trace Overview.

There are two ways of selecting what traces you want displayed. In the initial screen, select the components to be logged, and additional filters, if required. You can reuse the filters and restrictions from the traces that have these settings when the traces are evaluated.

Initial Screen

The initial screen of the system trace looks like this:

This graphic is explained in the accompanying text

Activating and Deactivating Traces

First configure the trace components. If necessary, restrict the selection using the pushbutton General filter, and then choose This graphic is explained in the accompanying text Trace on. You can also change the components while the trace is activate by choosing Change trace.

You can use both Settings buttons to save your settings and call them up again later.

You can use the Save button (or Go To Save in the menu) to save trace records in dedicated files. You are presented with a screen on which you can create a remark for the trace file and select whether this should be created automatically or whether a file has to be created for this purpose. The use of explicit files is described in greater detail below.

Options for Trace Analysis

If you choose Evaluation, a screen opens on which you can make various evaluation settings.

This graphic is explained in the accompanying text

Here you can set various evaluation options.

Besides determining the trace components, you can restrict the analysis to particular users, work processes, transactions, and times.

For performance analysis, you can use the field Duration to analyze only records for which the duration of a trace record exceeds a specific period of time. This also applies to trace components that have a duration. This setting does not apply to the authorization trace.

You can also set a restriction that only specific tables are included in the trace analysis (this also applies to the SQL and the table buffer trace). You can enter two table names directly on the screen; you can add other tables using the button of the same name. The button changes color if there are more than two tables in the list.

In the lower part of the screen, you can specify a separate filer to protect a trace from being automatically overwritten. If you specify a separate file here, the “normal” trace files are ignored and the specified file is used.

Besides the This graphic is explained in the accompanying text button, there are 3 more buttons:

This graphic is explained in the accompanying text Filter History

This shows you that last 10 filter settings of the user in question.

This graphic is explained in the accompanying text Use Default Values

The filter gets the following default values: own user, own client, from 10 minutes ago (rounded off) until now, all trace types, not tables D010* and D020*.

This graphic is explained in the accompanying text Delete All Field Values

This button deletes the values in all fields.

The menu Filter Settings also contains all these functions.

Once you are finished making the settings for the analysis criteria, choose This graphic is explained in the accompanying text to display the results of the analysis.

Interpreting the Analysis

Information in trace entries includes the following:

        Time(to the millisecond). Double-click to see the time to the microsecond.

        Type of the trace entry, that is, the component selected when the trace was activated or when the analysis settings were made.




Authorization check


Authorization object used

Kernel functions


Corresponding C function in kernel

General kernel


C module in the kernel in which the trace is written

Database accesses (SQL trace)


Database table being accessed

Table buffer trace


Database table being accessed

RFC calls


Called function module

Lock operations


Lock object used

        Duration of the trace, provided this is useful. In the case of an authorization trace, a user trace (free text that can be written by a kernel module), and the beginning of a C function in CMOD trace, a duration is not useful and therefore not required.

        Object: the object is different, depending on the trace component, and can be obtained from the table above.

        Trace message text

Double-click on a line to get additional detailed information on this trace record.

Protecting Trace Information from Being Overwritten

If you want to protext a trace from being overwritten later, choose the Save button on the initial screen, or choose Go To Save from the menu.

On the next screen, you can create a short text for a trace, and choose whether the new file that is created specifically for this trace should be automatically created, or whether you want to specify a file. If you do not specify an absolute path, a file of this name is created in the log directory. In the case of automatic file creation, the system determines the filename and stores the file in the log directory. The advantage of this is that, unlike a manually created file, the F4 help can be used for to search for the file from the analysis screen.


If you choose automatic creation, you can delete the file again in this transaction (use the This graphic is explained in the accompanying text button in the analysis screen). This is not possible if you specify a filename. If you want to delete this kind of file, you have to do so at the operating system level.

See also:

Further trace functions include:

System Trace: Administration

System Trace: Relevant Profile Parameters

System Trace: Error Analysis


Enter transaction code ST01. Alternatively, choose Administration System administration Monitor Traces SAP System Trace.



End of Content Area