Show TOC

Starting an Ad Hoc Inspection from the Code InspectorLocate this document in the navigation structure

Procedure

You can run a fast ad hoc inspection from the Code Inspector (transaction SCI), not just from the tools of the ABAP Workbench. The definition and results of the inspection are not saved for reuse.

Do the following:

  1. Start transaction SCI to start the Code Inspector.

  2. Leave the Name field in the Inspection frame empty. Click on Create or Change.

  3. On the screen which follows, you define the ad hoc inspection. Just as in a reusable inspection, you can choose from existing object sets and check variants or define new ones.

    You can also inspect the entities in a transport request or specify single programs or other entities. And you can define a temporary check variant by marking and unmarking the checks you would like to run.

  4. Run the inspection. The Code Inspector presents the results screen automatically.

    Here, the display is opened to show an error and two warnings. These are in the categories Analysis of WHERE Condition for SELECT and Low Performance Operations on Internal Tables.

    Figure 1: Useful Functions in the Code Inspector Results Display

  5. Respond to a result message. You can:

    • Correct the problem. Double-click on the error message to open the editor.

    • Mask the problem if it cannot or should not be corrected. In your code, enter the pseudo comment- if there is one - that cancels the Code Inspector check.

      Click on Documentation or the Exceptions in the results table to see if there is a pseudo comment.

    • Mask the problem with an exception if it cannot be corrected or masked with a pseudo comment. An exception has to be approved by a Quality Manager.

      Not all problems can be masked with a pseudo comment. In these cases, choosing Exceptions instead lets you request an exception.

      To request an exception, you need to specify the name of a user authorized to grant it, the scope of the exception, and optionally a comment. Once you save the exception, you can see it from the entry screen of transaction SCI. Choose Start of the navigation path Goto Next navigation step Exceptions Next navigation step Requested End of the navigation path.

      Note: For a complete list of messages with documentation and exception handling, choose Start of the navigation path Goto Next navigation step Management of Next navigation step Message Priorities End of the navigation path. Table entry in the Exception column means that an exception can be requested. Where a pseudo comment is shown, the message can be masked.