CODE INSPECTOR 

Purpose
The Code Inspector is a generic tool that you use to check SAP repository objects. You use it to define inspections
which examine object sets with the help of check variants. It checks the performance, security, syntax, and
adherence to naming conventions of individual or sets of repository objects. You also use it to retrieve statistical
information or to search for certain ABAP tokens. As a result of an inspection, you receive information, warning,
and error messages about the different properties of the examined objects.

To start the Code Inspector, perform one of the following:

Choose SAP Menu ® Tools ® ABAP Workbench ® Test ® Code Inspector.
From the SAP Easy Access, enter transaction code SCI.
Features
The Code Inspector comprises the following elements:
1. Inspection, where you can perform checks on an object.
You can display, create, change, copy, create a new version of, delete, and see the results of an
inspection.
2. Object set, where you can determine the objects to be checked.
You can display, create, change, copy, and delete an object set.
3. Check variant, where you can define the individual checks that are performed on the objects.
You can display, create, change, copy, and delete a check variant.
Constraints
The range of functions of the Code Inspector is limited to checking static object definitions and can only point out
certain problems. For example, it cannot give a precise prediction of the overall program performance. To do this,
you need to analyze the program execution at runtime, using the Runtime Analysis (transaction code SAT), the
Performance Analysis (transaction code ST05), the Global Performance Analysis (transaction code ST30), or
another relevant tool.

Inspection  Definition
During an inspection, individual objects or sets of objects are checked as to whether they adhere to certain
programming guidelines or meet certain search criteria. The result of an inspection is a list of the conducted checks
together with the created errors, warnings, and information messages.

Structure

Types of Inspections
There are two types of inspections, which differ with respect to whether the results are made persistent or not.

●      Persistent inspections, the results of which are stored.

These inspections are executed on the local server or parallel in a server group. You can plan
persistent inspections in the background and in a periodic job and run them on any size of object
set.
 You can create and maintain server groups for persistent inspections using the RFC server
groups (transaction RZ12)
●      Anonymous inspections, the results of which are not stored.
These inspections are executed on the local server and can only be run on no more than 50
objects. You can execute anonymous inspections in online mode only.

Inspection results
The results of an inspection are subdivided into check categories. These can be, for example, performance,
security, syntax, or search. Each check category contains the individual check results, sorted by error, warning, and
information messages. Each of the latter contains the position in the source code (for program-like objects), and a
short explanation.

 Object Set  Definition

Object sets are groups of repository objects grouped together for an inspection. There are global and local sets of
objects. Global sets are visible for all users while local sets are only visible for a single user.

Use
Use object sets to group several single objects together for an inspection. You can include any repository objects in
a set. For example, object sets can contain programs, function groups, classes, or DDIC objects.

Integration
Together with the check variant, the object set makes up an inspection within the framework of the Code
Inspector.

Check Variant 
Definition
A check variant is a set of checks which are executed during an inspection on the individual objects of a defined
object set.

Structure

Check Variants Types

There are global and local check variants. Global check variants are available for all users. SAP supplies the global
DEFAULT variant which you can use to check objects from within the workbench. If you have the appropriate
authorizations, you can create global check variants yourself. It is possible to transport global check variants into
other systems using the transport system. In contrast to the global check variants, local check variants are visible
only for one user.

Check Variant Categories

A check variant consists of one or more check categories, each of which consists of one or more individual checks.
Different checks examine different object types. It is possible to select different attributes for the individual checks.