Analyzing and Correcting Update Errors (SAP Library - Updates in the SAP System (BC-CST-UP))

Analyzing and Correcting Update Errors

Purpose

Before you can correct update errors you have to know their cause. Different problem types exist.

There are various means of obtaining more detailed information and of analyzing the problem:

Information displayed in Update Management and in the system log

Test the canceled update

Error cleanup in the canceled update in test systems

If the error involves a problem affecting the entire system (a database problem, for example), further analysis is probably not required. You can assume that the update problem will be resolved when the system error is eliminated. Canceled updates can be repeated (see Repeating Canceled Updates).

Prerequisites

To be able to view the error message in the system log, you have to be logged onto the server on which the error occurred. You can determine which server this is as follows:

If an alert was displayed for the update error, click the pushbutton Appl. server next to the message.

If you found an update record with the status Error in Update Management, choose Display update header to display the name of the update server. To log on to the server, use the function SAP Server (transaction SM51).

Process Flow

Error Information from Update Management

Begin by viewing the update record ( Selecting and Displaying Updates). Canceled update records have the status Error . Note the time when the cancelation occurred. You will use this to find the relevant message in the system log. Select the canceled update (by positioning your cursor on it), and choose This graphic is explained in the accompanying text Modules.

The update modules (function modules) along with the processing status are listed. Select canceled update modules (status Error ) one at a time, and display the relevant error information by double-clicking (or by choosing the update header This graphic is explained in the accompanying text ) in the dialog box Update Module Status. Depending on the error, you have access to the error message issued (with the point at which the error occurred), or to the ABAP short dump (raise exception) generated when the error occurred.

The following information is output in Update Module Status.

Where the error occurred: The system outputs the name of the function module and of the program element in which the error occurred and the relevant line number directly on the screen. In this case, click This graphic is explained in the accompanying text

This graphic is explained in the accompanying text

to open the ABAP editor. The line in which the termination occurred is usually located one or two lines above the selection in the editor. If a message of the type "A" is located here, click it to view the text.

Alternatively, you find an ABAP short dump. The short dump contains the location where the error occurred together with additional information on the cause of the error. To display the dump, click This graphic is explained in the accompanying text .

Note

In rare cases, the SAP System does not supply this information. For instance, information on the error location may not available in the ABAP Editor following a termination in the update work process.

Why the error occurred: As mentioned above, an error message or an ABAP short dump with information on the update error is displayed.

If an error message is output in the field Error text, proceed as follows: To view the documentation on the message, test the update ( Testing Canceled Updates), and click the error message when it is output. You can also view the documentation via table T100 (using transaction SM31). (Use the first two characters of the error number in the field Error text for message class or ID. Enter the next three digits for the message number).

If a short dump (RAISE EXCEPTION) is available: Click on ABAP short dump to view a clarification of the problem and detailed information on the processing status when the error occurred. For further information on short dumps, see ABAP Development Workbench: Tools.

Note

Short dumps are not always available. For instance, a short dump is not generated if an update function module is ended with the ABAP statement MESSAGE TYPE A.

Error Information from the System Log

Check the system log for messages pertaining to the premature cancelation. To do this, choose Tools ® Administration ® Monitor ® System log. Alternatively, enter transaction code SM21 . In the system log, select entries that were created at approximately the time of the update error. For more information about the system log, see System Logs.

Search for a message of the following type:

Msg No . R65: Update was canceled VB-RC: 9

> Update key : < Date and timestamp >< Update ID>

> Update module : <Name of update function module >

The message frequently appears in conjunction with the following messages:

Execute transaction termination.... and/o r rollback .

To view the message sent to the user, click the message number after Transaction termination (if available).

Also read the messages before and after those listed above to obtain further information on the problem.

Note

You must be logged onto the application server on which the update error occurred. If central logging is not available, or not active in your SAP System, the relevant messages do not appear in the system log.

Result

You have found the cause of the error, or further delimited the error. If this error occurs frequently, you can summarize the acquired information in an SAPNet – R/3 Frontend problem message, and send it to SAP.

See also:

Repeating Canceled Updates

Displaying Users, Transactions and Data from Updates

Problem Types

Reporting Update Problems

Automatic Update Stop in the Event of Database Problems