V1 versus V2 update

[Former Member]

I need to know the difference between V1 and v2 update in simple terms.

Any pointers.

[Former Member]

Hi,

V1 update is primary..which will be triggered immediately...in the function module attributes..You will choose start immediately..

V2 updates are secondary..Which is not time critical..in the function module attributes..You will choose the radio button Start delayed..

Check this link for more details..

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

Thanks,

Naren

[Former Member]

Hi,

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.

Regards,

Younus

<b>Reward Helpful Answers:-)</b>

[Former Member]

Hi,

V1 updates are time critical updates

V2 updates are not so time critical

so if you have a series of V1 & V2 updates a V2 update will trigger only after the completeion of V1 updates.

Regards,

gaurav

[Former Member]

hi sv,

check this,

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).

regards,

seshu.

[former_member214288]

Hi,

An update is V1 Update if it is done in the same internal session - for example doing an update in FM and calling that FM in Update Task or Calling that FM using RFC Destination (of the same system). LUW will still be the same here.

An update is V2 Update if it is done in an external session - for example Calling FM starting new task. This will be a separate LUW.

Reward points if helpful.

Regards,

Ram