Archive
Code Insights
-
Avoid octal values
Integer literals starting with a zero are octal rather than decimal values. While using octal values is fully supported, most developers do not have…
-
The code contains too many throws to system exceptions
The code contains too many thows to system exceptions (java.lang.Error, java.lang.RuntimeException). Application should have their own error exception classes. Throwing generic exception force callers…
-
The code contains too many queries leading to a high number of table columns
Complex select clauses, i.e select clauses with many column can be difficult to read and does not help the reader who needs to identify…
-
The code contains too many hard coded absolute file system paths in include directives
In order to ease change and to hide platform specific information from any potential misuse, it is highly recommended to use SAP ABAP logical…
-
The code contains too many “SELECT *” requests
This Code Insight counts one occurrence each time a “SELECT *” or “SELECT SINGLE *” query is found.
-
The Web Dynpro code contains too many direct calls to routines using “me–>”
Special rules apply for the implementation of Web Dynpro routines, such as “wd_Do_Init” methods. Some ABAP language statements cannot be used. Other routines cannot…
-
A Program, User-Exit or Include contains too many Open SQL queries that access SAP standard tables in modification
SAP standard tables are part of the SAP software and they must not be modified by custom components. These can be affected by the…
-
The code contains too many SQL instructions with a missing where clause, or using “order by”, or using “not” operator or “is null” check in a where clause
For reliability and performance purposes, avoid using too many SQL instructions with a missing WHERE clause. Also, using “ORDER BY”, “NOT LIKE” or “IS…
-
Empty functions and methods should be avoided
For maintainability aspect, avoid ABAP Functions, ABAP Forms, and ABAP Modules that contain no statements.
-
The code contains too many unchecked returns of functions calls
Missing return code checks after an Open SQL statement can result in unpredictable behavior and untraceable execution errors. This is why it is extremely…