Application Development Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 

V1 and V2 Update Modules

Go to solution
Former Member

‎07-02-2007 6:50 AM

0 Kudos

Hi All

what are <b>v1 update modules</b> and <b>v2update modules</b> in SM13??

urgent..

reward for sure...

regards

dinesh

1 ACCEPTED SOLUTION

Go to solution
Former Member

‎07-02-2007 6:58 AM

0 Kudos

Hi,

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

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

<b>Reward points</b>

Regards

3 REPLIES 3

Go to solution
Former Member

‎07-02-2007 6:58 AM

0 Kudos

Hi,

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

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

<b>Reward points</b>

Regards

Go to solution
Former Member

‎07-02-2007 7:14 AM

0 Kudos

there are 2 types of updates

V1 and V2

the most important update will go to V1 update

not critical things go to V2 update

V1 update will run using locks

V1 update can restart or not restartable

this can be set in the attributes of Function module

if there is any error in V1 update, lock will be deleted

only after completing the V1 update, the V2 will start