Show TOC

Managing Code Inspector ExceptionsLocate this document in the navigation structure

Procedure

Some check messages of the Code Inspector can be masked with exceptions.

This section explains how to use exceptions.

Note

To see which messages may be masked with exceptions, 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, a message can be masked by inserting the comment in the source code.

No entry in the Exception column means that a message cannot be hidden or cancelled.

Prerequisites and Limitations

  • You must designate one or more users with full Code Inspector authorizations to review and approve exceptions. You must tell your developers which users are responsible for their exceptions.

    Developers apply for exceptions from the results of code inspections. To complete an exception request, a developer must enter the name of the user who should review the request.

  • You should use the Code Inspector in your consolidation or Quality Assurance test system only. Do not let developers apply for exceptions in their development systems.

    The reason: Exceptions are system-local entities. They cannot be transported. You should use and manage exceptions only in a stable, long-lived Quality Assurance system. Otherwise, the exceptions can get lost, so that hidden errors are reported once again.

    In practice, this limitation means that developers should use the Code Inspector in the QA system. Only there will check messages be hidden by exceptions.

Reviewing and Approving Exceptions

  1. Start the Code Inspector with transaction SCI.

  2. Choose Start of the navigation path Goto Next navigation step Exceptions Next navigation step Approve End of the navigation path to see if any developers have sent you requests for exceptions. You will only see exceptions that specify your user name as the approver.

    ( Start of the navigation path Exceptions Next navigation step Requested End of the navigation path shows a developer which exceptions he or she has asked for.)

  3. If you need more information, double-click on a requested exception to see the original check message.

    From the check message, you can jump to the source code or use the other resources of the results display.

  4. Approve or reject an exception.

    If you approve, the problem is masked or hidden in this system as long as the exception stays in effect.

    If you reject the exception, then the request disappears from the exception display. The Code Inspector will report the problem again when it next runs.