Statement Hit List 

To display a hit list of all of the statements measured within a transaction, program, or function module, choose Goto ® Hit list ® Standard. The hit list displays all measurable ABAP statements in descending order of gross time. If the gross and net times are identical, the system only displays the net time. The values in the No. field indicate how often each statement was executed.

 

The list is sorted by gross time, and contains the absolute values in microseconds. However, you can display the net times by choosing Gross <-> Net. If you want to display the runtimes as percentages instead of absolute times, choose
Absolute <-> %.

The way and order in which the fields in the hit list are displayed depends on whether the measurement restrictions specify aggregation.

 

The Type column shows the category to which the individual statements belong:

Value in "Type" column

Category

" "

ABAP statements

DB

Database statements

Syst

System statements

 

To switch to the source code of the program at the point where a statement occurs, position the cursor on the statement and choose Display source code.

Hierarchies

A call can itself call further functions. From the hit list hierarchy, you can see the sequence in which the measured statements are executed. From the hit list, you can display the hierarchy by double-clicking the relevant line. The system can only display the hierarchy if you did not use aggregation in the measurement.

For example, a program can call a subroutine. This statement can itself contain further calls. The system displays the hierarchy of the calls contained in the subroutine on the Hierarchy screen:

Each hierarchy can contain further hierarchies. The runtime analysis tool allows you to display the relevant subhierarchies for each call.

If the gross and net times for a call are different, the call contains one or more subhierarchies. In the graphic, the subroutine CREATE_SIMPLE_TREE has a gross time of 841.390 microseconds, but a net time of 108 microseconds. The subhierarchy display for the call shows that the subroutine call itself only required 108 microseconds.

You can display a subanalysis for this call by double-clicking a line in the hierarchy.