Error Handling and Data Consistency
Use
In order to ensure the consistency of data, the update of an SAP transaction must be carried out in full or not at all. This is known as the “rollback requirement”. In the event of a runtime error in one of the components of an update, all of the critical database changes made by the update must be rolled back.
With update bundling and the lock system, the SAP update system ensures that data remains consistent.
The following list shows how the update system reacts if any component (V1 or V2) of an update fails due to a runtime error. There are various reasons for a failure.
Termination in a V1 Function Module
If the termination occurs in a V1 function module (requested by IN UPDATE TASK), the system responds as follows:
-
Updates already executed for V1 functions are rolled back.
-
All further update task requests (V1, V2 or collective run) are rejected.
-
The user receives an express mail that the update has failed (parameter rdisp/vbmail).
Termination in a V2 Function Module
If the termination occurs in a V2 function module (requested by IN UPDATE TASK), the system responds as follows:
-
Updates already executed for V2 functions are rolled back.
-
Updates already executed for V1 functions are not rolled back.
-
An error message appears on the screen, if your system is set up to send them
Termination in a collective run function module
If the termination occurs in a V2 function module (requested by IN UPDATE TASK), the system responds as follows:
-
Collective runs are handled like V2 update modules.
More Information
Error Handling with Bundled Updates