code inspector

[Former Member]

Hi experts,

What is meant by code inspector? (static performance tuning)

Regards veni.

[Former Member]

Hi,

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

Check this link for details.

http://help.sap.com/saphelp_nw04/helpdata/en/56/fd3b87d203064aa925256ff88d931b/content.htm

Also check this link too.

http://www.abapprogramming.blogspot.com/2007/11/code-inspector-in-abap.html

Regards,

Maha

[Former Member]

hi krishna,

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

In the Code Inspector, ABAP Unit tests can be used for any object sets.

The Code Inspector allows developers to define which objects are to be checked and which quality aspect of the code is to be inspected (e.g. performance, security).

It is also possible to define global check variants as general programming guidelines, to ensure standardized programming within a development community.

When configuring the check variant, you can activate ABAP Unit tests by choosing Dynamic Tests ? ABAP Unit. Existing ABAP Unit tests will then run alongside a regular code inspection.

reward points if useful..

[Former Member]

Hi

Code Inspector (SCI)

You can call the Code Inspector from the ABAP Editor (SE38), the Function Builder (SE37), the Class Builder (SE24), or as a separate transaction (SCI).

The Code Inspector indicates possible problems. However, note that, especially with performance issues: There is no rule without exception. If a program passes an inspection, it does not necessarily mean that this program will have no performance problems.

[Former Member]

Hi Veni,

Code Inspector (SCI) :-

You can call the Code Inspector from the ABAP Editor (SE38), the Function Builder (SE37), the Class Builder (SE24), or as a separate transaction (SCI).

The Code Inspector indicates possible problems. However, note that, especially with performance issues:-

There is no rule without exception.

If a program passes an inspection, it does not necessarily mean that this program will have no performance problems.

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.

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

http://help.sap.com/saphelp_nw04/helpdata/en/4f/3d1540bf1af72ee10000000a1550b0/content.htm

<b>Award points if useful.</b>

Regards,

kavitha