
The table below explains how to fill out the fields on the ABAP Trace Request dialog. The dialog lets you schedule asynchronous traces of ABAP program executions. For example, you can trace HTTP requests or RFC calls that are processed by the back end system.
| Field | Description |
| Which requests do you want to trace? |
Here you tell the ABAP Trace what sort of activity you want to trace. The most frequently used choices are these:
Other choices have the following meanings:
|
| Limit to | With the fields in this section, you can specify what you want to trace.
Object type: This selector appears if you need to specify the type of object to trace. For example, if you choose Reports and Transactions, above, then you can specify whether the object to trace is a transaction or an ABAP program. 'Object Name': The legend of this field changes to reflect the type of object you want to trace. In this field, you specify the name of the object to trace. This may be an ABAP program name or transaction, a URL, or some other object. In the case of a URL, enter the name of the ABAP HTTP service as it is shown in transaction SICF. For example: /sap/public/ping. Do not enter a full URL with host and port. Also, don't enter a query string or other parameter information. User and client: Activity is traced in your current client; you can specify another client only if you are logged on to the system client. It's often best to leave User: empty. Enter a user name if you are sure that the program you wish to trace will run under a particular user. Server: You can schedule a trace on all ABAP application servers of your back end system, or only on the current server. Usually, it's best to schedule a trace on all servers. ABAP's load-balancing features make it hard to predict the server at which a program will run. |
| Which restrictions should apply? | Here, you can specify how many traces should be made.
Schedule more than one trace if you need to be
sure of capturing the right instance of a program run. Once the requested
number of traces is reached, no further traces are run on that ABAP application server.
You can also change the expiration time of a trace request. By default, the request is canceled after one hour. |
| Should call tree information be included in the trace? | The Yes radio button
tells the trace to record all trace events
individually in a trace. Trace events are the ABAP statements and events that can be traced (all ABAP statements and events that have a potentially high cost in performance). The call tree display needs this unaggregated trace content. No tells the trace to aggregate trace events. Aggregation means that the run times of identical trace events that are called identically are accumulated. The run times of aggregated trace events are added up to a single total. In this case, Call Tree is not available. See Understanding the Trace Fields for more information on aggregation. If you select Yes, then both the Trace Hitlist and Call Tree analysis tools are available to you. If choose No, then only the Trace Hitlist analysis tool is available to you for displaying the trace. |
| Description of the trace | The Description is the trace title shown to you in the ABAP Traces view. The ABAP Trace generates a description for you, or you can enter your own description. |