SAP Note 18049 - General: Error message or program termination

Symptom:

You are looking for the cause of an error message or program termination. The present information does not give a note which applies here.

Cause and prerequisites

Still unknown.

Solution

The following information can be very helpful when searching for the cause:

Information on calling the function or the screen
---
Please use SAP terms when describing the process (function names in menus, pushbuttons, and so on). This will facilitate the searching for notes.
Please note the system status (menu call: System - Status) directly before the error occurs. The following is important for the analysis of application problems:

• SAP version

• Transaction

• Program name (screen)

• Screen number

• Program name (CUA)

• CUA status
  

If the error occurs in a dialog box (popup, without menu), note this information already in the primary window, that is, the last window in which the system menu is still available, and specify the path (function calls) on which you get to the dialog box. The window title could also be helpful.

Information on error and error cause in the case of error messages
---
Please always specify the complete error number in the case of error messages. It consists of two-character message ID and a three-character message number and is displayed when calling the (F1) help for the message (for example, "Message number CJ001").

The position in the program and the calling hierarchy are also helpful for analyzing the problem:
Activate the debugger mode by entering /H in the OK code on the last screen before the error occurs. After calling the function or after pressing ENTER, choose
Breakpoint - Breakpoint at - For key word in the debugger menu
and enter 'Message' as key word.
Continue the program execution using the function "Continue".
The debugger now stops when the error message is issued.
Write down the Include name, the line number and a command, if necessary, directly before the message statement.
Choose the calling hierarchy with "Goto - Active calls" and write down the calls given there (perhaps the first 10, if there are a lot).

Information on program terminations
---
Specify the raise exception (RAISE_EXCEPTION) in the case of a program termination. It is given at the beginning of the short dump. Please refer to the section "Notes on the error recovery" for key words on how to find notes.
Other important information is contained in the sections
User, transaction...
Information on where the termination occurred
Excerpt source code and
Active calls / Events

With transaction ST22 (Monitoring - Dump analysis) you can analyze short dumps of program or update terminations subsequently.

Information on update terminations
---
You usually receive an express message in the entry (office), if the update terminates. Please analyze the error as follows:

Tools - Administration
Monitoring - Update

Call the overview of the update records by pressing ENTER and choose the entry by double-clicking on it.
Note the module marked as incorrect in the overview and choose it by double-clicking on it.
Note the message number and the error text (screen "Status").
Branch to the "ABAP/4 Short dump", if possible, and get the above mentioned items of information from there (see "Information on program terminations").