*&---------------------------------------------------------------------* *& Report YCLASSICAL_JOINING *& *&---------------------------------------------------------------------* *& *& *&---------------------------------------------------------------------* REPORT yclassical_joining NO STANDARD PAGE HEADING LINE - SIZE 110 LINE - COUNT 255 MESSAGE - ID z...
ABAP Code Inspector Tool
The Code Inspector is a tool for checking static ABAP coding and DDIC objects .
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".
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 SE11). To do this, choose <object> > Check > Code Inspector from the menu, where <object> can be a program, function module, class, or table.
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 SE11). To do this, choose <object> > Check > Code Inspector from the menu, where <object> can be a program, function module, class, or table.
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.
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.
•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.
End
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.
End
Comments
Post a Comment