V1 and V2 Update Function Modules
Use
An update is divided into different modules. Each module corresponds to an update function module.
There are various types.
-
V1 modules describe critical or primary changes; these affect objects that have a controlling function in the SAP system, for example, creation of orders and changes to material stock.
-
V2 modules describe less critical secondary changes. These are pure statistical updates, for example, such as result calculations.
-
There are also collective runs for function modules that are frequently used.
Differentiating between update components according to priority lets the system process critical database changes ahead of less-critical changes.
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. V1 updates are executed under the SAP locks held by the transaction that generated the update. This ensures data consistency; concurrent changes to the objects to be updated are not possible.
V2 updates are executed together in a separate LUW. They are not executed under the locks held by the transaction that generated them. If your SAP System contains a work process for V2 updates, these are only carried out in this system. Otherwise, the V2 components are processed by a V1 update process.
All V1 modules of an update must be processed before the V2 modules.
Example
Assume that a transaction makes dispositive changes to a material and to a financial balance. It also updates two sets of statistics.
Each of these changes is represented by an update module (update function module call) in the update request - the two dispositive changes by a V1 update module (time critical), and the statistical changes by a V2 update module (less critical).