Problem solve Get help with specific problems with your technologies, process and projects.

Learn to use the ABAP code inspector

The static code inspector (transaction SCI) is an enhancement SAP included for the Web Application Server based releases of R/3. Here's information on how to use it!

The static code inspector (transaction SCI) is an enhancement SAP included for the Web Application Server based releases of R/3. It has been well integrated in the standard ABAP editors for that release. You don't have to upgrade to R/3 Enterprise, however, to enjoy the features and functions it offers because it has been retrofitted to 4.6C as an attachment to OSS Note 543359. The code inspector is "static" in the sense that it does not dynamically check the code in debug mode, but rather by applying a set of rules worked out by the SAP engineers.

The code inspector can produce a useful report informing developers that they have defined data items that they never reference, for example. The most useful feature may be the SQL advice that the inspector produces, warning developers that they have coded a SELECT statement that will bypass the buffered data in the servers, for example.

Creating a new test is very easy, even in the retrofit to 4.6C. Here are the steps:
1. Invoke transaction SCI
2. Define a new "test object", usually a single program name or range of program names. You must assign a meaningful name to the "test object".
3. Define "inspection criteria" by selection one or more possible tests from a dialog box. The more tests you select, the longer the report will take to run, and the more output produced. You must assign a name for this object as well.
4. Finally, create an "inspection" object by matching an already defined "test" object with a defined "test criteria" object.

The four-step process provides for maximum reusability of test definitions. The results of the inspection are presented in a hierarchical report that can be expanded only in the areas of greatest interest.

Production of the report for a large range of objects (over 50, as SAP recommends) can be done in parallel proceses spread over a server group.

More information is readily available at

Dig Deeper on SAP ABAP

Start the conversation

Send me notifications when other members comment.

Please create a username to comment.