Learn to use the ABAP code inspector

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. 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:

    Requires Free Membership to View

    Login

    When you register, you will start receiving targeted emails from my award-winning team of editorial writers. Our goal is to keep you informed on the hottest topics and biggest challenges faced by SAP professionals today.

    Hannah Smalltree, Editorial Director

    By submitting your registration information to SearchSAP.com you agree to receive email communications from TechTarget and TechTarget partners. We encourage you to read our Privacy Policy which contains important disclosures about how we collect and use your registration and other information. If you reside outside of the United States, by submitting this registration information you consent to having your personal data transferred to and processed in the United States. Your use of SearchSAP.com is governed by our Terms of Use. You may contact us at webmaster@TechTarget.com.


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 http://service.sap.com/performance.
 

This was first published in August 2003

Join the conversationComment

Share
Comments

    Results

    Contribute to the conversation

    All fields are required. Comments will appear at the bottom of the article.

    Disclaimer: Our Tips Exchange is a forum for you to share technical advice and expertise with your peers and to learn from other enterprise IT professionals. TechTarget provides the infrastructure to facilitate this sharing of information. However, we cannot guarantee the accuracy or validity of the material submitted. You agree that your use of the Ask The Expert services and your reliance on any questions, answers, information or other materials received through this Web site is at your own risk.

    Back to top