ABAP Keyword Documentation →  ABAP − Reference →  Program Flow Logic →  Exception Handling 

Runtime Error

Runtime errors identify situations in which the system cannot continue running an ABAP program and has to terminate it. Runtime errors can occur in one of the following situations when ABAP programs are executed:

• Non-handled exceptions:

• A handleable exception is not handled.

• A non-handleable exception is raised.

• Program-driven raise:

• The statement RAISE SHORTDUMP or the addition THROW SHORTDUMP is used.

• An assertion fails.

• An exit message or message of type X is sent.

Each runtime error is identified by a name and assigned to a specific error situation. Each runtime error produces a database rollback. Following a program termination caused by a runtime error, the system displays a short dump which indicates the name of the runtime error, the associated exception class, content of data objects, active calls, control structures, and so on, and allows the user to navigate directly to ABAP Debugger. Short dumps are kept in the system for 14 days by default and managed using the ABAP dump analysis (transaction ST22). The output of the short dump can be changed in the profile parameter rdisp/verbose_level if there are special requirements.

Other versions: 7.31 | 7.40 | 7.54

Note

If a program-driven termination of a program is needed in situations where it is not a good idea for the program to continue, it is best to use RAISE SHORTDUMP, THROW SHORTDUMP, or ASSERT from now on and avoid using exit messages.

Example

Raises the runtime error COMPUTE_INT_ZERODIVIDE when the exception CX_SY_ZERODIVIDE is not caught.

cl_demo_output=>display( 1 / 0 ).

Continue

RAISE SHORTDUMP