Understanding Parameters in Aggregated Call Tree and Call Sequence

Here you will find information on the trace parameters that are displayed in the Aggregated Call Tree and the Call Sequence:

Note With one exception, the parameters are identical in the Aggregated Call Tree and Call Sequence views:

The Executions column appears only in the Aggregated Call Tree.

Parameter	Description
Trace Event	A trace event is an ABAP statement or other operation (a database operation, for example) for which the ABAP Profiler records discrete performance data. Each individual trace event that has been recorded allows you to analyze the runtime consumption of the underlying ABAP statement or other operation. The ABAP Trace does not record all ABAP statements and operations as trace events, but only those that are potentially expensive in terms of resources. A CALL METHOD statement is recorded as a trace event. An IF statement is not. Though the ABAP Profiler does not record all ABAP statements and events, a trace nevertheless gives you a rich and detailed view of program performance and execution flow, especially since all procedure call statements are recorded. The trace events you see in a particular ABAP trace also depend on the Profiler settings that you selected before creating the ABAP trace. More on this: Understanding ABAP Profiler Settings Aggregation Options In the Aggregated Call Tree, the trace events are always aggregated for display according to their call stacks. The Aggregated Call Tree tool is available for non-aggregated trace files and for trace files that are aggregated by Call Stack. The Call Sequence tool is only available for non-aggregated trace files More on this: Aggregation Options in ABAP Traces.
Statement Filter	The Aggregated Call Tree and the Call Sequence view filter the trace display to highlight procedure calls such as `CALL METHOD` and `CALL FUNCTION`. Clicking on Show link in this field displays specified statements within the procedure call, such as data object creation, database calls, or use of an internal table, that were also recorded within the current procedure. These trace events are shown in contrasting colors. Remember The Hit List view for example, shows by all trace events, including the unspecified statements that the Aggregated Call Tree and the Call Sequence hide by default.
Executions	The number of executions of a trace event indicates whether this trace event shows aggregated runtimes or not. If you see the value 1 in Executions, then the trace event in not aggregated. The runtimes that you see then reflect a single execution of the statement or operation recorded in the trace entry. If you see a Executions of greater than 1, then that number of runs of the traced ABAP statement or operation are aggregated in the runtimes that you see. Executions with an Own Time, for example, of nine seconds means that each instance of the trace event ran for an average of three seconds. Note This column is available in Aggregated Call Tree only! In the Call Sequence view, the Executions counts the value 1 for each trace event recorded).
Total Time [µs]	This represents the amount of runtime in microseconds from the start to the finish of a particular trace event or set of aggregated trace events. The Total Time includes time spent waiting for other trace events started from the first trace event. In other words: it includes the runtime of external calls, as well as unspecified (intrinsic) and specified statements (for example: a `SELECT` statement that requires database calls) within the present trace event. Total Time lets you see the total contribution of the processing done within such tracing events. Example: A method M1 has a total runtime of six seconds. Five seconds of that time are spent waiting for method M2 to complete. Method M2 is called from method M1. The Total Time of method M1 is six seconds, including the run time of method M2.
Own Time [µs]	This represents the amount of runtime in microseconds spent running a particular trace event or set of aggregated trace events. The Own Time excludes all time spent waiting for other trace events that were started from the present trace event, such as external calls or specified statements (for example: SELECT statements). Own Time lets you see how intrinsically expensive a traced statement or operation was, in and of itself. Example: Imagine that method M1 has a total runtime of six seconds. One tenth of a second is accounted for by creating an object that offers method M2 (specified statement). Nine tenths of a second is spent doing other processing in M1 (unspecified statements). Five seconds more are spent waiting for calls from M1 to method M2 to complete. In the Aggregated Call Tree and in the Call Sequence, the Own Time of method M1 is nine tenths of a second because the rest of the runtime of six seconds was accounted for creating an object (100 milliseconds) and waiting for by method M2 (five seconds). Each of these events has its own trace entry. Their runtimes are therefore excluded from the Own Time of M1.
Call Level	This parameter counts the depth within the call hierarchy, starting from entry point of the call tree (Call Level = 0) downwards to the level of the selected trace event.
% Total Time	This column shows the Total Time of the trace event as a percentage of the total trace runtime.
% Own Time	This column shows the Own Time of the trace event as a percentage of the total trace runtime.
Calling Program	Calling Program identifies the ABAP program that initiated the trace event.
Called Program	Called Program identifies the ABAP program in which the trace event is located. These two parameters Calling Program and Called Program let you differentiate between code in your own application and the infrastructure code that originated in the ABAP Application Server. Tip Use the filter field, for example, to show only trace events that belong to your own application.