Analyzing ABAP Runtime Errors

Prerequisites

Analysis of dumps in the debugger is not available in SAP NetWeaver Release 7.x systems.

The program that you are running has just aborted because of a run time error and has written an ABAP 'short dump'.

This section shows you how to display the dump and use it to do a post-mortem analysis of the problem.

Tip

See more background information on the SAP Community Network (SCN):

If an ABAP program that you have started from the ABAP Development Tools fails with a short dump, then the system responds by displaying a dialog like this one:

The dialog appears outside of the ADT window and also automatically fades out. Keep an eye out for the dialog if you are testing a new program.
Click on Debug to do a post mortem analysis of the problem in the debugger.

The program is dead, so you cannot run it at all in the debugger. However, all of the variables and other runtime information in the program context are available for you to look at. See the Debugging ABAP Code for more help.
Click on Show to display the ABAP dump.

The dump is displayed in transaction ST22 in the integrated SAP GUI.

You can use the debugger to inspect a dump only if you have started an ABAP program (executable program, class, ...) from the ABAP Development Tools, and it has aborted with an ABAP dump. Only in this dialog use case – in which you are still connected to the program context – can you view an ABAP dump in the debugger.
The system notifies you of a short dump even if the dump occurs while you are running ABAP Unit. ABAP Unit catches dumps and reports them as errors rather than terminating. Even so, the system lets you intercept and analyze a dump that occurs during unit testing.