Application Development Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
cancel
Showing results for 
Search instead for 
Did you mean: 

Hi,what is extended progm check and code inspector & diff of both &use

Former Member
0 Kudos
307

Hi All,

Pls provide the information for :

what is extended program check ,where and when it is used &

what is code inspector

Difference between extended program check and code inspector .

pls provide ASAP.

Thanks&regards.

Bharat Kumar

6 REPLIES 6

Former Member
0 Kudos
77

Hi Bharat,

Extended program check : gives all the errors , warnings in our program.

any formatting errors like that.

while code inspector checks for program codes.select queriesetc..

reward points if helpful.

Regards,

Hemant

Former Member
0 Kudos
77

Hi Bharat,

<b>EPC</b> will 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.

check more herehttp://help.sap.com/saphelp_nw2004s/helpdata/en/d1/801afd454211d189710000e8322d00/frameset.htm

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

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

Regards,

Raghav

uwe_schieferstein
Active Contributor
0 Kudos
77

Hello Bharat

The extended program check (SLIN) is a subset of the checks that can be done using the code inspector (SCI).

If your application passes the SLIN check this simply means that the program is syntactically correct. However, it may be messy coded and become a nightmare for every (other) developer who has to maintain this application.

Using the code inspector you can, for example, check the naming conventions of program variables. Naming conventions are an indispensible part of every quality assurance in development. Hopefully your company has such naming conventions and the developers stick to it.

In essence: the code inspector includes the SLIN check (syntax check) and allows you to check the <b>quality of the applications</b> at the same time.

Regards

Uwe

sreeramkumar_madisetty
Active Contributor
0 Kudos
77

Hi

To check the program consistency and to findout the syntax errors and warnings.

We use the Extended Program Check and Code Inspectors.

se38->give program name ->Menu(Program)-> Check-> Extended Program Check/Code Inspector.

Regards,

Sreeram

former_member198270
Active Contributor
0 Kudos
77

hi Kumar ,

<b>EPC,</b> advantages are.........

With the help of EPC we can find out the

1. Absolete stmts

2. Authorization checks

3. Problematic stmts

4. Any hidden messages

through this we can increase the consistency of the program and the performance can also be increased.

And we can find out the stms that causes the problems in future when modifications are happened.

while <b>code inspector</b> checks for program codes,select queries .

For this go to se38 then program then check then EPC

Reward Points if helpful .

Reagrds,

Amber S

Yogitha
Employee
Employee
0 Kudos
77

Hi,

<b>Extended Program Check</b>

Many checks are excluded from the standard syntax check for performance reasons. The extended program check performs a complete check that includes the interfaces of external procedures called from your program.

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

<b>Errors</b> in the extended program check cause exceptions when you run the program which, in turn, lead to runtime errors. You must therefore correct them. The exception to this is coding that cannot be reached. However, you should delete this to minimize the size of your program and make the source code easier to understand.

<b>Warnings</b> in the extended program check should also be corrected. If your program contains statements that are definitely correct but still produce warnings in the extended program check, you can exclude them from the check using pseudocomments ("#EC ...).

The extended program check is also only a static check. It cannot eliminate all of the circumstances that could lead to exceptions or runtime errors. For example, any statements in which you specify arguments dynamically as the contents of fields, or in which you call procedures dynamically, cannot be checked statically.

Check the link:

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

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

Check the link:

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

Regards,

Yogitha