Basis Errors and Solutions

Symptom

This note describes an enhancement of the ABAP runtime analysis (SE30) to improve the support for end-to-end (E2E) tracing.
Other terms

Solution Manager diagnostics
Reason and Prerequisites

The ABAP runtime analysis generates one performance data file for each runtime measurement.
If you measure a stateful application (for example, SAP GUI for HTML, ABAP Web Dynpro, Business Server Page (BSP), or synchronous RFCs), successive HTTP calls or RFC calls are included in the same runtime measurement and are logged in the same file as a result.
In the case of a stateless application, the runtime measurement is closed when the application is ended. If a further HTTP call or RFC call is performed, the system starts a new runtime measurement and the data is written to a new file.
To be able to clearly assign the recorded performance data to a dialog step in the case of a stateful application, you must separate the data of the individual dialog steps, for example, by writing the data to different files.

Solution

To implement this solution, you must use the browser plug-in (see Note 1041556), which generates a new transaction ID for each HTTP request and each RFC call.
The enhancement includes
the dynamic profile parameter abap/atra_split_trace_file , anda kernel correction that ensures thatthe valid transaction ID is stored in the header of the performance data filethe current performance data file is closed and a new performance data file is created if
1. rstr/accept_remote_trace = TRUE
2. abap/atra_split_trace_file = 1
3. an incoming HTTP call or RFC call runs under a new transaction ID
A new performance data file is generated if one of the two following situations occurs: An inherited trace is used (”RFC, Update” is selected in the trace variant), or the “For User/Service” measurement is scheduled.

The enhancement meets specifically the requirements of the Solution Manager and can be used for the following release levels only:
7.00 (patch level 209)
7.01 (patch level xxx)
7.10 (patch level xxx)
7.11 (patch level xxx)
xxx means that the patch level number is not available yet.
The dynamic profile parameter exists only in the release levels mentioned in this note.