Display Update Header
Use
The update header is used to manage update requests.
Prerequisites
You are on the Update Requests screen.
Procedure
-
Position the cursor on the update request.
-
Choose or
.
The update header screen contains the following information:
|
Field |
Meaning |
|---|---|
|
Update Key |
Key under which an update request is stored as a data record in the database. Abnormal terminations in update processing are recorded in the system log with the update key. The express mail that informs you of the canceled update also contains this key. Compare the key in the express mail or in the system log with the value in this field to make sure that you have found the correct update record. |
|
Client |
Client to which the user is logged on. |
|
User |
User who triggered the update |
|
Language |
Language in which the user is logged on |
|
Account |
The Account field is currently not used. |
|
Report |
ABAP report with which the update was created |
|
Transaction |
Transaction that called up the ABAP program |
|
Enqueue key |
The key of the lock entries created by the transaction which generated the update. The update task holds the locks until the V1 update has been successfully completed. The locks are canceled if an update error occurs (symbol |
|
Context |
Language that the update server has to support for this update request. You can display the contexts of the update server(s) in your system by choosing Display Update Server. |
|
Information |
Bit mask that contains further information on the update request. The default value is 1 (standard update request). 2 means that this request is from the batch input, and must not be restarted manually. |
|
Update RC |
Update return code (for error analysis) |
|
Status |
Detailed description of status |
|
Update server |
Update server on which the update request was processed |
|
UD Client |
Update server on which the update request was created |
|
Local time zone |
Local time zone |
|
Time Offset |
Difference between local time and system time |


).