Show TOC

Code InspectorLocate this document in the navigation structure

Use

The ABAP Workbench offers a variety of tools for doing static and dynamic checks of the correctness of your programs and other objects.

The Code Inspector resolves the question of how to use these separate tools comfortably and efficiently.

With the Code Inspector, you can run all of ABAP's checking tools at one time. You can also choose which tools you want to run.

Uses: If you are a Developer, you can use the Code Inspector for the following tasks:

Ad hoc inspection definitions and results are not saved - you use them to check objects on which you are currently working. The definitions and results of re-usable inspections are saved. You can define re-usable inspections to check larger sets of objects or track your errors over time.

If you are a Quality Manager, you can do the following with the Code Inspector:

  • Define public re-usable code inspections. Other users - for example, other QMs - can use these inspection definitions and their results.

  • Approve or reject exceptions. Exceptions let developers mask check errors without correcting them.

  • Change the priority of check messages and get an overview of the available checks, documentation, and handling of check messages.

    For these functions, 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.

  • Do special checking tasks, such as these:

    • Automate regular runs of ABAP Unit tests

    • Review saved results

    • Search for particular ABAP statements or words in program texts

    • Have the Code Inspector automatically check objects when a transport request is released

    • Sending lists of messages by e-mail.

Starting the Code Inspector

Start the Code Inspector by entering transaction code SCI.

You can run ad hoc code inspections from most of the tools of the ABAP Workbench.

Authorizations

  • To run ad hoc inspections as a Developer, you need an authorization for authorization object S_TCODE with value SCI for field TCD.

  • To define and run re-usable, system-global inspections, approve exceptions, and do other Quality Manager tasks, you need an authorization for object S_COV_ADM with value * for field ACTVT