hi

[Former Member]

hi frds

i got a query that

What is the difference b/w Codeinspector and Extendable check

[seshatalpasai_madala]

Hi,

THe basic difference is COde inspector can be run for an entire package where as Extended check is alwys for a program

Extended check is more concentrated on the SYNTAX Like checking for obsolete statements etc where as Code inspector is more intelligent and gives you info about the performance aspects of the program, including warning for Unicode checks etc.

Regards,

Sesh

.

.

[Former Member]

Hi,

Code Inspector can be used to check the performance of the code.

Regards,

Atish

[Former Member]

The

Code Inspector

is a tool for checking Repository objects regarding performance, security, syntax, and adherence to name conventions.

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.

2.Extended Program Check

You use this function to perform static checks, which are too time consuming for the normal syntax check. The extended program check returns both errors and warnings and it is possible to run either individual specialized tests or one whole standard check.

Use

You use this function to perform static checks, which are too time consuming for the normal syntax check.

The extended program check

returns both errors and warnings and it is possible to run either individual specialized tests or one whole standard check.

Procedure

1.

You access the extended program check by means of transaction SLIN. You can also choose Program ® Check ® Extended program check.
The system displays a list of possible check options. By default, all of them are selected. For detailed information about a particular option, position the cursor on it and choose F1.
The extended program check takes considerably longer time than other checks but it uses a buffer and the process speeds up after the first run.

2.

Select any options you need.
For each option you have selected, the system displays an overview of the number of errors, warnings, and messages.
Only the especially critical warnings are displayed before the standard check.

3.

Choose an entry to display the corresponding detail screen.

From that screen you can jump to the appropriate point in the program and correct the error
Use
You use this function to analyze errors and warnings returned by the system during the standard and the extended program check of ABAP code.

Features

Syntax Errors (Red Light)
When you have an error in your program, the check stops and returns an error message. In many cases the system offers a possible correction of the error.

You can activate a program that has syntax errors but you cannot generate and execute it. Syntax errors are regarded as fatal by the extended program check and it is obligatory to remove them.

Syntax warnings (Yellow Light)
The syntax check does not stop at warnings and the program is basically executable. Syntax warnings should be taken care of because they may lead to unexpected errors.

The different types of warnings look the same in the syntax check tool but they have different priorities.

TODO-relevant warnings

These warnings are subdivided into three different priority levels, which are linked to the internal SAP TODO checks.

1. Priority 1

These are warnings known to lead to a program crash. The category also includes all constructs that should not be used because they lead to program errors and semantically incorrect behavior.

2. Priority 2

This category refers to constructs that do not necessarily lead to errors but are, for example, obsolete and can be replaced by up-to-date constructs. Priority 2 errors may lead to priority 1 errors or syntax errors in future releases.

3. Priority 3

It is recommended to remove these errors when possible. They may lead to escalation in priority in future releases.

Warnings without TODO relevance

These warnings do not have a TODO relevance but point to questionable language constructs, which may lead to TODO-relevant errors.

Warnings in the extended program check

There are two more classes of syntax warnings, which are displayed only during the extended program check (SLIN). They are:

· SLIN Warnings

Similar to the other warnings, but they are displayed only in the extended syntax check.

· SLIN Infos

SLIN Infos point to possible (semantic) program errors. According to the situation, the program should be changed or the messages should be switched off.

Only the SLIN messages of this category can be switched off by means of special comments

reward points if it is usefull .....

Girish

[Former Member]

Extensible check means it will take account of the program rules(basic steps) and it will tell how much errors warnings and messages u got in which part of ur code

Code inspector will shown in a folder format view which also have extensible check in it...It will show the statements accessing areas and how much it is get utilized

The Code Inspector tests single objects or object sets (programs, function groups, classes, interfaces, Dictionary objects) for performance, security, serviceability, error proneness, and statistical information

REWARD IF USEFUL!!!!!!!!!!!!!!!!!!!!