V1 and V2 updates in SAP
- in ABAP
1/17/2016 1:20:06 PM
V1 and V2 updates in SAP-V1 and V2 Update Function Modules, the SAP System makes a distinction between primary, time-critical (V1) and secondary, non-time-critical (V2) update modules. The V1 modules are processed consecutively in a single update work process on the same application server. These belong to a single database logical unit of work (LUW) and can be rolled back. V2 updates are executed together in a separate LUW. They are not executed under the locks held by the transaction that generated them
When you create the SAP function modules, set the Process Type attribute to one of the following values:
1. Update with Start immediate
Set this option for high priority ("V1") functions that run in a shared (SAP LUW). These functions can be restarted by the update task in case of errors.
2. Update with immediate start start, No Restart
Set this option for high priority ("V1") functions that run in a shared (SAP LUW). These functions may not be restarted by the update task.
3. Update with Start Delayed
Set this option for low priority ("V2") functions that run in their own update transactions. These functions can be restarted by the update task in case of errors.
4. coll. run
- For internal use only -
A number of similar function modules that previously used to run individually in the V2 update process can be grouped together and run collectively.
The V1 modules are processed consecutively in a single update work process on the same application server. This means that they belong to the same database LUW and can be reversed. Furthermore, V1 updates are carried out under the SAP locks of the transaction that creates the update. This ensures that the data remains consistent; simultaneous changes to the objects to be updated are not possible.
All V2 updates are carried out in a separate LUW and not under the locks of the transaction that creates them. If your SAP System contains a work process for V2 updates, these are only carried out in this work process. If this is not the case, the V2 components are processed by a V1 update process.
All V1 modules of an update must be processed before the V2 modules.