Overview of Functions 

Use

Using the Code Inspector (transaction code SCI), you can check individual objects or sets of objects for performance, security, syntax, and adherence to name conventions. You can also determine statistical information or search for certain ABAP words (tokens). In the Code Inspector, you can define inspections that, with the help of check variants, examine certain sets of objects. As the result of an inspection, you receive information messages, warning messages, or error messages on different properties of the examined objects.

Integration

You can call the Code Inspector using transaction code SCI or through the menu path SAP Menu à Tools à ABAP Workbench à Test à Code Inspector. Also, you can call the Code Inspector from the following transactions:

·        ABAP Dictionary (SE11) for DDIC tables

·        Class Builder (SE24) for classes and interfaces

·        Function Builder (SE37) for function groups

·        ABAP Editor (SE38) for programs or reports

·        ABAP Workbench (SE80)

Features

The range of functions in the Code Inspector is limited to checking static object definitions and can therefore only point out certain problems.

It cannot, for example, give a precise statement as to how the overall performance of a program is. To be able to do this, you need to analyze program execution yourself at runtime – for example, using the Runtime Analysis Tool (transaction code SE30), the Performance Trace (ST05), or the Global Performance Analysis Function (ST30).

Activities

If you have not yet worked with the Code Inspector, you need to do the following:

       1.      Create a set of objects to determine the objects to be checked.

       2.      Define a check variant (or use a predefined one) in order to define the extent of objects to be checked.

       3.      Create and execute an inspection in order to execute the object check.