Component documentationAnalyzing Individual ABAP Statistics Records

 

Use ABAP statistics records to find out which activities are running in your system. This is a log of system activities that is implemented in the ABAP kernel. Every dialog step is logged and recorded with technical information, such as response time, transaction code, or CPU time. These individual statistics records are written in the file system of the relevant instance, and are regularly overwritten (by default, every 48 hours).

ABAP statistics records are therefore well suited to investigating the performance of a system or of an instance in more detail, or, if performance problems occur, to identifying the area causing the problems.

If you want to examine performance on the basis of ABAP statistics data, there are a number of options available to you:

  • You can display the statistical aggregates in transaction ST03 (Workload Monitor) or ST03G (Global Workload Monitor). At this level, no information about individual system actions is available to you, but rather an overview of the workload on a daily, weekly, or monthly basis.

  • You can display the individual statistics records in transaction STADWD. This section describes the use of this transaction.

If you want to examine individual statistics records, transaction STADWD is available to you. You use the transaction in three steps:

  1. You define conditions and grouping rules for the main statistics records that you want to display (main records and subrecords are defined below). The options available to you here are described in the section Selecting the Statistics Records.

  2. A list of the selected main records and their most important information is displayed in a table.

  3. You can display additional details for individual main records, that is, both all of the measured times and additional information for the main record, and also all subrecords that belong to this main record. The options available to you here are described in the section Displaying the Statistics Records.

Note Note

Transaction STADWD is the successor to transaction STAD, which continues to be available to you.

End of the note.

More Information

Generating and Storing ABAP Statistics Records

The statistics records are generated by the work processes of the ABAP application servers and, at the end of each dialog step, are saved in a shared buffer of the SAP kernel. Once this buffer is full, the records are written to a file. Each application server has its own statistics files. A new file is created for each hour, and the maximum number of these files is limited. Every time a new statistics file is created, the oldest file is deleted. The profile parameter stat/max_files defines the number of statistics files; by default, this parameter has the value 48, which determines the retention period of the statistics files in hours.

Structure of ABAP Statistics Records

Every statistics record has exactly one main record; this contains general information about the action that is always available, such as response time, transaction code, or CPU time. This main record can also have various subrecords. Subrecords contain additional, specific statistical data for individual aspects of the action. If, for example, RFC calls have been made in the context of the action, there are RFC subrecords; if a job was executed in the context of the action, there is a background subrecord. All of these subrecords are optional, meaning that the storage space for the corresponding information is only required if they occur in the action.