CL_CHK_STS_DEBUGCODE - Check to Detect the Left Over Debug Code

SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3up   General Data in Customer Master  
This documentation is copyright by SAP AG.

Functionality

This Checkman Check scans the source code to find occurrences of the commands ASSERT, BREAK-POINT or BREAK.

Furthermore it also checks if there are any constant comparisions which are often used by developers for debug purposes during development.

Leftover debug information for support purposes should not be reported. This is important. Check forescape codes (like #EC nobreak). If the debug code is not needed anymore or contains sensible information (e.g. passwords, names of developers, etc.) add an error message to the log file.

If the Leftover debug code contains any sensible information then the Security Message Priority is 1 (high).

Relationships

Example

Following are few examples of constant comparisions:

IF 0 <> 0, IF 0 = 1; IF 1 = 1, IF 0 > 1, IF 1 < 0. These wrong conditions are often used by developers for debug purposes during development.

Notes

If any debug code is found, it checks whether it is used for support purposes and it also checks, if the debug code contains sensible information.

Further information

BAL Application Log Documentation   SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3up  
This documentation is copyright by SAP AG.


Length: 1176 Date: 20120526 Time: 100128     triton ( 57 ms )