Home / Vulnerability Database / ABAP : Error bad handling
ABAP
ABAP : Error bad handling
Classification
PCI DSS 4.0
Overview
The application does not correctly handle errors or does not handle at all.
Any exception, if it can affect the logic of the program, must be handled.
In ABAP, there are two main ways to handle exceptions: classical and based on OOP. The way based on OOP is preferred.
- To implement error handling when calling methods and procedures, you must use the way based on OOP. In this case, the
RAISE EXCEPTIONstatements are used to call exceptions and theCATCH-TRYstatements to handle exceptions. - To implement error handling when calling RFM (remote function modules), you must use the classic error handling method, because the method based on OOP is not supported. In the classical exception handling mode, the
sy-subrcfield will be filled with the number under which the exception was indicated when the function module was called inEXCEPTIONS. Handling is carried out using the constructionsRAISEorMESSAGE RAISING. If an exception that is not processed when the function module is called occurs, and theOTHERSkeyword is missed, theRAISE_EXCEPTIONrun-time error occurs.
The system field sy-subrc is undefined after the statement CALL FUNCTION ... IN UPDATE TASK is executed.
References
LOW
DerScanner Severity Score
Do you want to fix ABAP : Error bad handling in your application?
See also
ABAP
ABAP : Insufficient authorization check
ABAP
ABAP : Empty password
ABAP
