Show TOC

Runtime Error Long TextLocate this document in the navigation structure

Use

If a runtime error occurs while executing an ABAP program, then an error log ( Short Dump ) is created. When displaying the technical short dump, a long text is created and displayed that is easier for the end user to read. You can print or locally save the long text that is displayed. You can, for example, send it as an attachment to an error message.

Display Structure

The long text of a runtime error contains a lot of information. Most of the sections of the long text are helpful for different people, depending on their technical knowledge. The display, therefore, is structured.

Note

Depending on how far down you scroll in the display, you can see more detailed and technical information.

The display is comprised of the following areas:

  • Header rows (top)

  • The long text - divided into sections (header area of display)

  • Navigation area (left)

    The navigation area is only available in transaction ST22.

The header rows identify the runtime error that occurred and offer hints for the cause of the error and troubleshooting. The following header rows are always provided:

  • Name of the runtime error

  • Date and time

  • Category of runtime error

The number of header rows is variable. More information is displayed as required depending on the category of the runtime error, program type, and circumstances that lead to the program termination:

  • Exception that lead to runtime error

  • Name of ABAP Program

  • Name of BSP Application

  • Name of the Web Dynpro Component

  • Application Component

Recommendation

If an application component appears in the header rows, you should report the problem to SAP. Send an error message to SAP using the specified application component.

Otherwise you could probably solve the problem without the support of SAP.

The navigation area (only available in transaction ST22) offers a tree-like structure that makes navigation easier in the long text. The sections of the long text are dividied into blocks that are relevant for the following groups:

  • End users

  • ABAP developers

  • SAP employees

You can go directly to the relevant sections of the long text by double-clicking them.

There are the following blocks:

System Environment

The sections in this block list general information about the technical conditions of the environment in which the termination occurred. As well as the relevant system data, this includes information about the relevant user and the transaction executed at the time of the termination.

User View

This block is relevant for the end users of an SAP system. The user view is for the end user. It summarizes the cause for the termination for program users without ABAP developer-level knowledge. If possible, the What can you do? section suggests possible solutions for which no changes to the ABAP source code are required.

ABAP Developer View

This block is for ABAP developers . If the problem that led to the termination of the program can be solved by making changes to the ABAP source code, the responsible application developer can find the information required to do so in this block. All information that is relevant to the source code of the terminated program and possible solutions is shown here.

This section also contains information about terminations that occurred due to incorrect system configuration. (for example: A required RFC destination is missing). Problems of this kind can usually be solved by the system administrator .

Note

In most cases, the section How to correct the error contains all of the required information and you should therefore read it carefully.

BASIS Developer View

These sections are only relevant for SAP developers and SAP Support.

Additional Functions

Printing and Saving

The display is a classic list. All functions of the classic list display are available to you. You can print or locally save the long text that is displayed. You can then send it as an attachment to an error message.

Open the System menu. Select the relevant entry:

  • Start of the navigation path List Next navigation step Print End of the navigation path

  • Start of the navigation path Liste Next navigation step Save End of the navigation path

The program opens in the Editor

You can display the source code for the affected program by branching to the Editor. To do this, select

Jump to Affected Program F7

Unedited Display

In case of this, you can display the short dump. To do this, select

Start of the navigation path Runtime Error Next navigation step Unedited Display End of the navigation path or Unedited Display F9

More Information