Get Example source ABAP code based on a different SAP table
Runtime Errors Runtime errors indicate situations in which the execution of an ABAP program cannot be continued but must be terminated. Runtime errors can occur in one of the following situations when ABAP programs are executed:
Non-handled exceptions:
A catchable exception is not handled.
A uncatchable 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 and leads to a database rollback. Following a program termination caused by a runtime error, the system generates a short dump which contains 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 branch directly to the ABAP Debugger. Short dumps are kept in the system for 14 days by default and managed using the ABAP dump analysis BEGIN_SECTION VERSION 5 OUT (transaction ST22). The output of the short dump can be controlled in the profile parameter rdisp/verbose_level if there are special requirements. END_SECTION VERSION 5 OUT
Latest notes: NON_V5_HINTS Program-driven termination of a program should be implemented in situations where meaningful program execution is no longer possible, using RAISE SHORTDUMP, THROW SHORTDUMP, or ASSERT from now on and not using exit messages. ABAP_HINT_END
ABAP_EXAMPLE_VX5 Raising of the runtime error COMPUTE_INT_ZERODIVIDE when the exception CX_SY_ZERODIVIDE is not caught. cl_demo_output=>display( 1 / 0 ). ABAP_EXAMPLE_END
