Error Handling and Data Consistency (SAP Library - Updates in the SAP System (BC-CST-UP))

Error Handling and Data Consistency

In order to ensure the consistency of the data, the update of an SAP transaction must be carried out in full or not at all. This is referred to as a rollback requirement. If a runtime error occurs in part of the update, all of the critical database changes made as a result of the update must be reversed. Less critical changes cannot be made.

With update bundling and the SAP lock system, the SAP Update System ensures that the data remains consistent (see also The Update Process).

The following section describes how the Update System responds if part of the update (V1 or V2) is canceled due to a runtime error. Various scenarios are possible here.

Cancelation in a V1 function module ( IN UPDATE TASK requested)

Updates already made for V1 functions are reversed.

All other update task requests (V1, V2 or collective run) are discarded.

The user receives an express mail indicating that the update was unsuccessful (see parameter rdisp/vbmail)

Cancelation in a V2 function module ( IN UPDATE TASK requested)

Updates already made for V2 functions are reversed.

Updates already made for V1 functions are not reversed.
An error message appears on the screen if the system has been configured for this.

Cancelation in a collective run function module

Collective runs are handled in the same way as V2 update modules.

See also:

Error Handling with Bundled Updates