Non-class-based exceptions can be defined in the interfaces of function modules and methods. These exceptions are defined as follows:
- For methods of local classes, by assigning a name for the exception after the
EXCEPTIONSaddition of the statement [CLASS-]
- For methods of global classes or function modules, by assigning a name for the exception in the Class Builder or the Function Builder, in which case the radio button for exception classes is not selected.
In a method or a function module in whose interface non-class-based exceptions are defined, the statement
EXCEPTION or the addition
THROW in a
conditional expression cannot be used to raise class-based exceptions.
Before class-based exceptions were introduced, all exceptions defined in the interface of methods of global classes or function modules were non-class-based.
Non-class-based exceptions are raised by the following statements:
The handling of non-class-based exceptions is made possible by the addition
method calls and in
function module calls. Numeric values are assigned
to the exceptions, which are used to fill the system field
the exception is raised. The actual error handling takes place after the call, when the system evaluates
- The exceptions that can be defined in the interfaces of methods and function modules are not real exceptions, since they do not modify the control flow; instead they just end the processing of the
procedure prematurely and set the return code
- RFC currently allows only classical exception handling. Class-based exception handling is only possible in a different release track.