CODE INSPECTION

[Former Member]

HAI,

WHAT IS MEANT BY CODE INSPECTION (TCODE-SCI) ?

WHAT IS THE USE ?

THANK YOU

ASHOK KUMAR

[Former Member]

Hi,

You can check errors, warning and informations messages in Code Inspection for your program related to performance issues only. you can increase the performance of your program by removing these errors, warnings etc. by changing your code.

you can run this :

goto SE38 --> Open program --> goto Program Menu --> Check --> Code Inspector

Regards,

Sandeep Kaushik

[Former Member]

Hi See the link

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

<b>Reward points for useful Answers</b>

Regards

Anji

[seshatalpasai_madala]

Hi,

SCI (SAP code inspection) is a veru useful tool to check the developer code and other developer activites like table buffer options etc.

When you do a code inspector check it cheks for low performance DB statements, low performance LOOP statements, package errors that might lead to runtime exceptions in case of missing ADD-ON's etc etc.

So its always useful to use SCI To check your code once your development is done to improve the application.

Regards,

Sesh

[Former Member]

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

1. You can call the Code Inspector using transaction code SCI or through the path SAP Menu à Tools à ABAP Workbench à Test à Code Inspector.

2. Decide whether the inspection is to be visible locally for one user or globally for all users.

To be able to create an inspection globally, you require the appropriate authorizations.

3. Assign a name for the inspection.

4. Choose Create.

The system will then:

¡ Automatically assign a version number

¡ Propose a deletion date when the inspection should be deleted.

5. Select the objects to be checked.

To do this, you can specify a predefined set of objects, a transport request, or a single object.

If you specify a set of objects, you can decide – using the appropriate pushbutton – whether it is a local or a global set of objects.

6. Enter a check variant.

If you specify a check variant, you can decide – using the appropriate pushbutton – whether it is a local or a global check variant.

7. Save your entries.

8. Decide whether the inspection is to be executed locally (that means, on the current application server) or parallel on several application servers in a server group.

a. To execute immediately on the local server, choose Execute.

b. If you wish to execute the inspection in parallel on several application servers, choose .

The system shows a selection screen where you can decide the following:

i. The server group on which the inspection is to run.

ii. Whether the inspection is to run in the background.

iii.

9. Choose Execute or Execute...

The system performs the inspection run.

10. Choose Results.

The system displays a results tree.

a. To see the individual results, click the appropriate node of the results tree.

b. To get details of the individual results, choose Information.

Reward points if it usefull ...

Girish

[Former Member]

Hi,

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

For more info,

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

Regards,

Padmam.

[Former Member]

Hi,

The Code Inspector (transaction code SCI) is a tool for checking Repository objects regarding 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.

Code Inspector

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

Overview of Functions

Use

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.

Inspection

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.

Regards

[former_member404244]

Hi,

plz go through the below links..

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

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

Regards,

nagaraj