Question on function moodule.

[Former Member]

Update function modules are classified as v1 or v2, which type of update is performed first and what mode ( Asynchronous, synchronous or locally ) can each type be processed?

[Former Member]

Hi Dinesh,

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

More details at http://help.sap.com/saphelp_nw04/helpdata/en/e5/de86f335cd11d3acb00000e83539c3/frameset.htm

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

http://help.sap.com/saphelp_47x200/helpdata/EN/41/7af4d4a79e11d1950f0000e82de14a/frameset.htm

Regards,

Priyanka.

[p291102]

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

Thanks,

Sankar M

[Former Member]

Hi Dinesh,

To be able to call a function module in an update work process, you must flag it in the Function Builder. When you create the function module, set the Process Type attribute to one of the following values:

Update with immediate start

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.

Update w. imm. 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.

Update with delayed start

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.

Reward points if helpful.

Regards,

Hemant

[Former Member]

hi

good

go through this link,hope help you to solve your problem

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

/people/aditya.palekar/blog/2006/12/03/how-to-carry-out-pricing-using-abap-function-module-pricing

thanks

mrutyun^

[Former Member]

Thanks alot for your help,

Priyanka Neelam

Sankar M

Hemant Goyal

Mrutyunjaya Tri...

Regards,

Dineshbabu.