Class-Based Exceptions

Class-based exceptions started with release 6.10. They are realized as instances of exception classes. Exception classes are either globally predefined in the system or can be defined by the user globally or locally. Class-based exceptions are triggered either by the ABAP runtime environment or by a program.

• Exception situations recognized by the system, whose causes can be handled in the program, trigger predefined class-based exceptions. This happens especially in all situations, in which before release 6.10 catchable runtime errors were triggered.

• The exceptions of all exception classes visible in a program can be triggered with RAISE EXCEPTION.

• Class-based exceptions can be declared in the interface of procedures. For local procedures, you use the addition RAISING of the statements METHODS and FORM for it. In the Class and Function Builder, you select exception classes when defining exceptions in the interface. The declared exceptions can occur at the call position of a procedure if the exception is not treated in the procedure.

When an exception is triggered, an exception object is created, whose attributes contain information on the error situation. A class-based exception can be treated in a TRY controll structure. Within the TRY, a protected area is defined, whose exceptions can be treated in subsequent CATCH blocks. Because all exception classes are subclasses of common superclasses, also the related exceptions can be treated in common by treating the respective superclass. The system propagates the exception object or the class-based exception until the exception is treated or an interface is violated.