topic hi in Application Development and Automation Discussions

hi

Former Member — Fri, 16 Mar 2007 05:54:48 GMT

hi this is prathap

can any body send material regarding slin and code inspector

thanks & regards

prathap

Re: hi

Former Member — Fri, 16 Mar 2007 05:57:48 GMT

HI,

Hi,

U can refer this

http://help.sap.com/saphelp_nw2004s/helpdata/en/43/00c5b7daf15166e10000000a1553f6/content.htm

http://help.sap.com/saphelp_nw04/helpdata/en/cf/f2bbcb142c11d3b93a0000e8353423/content.htm

http://help.sap.com/saphelp_nw2004s/helpdata/en/d1/801afd454211d189710000e8322d00/content.htm

Kishore.

Re: hi

Former Member — Fri, 16 Mar 2007 06:03:31 GMT

HI Prathap..

U can refer this

http://help.sap.com/saphelp_nw2004s/helpdata/en/43/00c5b7daf15166e10000000a1553f6/content.htm

http://help.sap.com/saphelp_nw04/helpdata/en/cf/f2bbcb142c11d3b93a0000e8353423/content.htm

http://help.sap.com/saphelp_nw2004s/helpdata/en/d1/801afd454211d189710000e8322d00/content.htm

GOTO SLIN transaction,

Place the cursor on each of the checkboxes and click F1 button,

You can get help for each of the checkboxes

EPC check is nothing but, Extended Program Check.

Goto SE38 > Program > Check > Extended Program check > F8 then u will get the errors, mesages, warnings in ur program.

Its always better to do a check for every program.

SLIN is teh TCODE for directly going into the check.

ABAP program extended syntax check (full check of programs syntax)

AND

Code Inspector:

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.

If it helps Reward with point's..

Regards Rk

Message was edited by:

Rk Pasupuleti

Re: hi

Former Member — Fri, 16 Mar 2007 07:14:00 GMT

hi,

Code Inspector

Features

The Code Inspector is a tool for checking static ABAP coding and DDIC objects (i.e. generally all objects of the Object Repository) under aspects of functional correctness, performance, security, reliability, and statistical information.

It helps developers to adhere to programming standards and guidelines by creating messages on less-than-optimal coding. The Code Inspector offers various possibilities to define object sets and to combine multiple single checks in so-called "check variants". These functions, and the tool's parallel processing framework, make the Code Inspector a flexible and effective development assistant.

The Code Inspector can be used in various scenarios with different types of checks, thus providing insights into the code quality from various angles.

Usage scenarios

Single object checks from the Development Workbench

You can check a single object with the Code Inspector from the ABAP Editor (transaction SE38), the Function Builder (transaction SE37), the Class Builder (transaction SE24), or the ABAP Data Dictionary (transaction SE16). To do this, choose <object> > Check > Code Inspector from the menu, where <object> can be a program, function module, class, or table. The respective single objects are then checked with a default check variant.

Checks on transport objects from the Transport Organizer

You can invoke the Code Inspector from within the Transport Organizer (transaction SE09) to check objects in a transport request. To do this, choose Request/Task > Complete Check > Objects (Syntax Check).

Checks on sets of objects from transaction SCI

The Code Inspector (transaction SCI) itself enables you to create a wide range of object sets using standard selections via package, software and application component, source system, transport layer, responsible, object type, object name and so on.

In addition, special object collectors are available that allow you to read objects from a file, for example.

An object set can be combined with a check variant to a so-called "inspection" that can be executed in a single process or in parallel. For a more details see Code Inspector User Manual

regards,

keerthi