general

[Former Member]

hi,

what is code inspector?

[Former Member]

Hi,

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.

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

You can check the following link for details.

https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/library/events/sap-teched-...

http://help.sap.com/saphelp_erp2004/helpdata/en/56/fd3b87d203064aa925256ff88d931b/frameset.htm

Thanks,

Reward If Helpful.

[Former Member]

Hi

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.

Creating and Starting a Test Run in the Code Inspector Locate the document in its SAP Library structure

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

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.

Inspection Locate the document in its SAP Library structure

Definition

During an inspection, individual objects or sets of objects are checked as to whether certain programming guidelines have been adhered to. The result of an inspection run is a list of the individual checks made with errors, warnings, or information messages.

There are two types of inspections. They differ with respect to whether the results are made persistent or not.

· Persistent inspections with results storage

For execution on the local server or parallel execution on the server group. You can plan persistent inspections as background jobs and use them for any size of object set.

· Anonymous or ad-hoc inspections without results storage

For execution on the local server and for fewer than 50 objects. You can execute ad-hoc inspections in online mode only.

Use

As an ABAP developer or quality manager, you can use the inspections to find out whether the most important programming guidelines in static ABAP coding or other object definitions have been adhered to.

Structure

The results list of the inspection consists of the following overview levels:

· The executed checks are subdivided into the check categories: performance, security, syntax, search, general.

· Each check category contains the individual test results, sorted by error, warning, or information messages.

· Each of these messages contains:

¡ The position of the source code (or the name of the TADIR object)

¡ A short explanation

Integration

You can create and maintain server groups for persistent inspections using the transaction SE59 -> RFC Groups.

Checkthis link

http://help.sap.com/saphelp_nw04/helpdata/en/30/243ad24cf4cb4faf5a5b83621a37d7/content.htm

http://searchsap.techtarget.com/loginMembersOnly/1,289498,sid21_gci918390,00.html?NextURL=http%3A//s...

http://www.sapfans.com/forums/viewtopic.php?t=71547

Regards

Pavan

[Former Member]

Hi

Code inspector is used to analyse the program for the

following ..

Performance checks

Syntax Checks

Naming Conventions , etc...

Use tcode SCI

Regards

Raghav T

[Former Member]

hi Ganpathi,

give U r mail id ,I will send the document usage on code inspector.

Regards