WHT ARE V1 AND V2 UPDATE FUNCITON ?

[Former Member]

i want to knwo the differance between v1 and v2 update ?

[Former Member]

Hi,

Please refer to this.

http://help.sap.com/saphelp_nw04s/helpdata/en/e5/de86f335cd11d3acb00000e83539c3/content.htm

Thanks,

Anitha

[Former Member]

Hi

V1 and V2 Update Modules

An update is divided into different modules (see also Update Request). Each module corresponds to an update function module.

There are two types of module.

The SAP System makes a distinction between primary, time-critical (V1) and secondary, non-time-critical (V2) update modules. The system also supports collective runs for function modules that are used on a regular basis.

This distinction allows the system to process critical database changes before less critical changes.

V1 modules describe critical or primary changes; these affect objects that have a controlling function in the SAP System, for example order creation or changes to material stock.

V2 modules describe less critical secondary changes. These are pure statistical updates, for example, such as result calculations.

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 (see The SAP Lock Concept). 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.

Let us assume that a transaction makes planning changes to a material and balance sheet, and updates two sets of statistics.

Each of these changes is represented by means of an update module (call update function module) in the update request - the two planning changes by a V1 update module (time critical), and the statistical changes by a V2 update module (less critical). (The V1 modules have priority, although the V2 modules are usually also processed straight away).

Reward points for useful Answers

Regards

Anji

[former_member196299]

hi ,

V1 update module generate update requests in table VBLOG in synchronous mode and in asynchronous update in main memory .

V2 update module generates requests in table VBLOG and always run asynchronously .

V1 update functions are handled by the system asynchronously,synchronously and in lolal where as V2 update functions are always handled by the system asynchronously .

Reward if helpful !

Regards,

Ranjita

[Former Member]

The SAP update concept has two priorites for function modules which run in the update task: Start immediately (V1 function modules) and Start delayed (V2 function modules). If all V1 function modules have been successfully processed, the update program deletes all ENQUEUE locks specified by the transaction. This means that the V2 function modules cannot rely on the locks set.

CALL FUNCTION function IN UPDATE TASK

With this statement, the function module function is registered so that it can be executed by an update process on encountering the next ABAP/4 command COMMIT WORK. In this case (i.e. asynchronous processing), the dialog process does not wait until the function module has been executed. However, with COMMIT WORK AND WAIT (i.e. synchronous processing), the processing does not continue until the function module has finished. All function modules specified as "Update with immediate start" or "Immediate start, no restart" (in short V1) are executed together in one LUW. All function modules specified as "Update with delayed start (in short V2 are executed in a separate LUW. The type V2 is mainly used for less urgent database updates (e.g. of a statistical nature).

I hope it helps

Check this http://help.sap.com/saphelp_nw04/helpdata/en/e5/de86f035cd11d3acb00000e83539c3/content.htm

Regards