Analyzing and Correcting Update Errors 
Before you can fix an update error, you need to find out what went wrong. There are various Types of Problems.
There are the following ways to get information about the problem and to analyze it:
Display information in the update manager and in the system log
Test the canceled update
Debug the canceled update in test systems
If you have just had a system-wide problem, such as a database problem, then no further analysis is necessary. You can assume that correcting the system problem has also corrected the update problem. You can re-process canceled updates.
Prerequisites
To display the error message in the system log, you must be logged on to the server where the error occurred. To find out which one, proceed as follows:
If an alert is shown for the update error, choose 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 Overview of SAP Application Servers (transaction SM51).
Procedure
Error Information from the Update manager
First, display the update record. Canceled update records have the status Error. Note the time when the failure occurred for use in locating relevant messages in the system log. Select a canceled update with the cursor, and choose 
Modules (Update 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 
(Update Header)) in the dialog box Status of Update Module. 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: You will see either the name of the function module and the program element, and line number at which the error occurred directly on the screen. In this case, choose
(ABAP Editor) to open the ABAP editor. Usually, the line at which the error occurred is a line or two above the highlight in the editor. If a message of type A appears here, click it to view the text. Or you find an ABAP short dump. The short dump includes the position at which the error occurred as well as additional information on the cause of the error. Choose 
(ABAP Short Dump) to display the dump.
NoteIn rare cases, the SAP system does not supply this information. For example, after an error in the update work process itself, location information in ABAP may not be available.
End of the note.Why the error occurred: If an error message is displayed in the Error Info field, proceed as follows: You can display the documentation for the message by testing the update and clicking the error message when it is displayed (Testing Failed Updates). You can also display the documentation in table T100 (with transaction SM31). (In each transaction, use the first two characters of the error message in the Error text field as the Message class or ID. Enter the next three characters as the message number.)
If a short dump (RAISE EXCEPTION) is available: Choose ABAP short dump to display an explanation of the error, and information about the processing status at the time of the error.
NoteShort dumps are not always available. For example, no short dump is created if an update function module is terminated with the ABAP instruction MESSAGE TYPE A.
End of the note.
Error Information from the System Log
Check the system log for messages about the premature cancelation. To do this choose 
Tools 
Administration Monitoring System Log 
, or enter transaction SM21. Select system log records for the time period around the time of the update error.
Look for a message such as the following:
Msg No. R65: Update was aborted VB-RC: 9
> Update key: <Date and time stamp><update ID>
> Update module: <update function module name>
This message is often associated with the following messages:
Transaction aborted... and/or Perform rollback.
Click on the message number following Transaction aborted (if any) to display the message that the user received.
Check before and after these messages for other messages that may provide more information about the error.
Recommendation
Log on to the application server in 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 found the cause of the error, or narrowed down the error. If the error occurs often, you can write a customer message with this information and send it to SAP.