Evaluating the Trace


If you have created a trace you can evaluate it to analyze the behavior of the system during the recorded steps.


On the initial screen choose System Trace  Evaluation.

The following screen appears Trace Evaluation Options.

Setting Options

You can set various options for the evaluation.

·        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 applies only to trace components that have a duration. This setting should not be made for authorization traces.

·        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 by choosing Further Tables. The button changes color if there are more than two tables in the list.

·        In the group box File Selection, 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  button, there are 3 more buttons:

·         Filter History

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

·         Set 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*.

·         Delete All Field Values

This button deletes the values in all fields.

The menu Filter Settings also contains all these functions.

Once you have set the criteria for the evaluation, you can display the evaluation with   Start Evaluation.

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 detailed information on this trace record.