SLIN is T.code For extended program check.......
Use
You use this function to 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.
Procedure
... 1. You access the extended program check by means of transaction SLIN. You can also choose Program ® Check ® Extended program check.
The system displays a list of possible check options. By default, all of them are selected. For detailed information about a particular option, position the cursor on it and choose F1.
The extended program check takes considerably longer time than other checks but it uses a buffer and the process speeds up after the first run.
2. Select any options you need.
For each option you have selected, the system displays an overview of the number of errors, warnings, and messages.
Only the especially critical warnings are displayed before the standard check.
3. Choose an entry to display the corresponding detail screen.
From that screen you can jump to the appropriate point in the program and correct the error.
Errors and Warnings Use
You use this function to analyze errors and warnings returned by the system during the standard and the extended program check of ABAP code.
Features
Syntax Errors (Red Light)
When you have an error in your program, the check stops and returns an error message. In many cases the system offers a possible correction of the error.
You can activate a program that has syntax errors but you cannot generate and execute it. Syntax errors are regarded as fatal by the extended program check and it is obligatory to remove them.
Syntax warnings (Yellow Light)
The syntax check does not stop at warnings and the program is basically executable. Syntax warnings should be taken care of because they may lead to unexpected errors.
The different types of warnings look the same in the syntax check tool but they have different priorities.
TODO-relevant warnings
These warnings are subdivided into three different priority levels, which are linked to the internal SAP TODO checks.
1. Priority 1
These are warnings known to lead to a program crash. The category also includes all constructs that should not be used because they lead to program errors and semantically incorrect behavior.
2. Priority 2
This category refers to constructs that do not necessarily lead to errors but are, for example, obsolete and can be replaced by up-to-date constructs. Priority 2 errors may lead to priority 1 errors or syntax errors in future releases.
3. Priority 3 it is recommended to remove these errors when possible. They may lead to escalation in priority in future releases.
Warnings without TODO relevance
These warnings do not have a TODO relevance but point to questionable language constructs, which may lead to TODO-relevant errors.
Warnings in the extended program check
There are two more classes of syntax warnings, which are displayed only during the extended program check (SLIN). They are:
· SLIN Warnings
Similar to the other warnings, but they are displayed only in the extended syntax check.
· SLIN Infos
SLIN Infos point to possible (semantic) program errors. According to the situation, the program should be changed or the messages should be switched off.
Only the SLIN messages of this category can be switched off by means of special comments.
IF helpful, reward some points.Regards,
Bhaskar
Bluesky
