Show TOC

ABAP Runtime Errors and Short DumpsLocate this document in the navigation structure

If an ABAP program encounters a runtime error (because of an uncaught exception, an exit message, or a failed assertion), the program writes an ABAP short dump to document the error and help in its analysis.

An ABAP dump provides a great deal of well-structured information for localizing and understanding a runtime error, including a textual description of the error and its likely cause, an excerpt showing the location of the error in the source code, tables of variables and their values, and more.

In addition, while the context of the failed program still exists, you can use the debugger to examine the 'remains' of the aborted program.

If a runtime error occurs in a program that you have started from the ABAP Development Tools (ADT, then the ADT alerts you of the runtime error with a small dialog window. From this dialog you can start the debugger to examine the short dump.

The ADT is able to present this dialog to you if an external request causes a runtime error in code that you own. For example, if a request from a browser causes an error in handler code that belongs to you, then the ADT alerts you to the error and gives you the chance to examine the error in the debugger.

You can also subscribe to an ABAP feed of runtime errors. While you cannot examine an error in the debugger from an entry in the feed, the feed has the advantage of providing you with a complete list of dumps. You can define filter conditions for selecting dumps for the feed.