Update Mode of Function Module

[Former Member]

Hi all,

The detailed knowledge of SAP techniques is so much ........

Nowadays I encountered one,which is the 'Update Mode' attribute of a function module.when we create

a function ,we will find the attribute is set as 'Start Immed' by default. But actualy I don't know the meaning

of this attribute. According to some material info.,I learnt that it can be classified into two:v1 & v2.

Would you tell me the true meaning of 'Update MOde' and the distinction between V1 and V2.

Thanks a lot.

[Former Member]

Please chek following links.

http://abapcode.blogspot.com/2007/09/update-techniques-asynchronous-and.html

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

Thanks,

[matt]

Function modules with the update module radio button set can be run in the update process. As V1 function modules are called, they are placed in a queue. When the commit work happens, which triggers the update process, all the V1(immediate start) FM will run, in the order they were called. After that, any V2 "Start Delayed" FM will run.

V3 FM are triggered by (usually) a batch job.

matt

[kell_vagtholm1]

Hi Matthew

If I use 'Collective run' how do I define the background job to handle it?

Or does it already exist on the system.

Best regards

kvagtholm

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

U can also refer these links:

http://www.erpgenie.com/abaptips/content/view/498/62/

http://www.allinterview.com/showanswers/5513.html

Thanks

Vasudha

[Former Member]

hi,

Calling a FM in Update Task is one of the bundling techniques used in ABAP to avail functionality provided by SAP Update System. Here all database updates are processed at the end of the SAP LUW in contrast to normal FM call where the database updates are done and commited at the time of call (Database LUW). It is necessary to bundle all your database updates in an SAP LUW e.g. all database updates in a transaction (like VA01) should be bundled. Almost all standard SAP transactions use bundling techniques.

V1 and V2 are workprocesses in which corresponding update bundles (by using calls to corresponding update FMs) are executed.

V1 is for primary updates (like txnl tables) while V2 is used for secondary (eg statistical LIS) updates.

You call an update FM in such task with

"call function ' ' in update task ..."

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