Working with Findings in the ATC Problems View

Each ATC check run creates new ATC check results, which include a list of ATC findings. If a local ATC check run finds errors or warnings, the ABAP Development Tools (ADT) automatically shows these to you in the Worklist of the ATC Problems view. The main purpose of the Worklist is to collect the results of all local ATC check runs that have been triggered in your IDE (during one and the same logon session) and keep the status of ATC findings up-to-date. This allows you, as a developer, to solve the ATC errors (or warnings) and immediately update the ATC status of the checked development objects – until the worklist is empty when all findings are fixed.

Here is how to work in this view and with ATC findings displayed.

Using the Filter

The ATC Problems view provides you with a filter to quickly switch between various views. In particular, you can switch...

Between multiple APAP projects from your workspace where local ATC check runs already have been performed during the IDE session
For each project, between various check variants used for the ATC check run
For each project and each check variant, between various object sets.

Figure 1: Using a filter for projects

Configuring Contents and Grouping Findings

By default, the ATC Problems view will group your ATC findings by priority. Using the view menu, you can also group your findings by checks or object names. In addition, you can configure the contents of the Worklist in the ATC Problems view to view only findings associated with a particular object or check. This is done using the Configure Columns... dialog available from the view menu.

Figure 2: Accessing the view menu

Jumping from ATC Findings into Your Source Code

If you are going to directly solve the findings listed in the Worklist in the ATC Problems view, double-click a finding to jump into your source code at the position where the ATC has found a problem.

Figure 3: Jumping from the worklist to the source code position affected

If you want to locate the program or program component that is responsible for an ATC finding, then:

Open the Outline view (if you have not done so already) to jump into the Outline at the program or component in which the error was found.
Choose the menu path Show In Project Explorer in the editor to display in the Project Explorer view, the program or program component in which the error was found.

Displaying Details and Documentation in the Worklist

The short description of the ATC findings might not provide you with sufficient details about the problem. In the ATC Problems view, you can directly views the specifics of an ATC problem – as well as the documentation that describes the ATC check and the ATC findings – for each currently selected finding.

The Details are especially important for understanding ATC findings and fixing problems quickly. For example, you might see these details for an instance of the ATC finding 'Parameter is a nested internal table and passed by VALUE'.

The context-sensitive help in the ATC Problems view

Figure 4: The context-sensitive help for a selected ATC finding is automatically displayed in the ATC Problem view

Note The Details content automatically refreshes when you select a new finding in the ATC Problems view.

Running a Recheck for Findings in the Worklist

After solving the finding in your source code, the currently displayed ATC result is no longer valid. You can then run a recheck for the corrected findings in order to check if they have disappeared from the worklist.

To run a recheck for one or multiple findings (within the entire worklist), proceed as follows:

(Multi-)Select the relevant finding(s) in the ATC Problems view.
Choose Recheck from the context menu.

Figure 5: Running a Recheck for a selected finding