Show TOC

Analyzing Runtime Check ResultsLocate this document in the navigation structure

Prerequisites

  • To analyze results of the Runtime Check Monitor, you need the authorization profile for data read access.

Context

Target Audience
  • ABAP developers

Procedure

  1. In the selection screen of the Runtime Check Monitor, specify the object dataset and the data sources, or select a variant (if available) that already comprises all relevant settings.
  2. Press F8 or choose the Display Results button in the toolbar.

Results

Based on your selection options, the Runtime Check Monitor generates a list of findings that are displayed in table form.

The result list provides you with a type of worklist. By default, the list is sorted according to packages so that you can easily identify the users responsible for the findings.

Some other fields may be interesting for your analysis:

  • The Total Number of Occurrences states how often the respective SQL statement has been executed within the given period of time.
  • The Program Changed column indicates for each finding whether the corresponding program has been touched in the meantime so that a new version of that program exists in the system since the Last Occurrence Date/Time.
Figure 1: Typical List of Findings for "Empty table in FOR ALL ENTRIES..." Runtime Check

In the results list, each line represents a finding that corresponds to the SQL statement concerned. You can directly navigate to the relevant source code position using the navigation link within the Include column. In the source editor, you can then verify whether the relevant source code exactly implements the intended behavior. If it does not, you have the option to immediately correct the relevant section of ABAP source code (in the development system).

Figure 2: Navigation to the Source Code Concerned
Note For the “Missing ORDER BY or SORT after SELECT” runtime check, every finding in the results list provides direct access to two source code positions: the first position points to the very statement that requires the internal table to be sorted and the second one refers to the related SELECT statement.
Figure 3: Typical List of Findings for "Missing ORDER or SORT after SELECT" Runtime Check
Tip For each finding, you can access the call stack that leads to a particular call or event within the call tree. To display the call stack, perform the following steps:
  • On the results list for the “Missing ORDER BY or SORT after SELECT” check, put the cursor on the finding in question.
  • Click the Call Stack button in the toolbar.
Figure 4: Accessing Call Stack