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: 

exactly use of SLIN tran. code

Former Member
0 Kudos

hi, experts,

please guide me the use of SLIN tran. code.

thanks & regards.

subhasis.

5 REPLIES 5

Former Member
0 Kudos

Hi

<b>SLIN -> Extended Syntax Check.</b>

This is Same as in <b>SE38 (Program->Check->Extended Syntax Check)</b>

The extended syntax check also performs package checks and displays messages of the appropriate type (error, warning, information) where necessary. You can then navigate to the line in the source code where the problem occurred by double-clicking.

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

Former Member
0 Kudos

SLIN is used for

1) to know unused data (variable, tables, subroutines)

2) to know obsolete FMs

3) superflous statements etc.

For more check the T-code SLIN

krishnak

Former Member
0 Kudos

Hi Subhasis,

We can go for the extended check.

Se38 provide the program name and crate and provide the logic ater that in application tool bar we can the program option select that in that we have the Check option in that extended chek is there select that. (SLIN-T.code).

These is used for perofrmance point of view if any un wanted line is there it will show.

Check any one program u can know.

Rgds,

P.Naganjana Reddy

0 Kudos

Hi subhasis,

There are two types of program checks - static check(when the program is created) and dynamic check(when you run the program).

The static check is again of two types - syntax check and epc (Extended program check)

The system checks ABAP programs statically when you create them and dynamically when they are running.

The syntax check tests the syntax of the program and internal semantics of a program. This what we usually use when we create the program using CNTL+F2.

The extended program check performs a semantic check (including, for example, checking whether the number and type of the interface parameters in an external procedure call is correct).

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.

Errors in the extended program check cause exceptions, which in turn cause runtime errors when you run the program. You must 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.

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

You should always run the extended program check on a new program. You have not finished developing a new program until you can run the extended program check on it without any errors or warnings. Messages are permissible, since they are generally not critical.

The extended program check is also only a static check. It cannot eliminate all of the circumstances that could lead to exception situations 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.

Hope that was useful.

Rgds,

P.Naganjana Reddy

Former Member
0 Kudos

Hi subhash,

SLIN is used for

To Find unused data (variable, tables, subroutines)

To find obsolete FMs

By executing slin we get errors, warnings, messages. normally as per standards u need to look into slin check and resolve the errors, warnings and messages. these are some of the parameters u get in slin check.

Test Environment

PERFORM/FORM interfaces

CALL FUNCTION interfaces

External program interface

Screen Consistency

Authorizations

GUI Status and TITLEBAR

SET/GET parameter IDs

MESSAGE

Character Strings

Output CURR/QUAN fields

Field Attributes

Superfluous Statements

Syntax check warnings

Check load sizes

Internationalization

Problematic Statements

Structure Enhancements

Package Check

Hidden errors and warnings

Regards,

Prasad