Analyzing Trace Records 

Prerequisites

You have displayed the trace records that you want to analyze in a basic or extended list.

Functions

Sorting the Lists

You can sort the list by any of the parameters in the list heading, that is, transaction name, process identification number, process type, client, and user name. To sort the list, position the cursor on the relevant column and choose Sort.

Switching Between Lists

To switch from the basic list to the extended list, choose Extended list. To return from the extended list to the basic list, choose Back.

Detailed Display and Replacing Placeholders

When the logged statement is formatted, you can specify whether to replace the placeholders in the statement by the current variables or leave them in the statement and list the variables separately. If there are no variables, the two display forms are identical. To display the statement, double-click its short form, or position the cursor on it and click the magnifying glass icon.

To replace the placeholders with the current variables, choose Var. replace.

Displaying Information about ABAP Dictionary Objects

To display ABAP Dictionary information for an object (table or lock object), position the cursor on the object and choose DDIC info. If the current statement contains more than one ABAP Dictionary object (for example, a join), the Object column contains the first object to appear in the statement.

 

If the log entry is an RFC entry, the column contains a shortened version of the name of the instance on which the function module was executed. In this case, you cannot display a ABAP Dictionary definition.

You can display further ABAP Dictionary information by opening the actual definition of the object within the ABAP Dictionary. For further information, see Finding Dictionary Information.

Execution Plan for SQL Statements

To display the execution plan of a selected SQL statement, place the cursor on the statement and choose Explain SQL. The SQL statements for which an execution plan can be displayed depends on the database system that you are using. The execution plan for a SELECT statement under Oracle looks like this:

Displaying the Source Code

To switch to the source code containing the current statement in the log, position the cursor on the short form display of the statement and choose ABAP Display.

Note that the source code cannot always be displayed. For example, if the call comes from the R/3 kernel, you cannot branch to the program code.

Identical Selects

When you are analyzing a trace log, it can be particularly useful to find out if there are any identical select statements. You can do this by choosing Identical selects. The system compiles a list of any SQL statements that are executed more than once. You can then eliminate any SQL statements that are not required.

Summarizing the Trace List

You can summarize the select statements by choosing Summary. This leaves you with an overview of the total runtime and the total number of records retrieved.