Update Administration

There are two types of updates:-

• Critical update- V1
• Non-critical update- V2

Update management supports different statuses for update requests. These statuses are displayed in Update Management (transaction sm13) in the column Status.

The status indicates the phase of the update process that the request has reached, or in which the request has become “stuck”. The background of the status field can be green (not yet processed, currently being processed), yellow (not yet processed, probably “stuck”), or red (terminated with error). The column Info provides further information.

The most important statuses are described below.

As already discussed in the section entitled The Update Process, the dialog work process passes the update request onto an update work process after the dialog area has been completed. This then processes the V1 update modules. When the ABAP statement COMMIT WORK is received, the data is written to the database and the V2 update is output to a V2 work process (providing V2 modules exist in the update request).

The following statuses are possible during this phase:

Status	Phase
initial	The update request has been created, but has not yet been completely processed. (This status applies from the moment the dialog work process transfers the update request to the update work process to the COMMIT in the update work process).
Error	An error occurred in the init phase, which prevents the update from being carried out.
Error (no retry)	The update request has been canceled and the update cannot be repeated.
V1 processed	The init phase has been successfully completed, and the V2 modules are being passed on for further processing. If no V2 modules exist, this update request no longer appears in the overview.
V2 processed	The V2 modules have also been processed correctly, but there is still a collective run (can be regarded as V3) to be carried out. If there is no collective processing to be carried out, this update request no longer appears in the overview.
processed	If the parameter rdisp/vb_delete_after_execution is set to 2 – in other words, if automatic deletion is deactivated – an update that has been successfully completed has the status ok. If automatic deletion is activated (default), the update record no longer appears in the overview.
to delete	This update request has been marked for deletion.
Enqueues deleted	The SAP locks belonging to this update request were manually deleted (SM12).