Categories of ABAP Runtime Errors

An ABAP program can be terminated during its runtime for a number of different reasons. The database table SNAPTID lists all potential runtime errors (in total, around 1900).

To allow clearer processing, the runtime errors are divided into categories. The category of the runtime error returns hints on cause of the error and troubleshooting.

Internal Kernel Error	Error in ABAP Kernel.  RECOMMENDATION Sending an error message to SAP.
Errors in the ABAP runtime Errors in the screen runtime Errors in the database interface	The system was able to roughly determine the area in which the error occurred. Next, clarify whether it was triggered by an internal error or by a programming error.
ABAP programming errors	Errors in the ABAP program, such as a division by zero or a catchable exception that was not caught.  RECOMMENDATION If you are dealing with a non-modified SAP application, send an error message to SAP.
Installation errors	These include, for example, inconsistencies between the kernel and the database.  EXAMPLE A typical installation error is the error START_CALL_SICK.
Resource bottleneck	EXAMPLE Example: SYSTEM_NO_ROLL: The application does not have enough memory available.
External errors	The error was caused by a call outside the system.  EXAMPLE The code page of the operating system does not match the SAP system language An incorrect logon attempt occurred when calling outside the SAP system (for example, RFC SDK).
End user errors	Incorrect printer settings at end user.
No error	The program was not terminated due to an error, but rather due to deliberately performed actions.  EXAMPLE If an administrator cancels a running transaction, the runtime error SYSTEM_CANCELED is thrown.
ST runtime errors	The error occurred during a Simple Transformation (ST). The cause is a programming error in the ST program.
Internal ST errors	The error occurred during a Simple Transformation (ST). There is an internal error in the ST VM.
XSLT runtime errors	The error occurred during the execution of an XSLT transformation.
ITS errors	The error occurred in ITS. This is usually an HTMLB error.

Managing ABAP Short Dumps

A short dump is saved in the database table SNAP in the error log for every runtime error that occurs in an ABAP system. Unless they are intended for retention and marked accordingly, these long texts are automatically released for deletion one week after they are generated.

The deletion of old short dumps takes place successively: If a program that is running in a window of the SAP GUI terminates with a runtime error and the short dump is displayed directly then older short dumps are searched and deleted (maximum 100 for performance reasons). The number of short texts not intended for retention in an ABAP system is therefore regularly regulated.

Manually Reorganizing Short Dumps

This mechanism does not apply, however, if a runtime error occurs during background processing, an RFC call (including JCo), or an HTTP call. It is therefore also possible, to selectively manually delete short texts from the database. To do this, on the initial screen of the transaction ABAP Dump Analysis (ST22), choose the Goto menu and the Reorganize option.

A selection screen appears, on which you can define the age as of which the short texts are to be deleted.

Reorganization as Automatically-Scheduled Operation (by the System Administrator)

If you need to regularly perform reorganization operations in a system and want to automate this step, you can schedule the program RSSNAPDL. This program provides the same function as the menu option Reorganize.

You can view the current size of table SNAP at any time by choosing the SNAP Statistics option from the Goto menu.

Stopping Short Dumps from Being Automatically Deleted

You can stop a short dump from being deleted automatically. Start the ABAP Dump Analysis (St22) for this and select the related runtime error. Choose  Runtime Error  Save/Release  from the menu. The short dump is then stored in the database until you revoke the lock using the same function.

ABAP Dump Analysis (ST22)

You can use the tools of the ABAP dump analysis (ST22) to list the ABAP runtime errors that have occurred in an ABAP system as well as the relevant short dumps.

• Displays and analyzes update statistics again

• Save in a local file

• Print

• Store for a longer period of time

  
  

Listing and Selecting Runtime Errors

To list the runtime errors that have occurred:

• Log on to the affected ABAP system.

• Start the ABAP Dump Analysis using transaction code ST22.

• On the initial screen, you can define the Selection Criteria that is searched for the whole list of stored runtime errors.

• A list appears of all of the runtime errors relevant to the selection criteria. You can sort the list according to various criteria.

  
  

  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.

Displaying Long Texts of Runtime Errors

You can open the long text of a runtime error for Detailed Review with a double click.

Alternatively you select the runtime error in the list and choose

 Runtime Error  Display Long Text 

or  (Display Long Text F2)

Unedited Display

In case of this, you can display the unformatted related short dump. Follow the procedure below:

Select the runtime error in the list. Choose

 Runtime Error  Unformatted Display 

or  (Unformatted Display F9)

Stopping Short Dumps from Being Automatically Deleted

Select the runtime error in the list. Choose

 Runtime Error  Save/Release Ctrl + F1 

or  (Save/Release Ctrl + F1)

Emergency Solutions for Displaying Short Dumps

The ABAP Dump Analysis uses SAP technologies as in ALV. It brings a higher level of usability but also a higher level of dependency.

Should transaction ST22 (ABAP Dump Analysis) not start correctly or if short dumps are not displayed correctly then there are two emergency solutions that you can implement. You can then continue to analyze problems with the help of short dumps.

First Emergency Solution: On the ST22 start screen, select the Use Old Dump Analyses option before you list the short dumps. ST22 then switches to the old list technology for displaying dumps.

Second Emergency Solution: If you cannot start transaction ST22, you can display short dumps in a simplified list form using report RSNAPREAD.

To use RSNAPREAD, proceed as follows:

1. Start transaction SA38or SE38.

2. Run the report RSNAPREAD. Enter a date for selecting short dumps

   RSNAPREAD gives a list of the short dumps that were created for the specified date.

3. Open the short dump you want to view.

   For technical reasons, RSNAPREAD is simply able to display the technical paragraphs from the short dump. You can, for example, view contents such as Contents of System Fields or Selected Variables in the list display.

   However, all headers are missing and all contents generated by ST22 with its section from the source text, such as the introductory texts about the error or the Termination Information paragraph.

Setting timezone in SAP EP