ABAP Dump Analysis 

Background

If an ABAP program ends up in a status during its processing that does not permit its continuation, this automatically results in an exception. Exceptions of this type are generated by the runtime environment and are completely integrated into the exception concept. There are essentially two types of exceptions:

Exceptions That Cannot Be Handled

Exceptions for which there is no predefined exception class lead directly to a runtime error. The execution of the program is terminated and a long text with all available information about the termination is stored in the system.

Exceptions That Can Be Handled

Exceptions that are assigned to predefined exception classes can be handled within the running program. If this is the case, the program can continue executing after it has handled the exception.

 

If an exception that can be handled occurs in an ABAP program and is neither handled nor propagated to a higher-level program, a runtime error also occurs in this case, and a long text is stored in the system.

 

Performing the Dump Analysis

If a runtime error occurred in your ABAP program, you can access and analyze the associated information. To do this, call ABAP Runtime Errors (transaction ST22) on the application server on which the error occurred.

On the initial screen, you can define the selection criteria for the list of runtime errors. It is very easy to call the most current runtime errors: if you choose the “Today” button in the Standard selection group box, the system displays a list of runtime errors for the current day in reverse chronological order – that is, the newest files first.

In any case, the system displays a list of runtime errors that match all of the criteria defined in your selection criteria. To select a runtime error for detailed review, double-click the corresponding line in the list.