SAP Note 16649 - SE30: Inaccurate positioning in the source code (Stat.)

Symptom:

With the following statistics entries, positioning is inaccurate in the source code:
- Loaded programs
- Conversions (from/to type P + other)
- Conversions from type P
- Conversions to type P
- Type P arithmetic

Cause and prerequisites

The statistics entries, unlike normal entries (z.B. PERFORM f), are not written to the measuring data file as a pair (for example begin/end PERFORM f), but as a unit in cumulative form:
a) Several similar entries are grouped together in one statistics entry.
In addition:
b) A statistics entry is only written to the measuring data file with the next part of a paired entry.
Due to a) and b), the precise allocation of an individual component of a statistics entry to the source code is no longer possible.
This was implemented this way so that the measuring data file does not become too large unnecessarily.

Solution

• There is no complete solution.

• Statistical conversions can be found with the help of the report RSANAL00.

• Start the report RSANAL00.

• Enter the name of the report or module pool to be examined for conversions.

• Press the pushbutton 'Conversions'.

• Choose a line in the list of results. This takes you into the editor where you can make the necessary changes, so that the conversion in question is missed out.

• Dynamic conversions cannot be positioned exactly in the source code. By double-clicking on 'Statistical entry', you display the modularization units where the conversions are done.

Additional key words

ABAP, runtime analysis