regarding syntax errors

[Former Member]

Hi guys,

Above 46C system, Can we use SLIN or FM 'Extended program check' instead of SCI.

Both outputs are same with respect listing Syntax errors/Warnings/Messages? please confirm.

Regards

Ambichan

[Former Member]

Both the Outputs are not same.

SLIN is an extended syntax check.

SCI is Code inspector, a tool for checking Repository objects regarding performance, security, syntax, and adherence to name conventions and other formats that you set in.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.

SLIN

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.

SCI

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

1. 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.

2. 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).

3. 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.

Types of checks and check variants

Below is a short extract of the types of checks and functions that are offered by Code Inspector. New checks can be implemented if required, see for example Code Inspector - How to create a new check .

• Syntax

Syntax check; extended program check

• Performance

Analysis of WHERE clauses for SELECT, UPDATE and DELETE ; SELECT statements that bypass the table buffer , low-performance operations on internal tables; table attributes check

• Security

Usage of critical statements; dynamic and cross-client database accesses; use of ADBC-interface

• Robustness

Check of SY-SUBRC handling; suspect conversions; activation check for DDIC objects

• Programming Conventions

Naming conventions

• Search Functions

Search of ABAP tokens; search ABAP statement patterns; search for ABAP statements with regular expressions

• Metrics and Statistics

Program complexity test; statement statistics

You can combine any of these single checks into so-called "check variants", for example to check for the adherence to given programming guidelines.

Best Practices

Developers can use the Code Inspector to support their everyday work. For example, the search functions or metric checks of the tool can be a great help when restructuring the code.

The Code Inspector allows developers to define which objects are to be checked and which quality aspect of the code is to be inspected (e.g. performance, security).

It is also possible to define global check variants as general programming guidelines, to ensure standardized programming within a development community.

Check variants can prescribe for example naming conventions or other rules. The global check variants 'DEFAULT' and 'TRANSPORT' inspect objects in the development workbench and in transport requests, respectively. These check variants contain SAP-defined settings, but can be modified as needed.

Another global check variant delivered with every SAP system is 'PERFORMANCE_CHECKLIST' which helps to detect less-than-optimal coding with regard to application performance.

Hope this Helps.

Vinodh Balakrishnan

[Former Member]

Hi

U can use both slin and sci . for checking the syntax and also for the performance issues.. Slin is for the extended program check whereas the sci is for the code inspector.

Regards,

Sana.'

[Former Member]

hi guys,

Thanks for your replies.

I know, Its possible to fetch the Syntax check errors and Extended program check errors using variant option in SCI.

i want to fetch those(above) errors/warnings and display the error in Customized format at Excel. So i am looking for FM to do above job. I found FM 'Extended_program_check'used in SLIN to display the Error output. But i want to confirm whether it includes both Standards Syntax errors & EPC errors or only EPC errors.

Is there any FM or Class to fetch the above errors to Excel format without using SCI tool or SLIN tool.

Thanks in advance.

regards

Ambichan