topic Re: Difference between V1 and V2 updates in Application Development and Automation Discussions

Difference between V1 and V2 updates

Former Member — Fri, 09 Nov 2007 04:51:31 GMT

Hello,

Could u pls tell me the difference between V1 and V2 updates... and the differences between 4 different types of update function modules....

Thannx in advance..

Regards,

Maya.

Re: Difference between V1 and V2 updates

JoffyJohn — Fri, 09 Nov 2007 05:07:26 GMT

V1 updates are syncronous updates

V2 updates are asyncronous updates

please see the following link

<a href="http://help.sap.com/saphelp_nw04s/helpdata/en/e5/de86f335cd11d3acb00000e83539c3/content.htm">http://help.sap.com/saphelp_nw04s/helpdata/en/e5/de86f335cd11d3acb00000e83539c3/content.htm</a>

Re: Difference between V1 and V2 updates

JoffyJohn — Fri, 09 Nov 2007 05:14:42 GMT

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:

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

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

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

4. coll. run

- For internal use only -

A number of similar function modules that previously used to run individually in the V2 update process can be grouped together and run collectively.

The reasons for processing them collectively are as follows:

the data of all the calls are read and processed internally

database updates are not made until the internal processing is complete

For further information, refer to the ABAP/4 documentation under IMPORT FROM LOGFILE and UPDATE

Re: Difference between V1 and V2 updates

Former Member — Fri, 09 Nov 2007 06:31:17 GMT

Thank u John for ur response...

I want to know what does this mean - "These functions can be restarted by the update task in case of errors." for Update with immediate start...

Regards,

Maya.

Re: Difference between V1 and V2 updates

JoffyJohn — Fri, 09 Nov 2007 07:06:27 GMT

There are various types of work-processes.

A typical SAP system installation contains dialog work processes

and at least one update work process.

The update work processes are responsible for updating the database.

The primary step is called V1, the secondary step V2.

V1 has 2 option.

1) start immediately

2)Imediate start, no restart.

Restarting can be done in tcode:SM13 - Update

The V1 and V2 steps of a log entry are processed in separate database LUWs. The entries in the lock table are usually deleted once the V1 step has been processed. There is no locking for the V2 step. Dividing up the update process allows you to separate time-critical updates that require database locks from less critical data updates that do not need locks. V2 steps receive lower priority from the dispatcher than V1 steps. This ensures that the time- and lock-critical updates are processed quickly, even when the system is busy.

If an error occurs during the V1 processing, the database rollback applies to all V1 steps in the log entry. The entire entry is replaced in table VBLOG. If an error occurs during V2 processing, all of the V2 steps in the log entry are replaced in table VBLOG, but the V1 updates are not reversed.

The system marks rolled-back function modules as error functions in the update task log. The error can then be corrected and the function restarted later.

Re: Difference between V1 and V2 updates

JoffyJohn — Fri, 09 Nov 2007 08:10:58 GMT

This link has answer to all ur doubts

<a href="http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCCSTUP/BCCSTUP_PT.pdf">http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCCSTUP/BCCSTUP_PT.pdf</a>

Re: Difference between V1 and V2 updates

Former Member — Fri, 09 Nov 2007 08:44:37 GMT

Synchronous versus Asynchronous

Synchronous

With synchronous updating, we can check SY-SUBRC to determine the success of the transaction and the actual update to the database.

DO.

………

PERFORM FILL_BDC_TAB.

CALL TRANSACTION ‘FK02’

USING BDC_TAB

MODE ‘N’

UPDATE ‘S’.

IF SY-SUBRC < > 0.

WRITE: /‘ERROR’.

ENDIF.

ENDDO.

Asynchronous

With asynchronous updating, we can check SY-SUBRC to determine the success of the transaction only, not the actual update to the database.

DO.

………

PERFORM FILL_BDC_TAB.

CALL TRANSACTION ‘FK02’

USING BDC_TAB

MODE ‘N’

UPDATE ‘A’.

IF SY-SUBRC < > 0.

WRITE: /‘ERROR’.

ENDIF.

ENDDO.

use Asynchronous Update

Synchronous Update : This means say if u have 10 records to update and the processing is going on in a loop the Synchronous update will wait till each update is actually done in the data base and then it will move on the next record's updation.

Asynchronous : In This mode, the updates are lined one after the other and the system doesn't wait for the updates to actually happen. These updates are then triggered by an internally scheduled job which then actually updates the data in the databse.

Asynchronous updating. In this mode, the called transaction does not wait for any updates it produces to be completed. It simply passes the updates to the SAP update service. Asynchronous processing therefore usually results in faster execution of your data transfer program.

Asynchronous processing is NOT recommended for processing any larger amount of data. This is because the called transaction receives no completion message from the update module in asynchronous updating. The calling data transfer program, in turn, cannot determine whether a called transaction ended with a successful update of the database or not.

If you use asynchronous updating, then you will need to use the update management facility (Transaction SM12) to check whether updates have been terminated abnormally during session processing. Error analysis and recovery is less convenient than with synchronous updating.

Synchronous updating. In this mode, the called transaction waits for any updates that it produces to be completed. Execution is slower than with asynchronous updating because called transactions wait for updating to be completed. However, the called transaction is able to return any update error message that occurs to your program. It is much easier for you to analyze and recover from errors.

DataBase Commit:

This statement will apply any outstanding database updates and wait until they have actually been put on the database before proceeding to the next statement.

An ordinary commit work will initiate the process to update the databases in a separate task and will press on in your abap.

COMMIT WORK: ( Asynchronous)

Your program does not wait for any acknowledgement. it just start executing the next statment after COMMIT WORK.

Re: Difference between V1 and V2 updates

Former Member — Fri, 09 Nov 2007 10:34:54 GMT

Thank you very much John for all the info....

U said that Restarting can be done in tcode:SM13 - Update ..

Restarting means Repeat Update function in SM13 ??? if Yes, this function is available for both start immediately and Immediate start, no restart. Please clarify this..

Regards,

Maya.

Re: Difference between V1 and V2 updates

Former Member — Wed, 31 Dec 2014 07:20:38 GMT

Hi,

These links are not opening John...

Thanks...

Re: Difference between V1 and V2 updates

former_member697780 — Mon, 14 Dec 2020 12:17:18 GMT

Hi,

V1 is Primary Function module. It is Time Critical.

1. V1 is a Synchronous Update,

2. In this mode, the called transaction waits for any updates that it produces to be completed.
3. 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.

4. V1 update module generates update requests in table VBLOG in synchronous mode.

V2 modules describe less critical secondary changes.

1. V2 is asynchronous update

2. 1. In This mode, the updates are lined one after the other and the system doesn't wait for the updates to actually happen. These updates are then triggered by an internally scheduled job which then actually updates the data in the database.

3. Asynchronous processing therefore usually results in faster execution of your data transfer program.

4.Asynchronous processing is NOT recommended for processing any larger amount of data. This is because the called transaction receives no completion message from the update module in asynchronous updating. The calling data transfer program, in turn, cannot determine whether a called transaction ended with a successful update of the database or not.

Regards,

Nasreen.