topic Re: Local Update in Application Development and Automation Discussions

Local Update

Former Member — Thu, 21 Jun 2007 07:30:24 GMT

Hi All,

Using CALL TRANSACTION UPDATE MODE IS LOCAL (L)

What is Local Update and give me small example Program

I look forward to your reply

Reward points compulsory

Thanks & Regards

SEK

Re: Local Update

Former Member — Thu, 21 Jun 2007 07:32:58 GMT

Asynchronous Update – The program does not wait for the work process to finish the update. Commit Work.

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 Update – The program wait for the work process to finish the update. Commit Work and Wait.

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.

<b>L Local updating. If you update data locally, the update of the database will not be processed in a separate process, but in the process of the calling program. (See the ABAP keyword documentation on SET UPDATE TASK LOCAL for more information.)</b>

Reward points for useful Answers

Regards

Anji

Re: Local Update

Former Member — Thu, 21 Jun 2007 07:35:25 GMT

Hi,

L Local updating. If you update data locally, the update of the database will not be processed in a separate process, but in the process of the calling program. (See the ABAP keyword documentation on SET UPDATE TASK LOCAL for more information.)

rEGARDS

Re: Local Update

Former Member — Thu, 21 Jun 2007 07:40:28 GMT

Hi,

Local Update :

In a local update, the update program is run by the same work process that processed the request. The dialog user has to wait for the update to finish before entering further data. This kind of update is useful when you want to reduce the amount of access to the database. The disadvantage of local updates is their parallel nature. The updates can be processed by many different work processes, unlike asynchronous or synchronous update, where the update is serialized due to the fact that there are fewer update work processes (and maybe only one).

You switch to local update using the ABAP statement SET UPDATE TASK LOCAL. This statement sets a "local update switch". When it is set, the system interprets CALL FUNCTION IN UPDATE TASK as a request for local update. The update is processed in the same work process as the dialog step containing the COMMIT WORK. The transaction waits for the update to finish before continuing.

As an example, suppose you have a program that uses asynchronous update that you normally run in dialog mode. However, this time you want to run it in the background. Since the system response time is irrelevant when you are running the program in the background, and you only want the program to continue processing when the update has actually finished, you can set the SET UPDATE TASK LOCAL switch in the program. You can then use a system variable to check at runtime whether the program is currently running in the background.

By default, the local update switch is not set, and it is reset after each COMMIT WORK or ROLLBACK WORK. You therefore need to include a SET UPDATE TASK LOCAL statement at the beginning of each SAP LUW.

If you reset data within the local update, the ROLLBACK WORK statement applies to both the dialog and the update part of the transaction, since no new SAP LUW is started for the update.

link:

<a href="http://help.sap.com/saphelp_nw04/helpdata/en/41/7af4d7a79e11d1950f0000e82de14a/content.htm">http://help.sap.com/saphelp_nw04/helpdata/en/41/7af4d7a79e11d1950f0000e82de14a/content.htm</a>

Regards,

Ameet

Re: Local Update

Former Member — Thu, 21 Jun 2007 07:42:12 GMT

Hi,

Local updating. If you update data locally, the update of the database will not be processed in a separate process, but in the process of the calling program.

Regards

Sudheer