<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: synchronous asynchronous update in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/synchronous-asynchronous-update/m-p/2283987#M497498</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;        Synchronous update is as and when you call the update funtion module or say routine at the same time that procedure is executed.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;        Where as in the case of Asynchronous update you call the procedure but it will be xecuted only after the database commit.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt; For example: PERFORM ON COMMIT.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Best Regards,&lt;/P&gt;&lt;P&gt;Sesh&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Mon, 14 May 2007 07:57:28 GMT</pubDate>
    <dc:creator>seshatalpasai_madala</dc:creator>
    <dc:date>2007-05-14T07:57:28Z</dc:date>
    <item>
      <title>synchronous asynchronous update</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/synchronous-asynchronous-update/m-p/2283986#M497497</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;what is difference between synch and asynch update???&lt;/P&gt;&lt;P&gt;how it affects database update???&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 14 May 2007 07:49:19 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/synchronous-asynchronous-update/m-p/2283986#M497497</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-05-14T07:49:19Z</dc:date>
    </item>
    <item>
      <title>Re: synchronous asynchronous update</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/synchronous-asynchronous-update/m-p/2283987#M497498</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;        Synchronous update is as and when you call the update funtion module or say routine at the same time that procedure is executed.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;        Where as in the case of Asynchronous update you call the procedure but it will be xecuted only after the database commit.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt; For example: PERFORM ON COMMIT.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Best Regards,&lt;/P&gt;&lt;P&gt;Sesh&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 14 May 2007 07:57:28 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/synchronous-asynchronous-update/m-p/2283987#M497498</guid>
      <dc:creator>seshatalpasai_madala</dc:creator>
      <dc:date>2007-05-14T07:57:28Z</dc:date>
    </item>
    <item>
      <title>Re: synchronous asynchronous update</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/synchronous-asynchronous-update/m-p/2283988#M497499</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi!&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Asyncron update: COMMIT WORK.&lt;/P&gt;&lt;P&gt;COMMIT WORK also &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Calls the subroutines specified by PERFORM ... ON COMMIT &lt;/P&gt;&lt;P&gt;Executes asynchronously any update requests (see CALL FUNCTION ... IN UPDATE TASK) specified in these subroutines or started just before &lt;/P&gt;&lt;P&gt;Processes the function modules specified in CALL FUNCTION ... IN BACKGROUND TASK &lt;/P&gt;&lt;P&gt;Resets the time slice counter to 0. &lt;/P&gt;&lt;P&gt;Ensures that the locks of the SAP locking concept are handled in accordance with its SCOPE Parameter. &lt;/P&gt;&lt;P&gt;Executes a database commit on all database connections &lt;/P&gt;&lt;P&gt;Closes all open database cursors (OPEN CURSOR) on all database connections &lt;/P&gt;&lt;P&gt;Releases all database locks on all database connections &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Syncron update: COMMIT WORK AND WAIT.&lt;/P&gt;&lt;P&gt;The addition ... AND WAIT makes the program wait for the type V1 update (update with immediate start) to be executed. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;We can say, in the synchron mode, you have to wait, until SAP syncronizes all database changes.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;Tamá&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 14 May 2007 07:58:51 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/synchronous-asynchronous-update/m-p/2283988#M497499</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-05-14T07:58:51Z</dc:date>
    </item>
    <item>
      <title>Re: synchronous asynchronous update</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/synchronous-asynchronous-update/m-p/2283989#M497500</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;hi&lt;/P&gt;&lt;P&gt;good&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Asynchronous Update &amp;#150; The program does not wait for the work process to finish the update. Commit Work.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Synchronous Update &amp;#150; The program wait for the work process to finish the update. Commit Work and Wait. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;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.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;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. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;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.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;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. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;thanks&lt;/P&gt;&lt;P&gt;mrutyun^&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 14 May 2007 08:21:26 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/synchronous-asynchronous-update/m-p/2283989#M497500</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-05-14T08:21:26Z</dc:date>
    </item>
    <item>
      <title>Re: synchronous asynchronous update</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/synchronous-asynchronous-update/m-p/2283990#M497501</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;For Update you have &lt;/P&gt;&lt;P&gt;A - asynchronus - does not wait for next update in the queue&lt;/P&gt;&lt;P&gt;S - Synchronus - waits until the previous update is completed before a new request is considered&lt;/P&gt;&lt;P&gt;L - Local update - Uses a different work process to trigger call function in update task.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;In synchronus method until one record process takes place into database next record will not be processed. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;In asynchronus immedate updation of data into database table.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Check this link for more detailed information:&lt;/P&gt;&lt;P&gt;&lt;A href="http://fuller.mit.edu/tech/sync_asynchronous.html" target="test_blank"&gt;http://fuller.mit.edu/tech/sync_asynchronous.html&lt;/A&gt; &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;'A', 'S' and 'L' are the update modes in CALL transaction method.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I will give you a simple example to explain this.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Suppose that there are 30 records in total and an error has occured in the 5th record.&lt;/P&gt;&lt;P&gt; In asynchronous, update is done for every 30 records while in synchronous one,&lt;/P&gt;&lt;P&gt; update is done only upto the 4th record.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;So only after the record in the fifth one is eliminated, remaining others are processed.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Have a look at this URL from SAP Help:&lt;/P&gt;&lt;P&gt;&lt;A href="http://help.sap.com/saphelp_46c/helpdata/en/41/7af4cba79e11d1950f0000e82de14a/frameset.htm" target="test_blank"&gt;http://help.sap.com/saphelp_46c/helpdata/en/41/7af4cba79e11d1950f0000e82de14a/frameset.htm&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;Reshma&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 14 May 2007 08:29:58 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/synchronous-asynchronous-update/m-p/2283990#M497501</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-05-14T08:29:58Z</dc:date>
    </item>
  </channel>
</rss>

