<?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 and asynchronous in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/synchronous-and-asynchronous/m-p/2517676#M569677</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Pavan,&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;DataBase Commit:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;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.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;An ordinary commit work will initiate the process to update the databases in a separate task and will press on in your abap.&lt;/P&gt;&lt;P&gt;COMMIT WORK: ( Asynchronous)&lt;/P&gt;&lt;P&gt;Your program does not wait for any acknowledgement. it just start executing the next statment after COMMIT WORK.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Reward if useful.&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;&lt;P&gt;Aneesh.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Sat, 07 Jul 2007 05:47:33 GMT</pubDate>
    <dc:creator>Former Member</dc:creator>
    <dc:date>2007-07-07T05:47:33Z</dc:date>
    <item>
      <title>synchronous and asynchronous</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/synchronous-and-asynchronous/m-p/2517675#M569676</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;hello gurus....&lt;/P&gt;&lt;P&gt;can u give the definitions for synchronous and asynchronous updates.....&lt;/P&gt;&lt;P&gt;i mean how u have to answer the definition when asked in an interview...&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thnaks &lt;/P&gt;&lt;P&gt;Pavan&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 07 Jul 2007 05:45:04 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/synchronous-and-asynchronous/m-p/2517675#M569676</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-07-07T05:45:04Z</dc:date>
    </item>
    <item>
      <title>Re: synchronous and asynchronous</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/synchronous-and-asynchronous/m-p/2517676#M569677</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Pavan,&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;DataBase Commit:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;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.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;An ordinary commit work will initiate the process to update the databases in a separate task and will press on in your abap.&lt;/P&gt;&lt;P&gt;COMMIT WORK: ( Asynchronous)&lt;/P&gt;&lt;P&gt;Your program does not wait for any acknowledgement. it just start executing the next statment after COMMIT WORK.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Reward if useful.&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;&lt;P&gt;Aneesh.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 07 Jul 2007 05:47:33 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/synchronous-and-asynchronous/m-p/2517676#M569677</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-07-07T05:47:33Z</dc:date>
    </item>
    <item>
      <title>Re: synchronous and asynchronous</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/synchronous-and-asynchronous/m-p/2517677#M569678</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Pavan&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Call Transaction can be Asynchronous or Synchronous whereas a Session is only Synchronous.&lt;/P&gt;&lt;P&gt;A  Synchronous update is when the process waits for each and every record to get updated into the table.When a particular record gets updated then and then only it processes the next record,but an Asynchronous update doesn't.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;SDN have some threads which are having answers beautifully explained by SDN experts.You can check the same for more on this.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;K.Kiran.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Message was edited by: &lt;/P&gt;&lt;P&gt;        Kiran K&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 07 Jul 2007 05:50:24 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/synchronous-and-asynchronous/m-p/2517677#M569678</guid>
      <dc:creator>kiran_k8</dc:creator>
      <dc:date>2007-07-07T05:50:24Z</dc:date>
    </item>
    <item>
      <title>Re: synchronous and asynchronous</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/synchronous-and-asynchronous/m-p/2517678#M569679</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;&lt;/P&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;Check these threads&lt;/P&gt;&lt;P&gt;&lt;A class="jive_macro jive_macro_message" href="https://community.sap.com/" __jive_macro_name="message" modifiedtitle="true" __default_attr="3358008"&gt;&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A class="jive_macro jive_macro_message" href="https://community.sap.com/" __jive_macro_name="message" modifiedtitle="true" __default_attr="3601064"&gt;&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Reward points if useful&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;Ashu&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 07 Jul 2007 05:54:38 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/synchronous-and-asynchronous/m-p/2517678#M569679</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-07-07T05:54:38Z</dc:date>
    </item>
    <item>
      <title>Re: synchronous and asynchronous</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/synchronous-and-asynchronous/m-p/2517679#M569680</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Pavan&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;A 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;S 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;one simple example : You are creating sales order from file and also you want to update header text of sales order.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;when you want to update sales order header text,you need to use save_text function module ,here you need to pass sales order number.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;when you use call transaction update 'A', data will update transaction level and it goes to the next record,here it will not wait for database .&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;when you use call transaction update 'S',data will update transaction level and it will update database then it goes next record.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;if you want to update header text,then you need to use sync update&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;database commit - &lt;/P&gt;&lt;P&gt;comitt work - it will update data in database sucessfully&lt;/P&gt;&lt;P&gt;roll back - it will not update in database.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Check these threads&lt;/P&gt;&lt;P&gt;&lt;A class="jive_macro jive_macro_message" href="https://community.sap.com/" __jive_macro_name="message" modifiedtitle="true" __default_attr="3358008"&gt;&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A class="jive_macro jive_macro_message" href="https://community.sap.com/" __jive_macro_name="message" modifiedtitle="true" __default_attr="3601064"&gt;&lt;/A&gt; &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Reward Points if it is helpful&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;Pavan&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 07 Jul 2007 05:57:54 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/synchronous-and-asynchronous/m-p/2517679#M569680</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-07-07T05:57:54Z</dc:date>
    </item>
    <item>
      <title>Re: synchronous and asynchronous</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/synchronous-and-asynchronous/m-p/2517680#M569681</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;A 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;S 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;one simple example : You are creating sales order from file and also you want to update header text of sales order.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;when you want to update sales order header text,you need to use save_text function module ,here you need to pass sales order number.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;when you use call transaction update 'A', data will update transaction level and it goes to the next record,here it will not wait for database .&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;when you use call transaction update 'S',data will update transaction level and it will update database then it goes next record.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;if you want to update header text,then you need to use sync update&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;database commit - &lt;/P&gt;&lt;P&gt;comitt work - it will update data in database sucessfully&lt;/P&gt;&lt;P&gt;roll back - it will not update in database.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Reward Points if it is helpful&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;&lt;P&gt;Ravi&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 07 Jul 2007 06:39:00 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/synchronous-and-asynchronous/m-p/2517680#M569681</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-07-07T06:39:00Z</dc:date>
    </item>
    <item>
      <title>Re: synchronous and asynchronous</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/synchronous-and-asynchronous/m-p/2517681#M569682</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;hai Kiran....&lt;/P&gt;&lt;P&gt;u said that ...&lt;/P&gt;&lt;P&gt;SDN have some threads which are having answers beautifully explained by SDN experts.You can check the same for more on this.&lt;/P&gt;&lt;P&gt; &lt;/P&gt;&lt;P&gt;if u are having them with u ...please do farward that to my mails id : kpavan07@rediffmail.com&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thnaks in advance....&lt;/P&gt;&lt;P&gt;Pavan&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 10 Jul 2007 03:43:44 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/synchronous-and-asynchronous/m-p/2517681#M569682</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-07-10T03:43:44Z</dc:date>
    </item>
    <item>
      <title>Re: synchronous and asynchronous</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/synchronous-and-asynchronous/m-p/2517682#M569683</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;hai Kiran....&lt;/P&gt;&lt;P&gt;u said that ...&lt;/P&gt;&lt;P&gt;SDN have some threads which are having answers beautifully explained by SDN experts.You can check the same for more on this.&lt;/P&gt;&lt;P&gt; &lt;/P&gt;&lt;P&gt;if u are having them with u ...please do farward that to my mails id : kpavan07@rediffmail.com&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thnaks in advance....&lt;/P&gt;&lt;P&gt;Pavan&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 10 Jul 2007 03:44:17 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/synchronous-and-asynchronous/m-p/2517682#M569683</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-07-10T03:44:17Z</dc:date>
    </item>
    <item>
      <title>Re: synchronous and asynchronous</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/synchronous-and-asynchronous/m-p/2517683#M569684</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi pavan,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Synchronous: 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;Asynchronous: 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;&amp;lt;u&amp;gt;&amp;lt;b&amp;gt;Example: &amp;lt;/b&amp;gt;&amp;lt;/u&amp;gt; &lt;/P&gt;&lt;P&gt;&amp;lt;b&amp;gt;Synchronous:&amp;lt;/b&amp;gt; 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.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;lt;b&amp;gt;Asynchronous :&amp;lt;/b&amp;gt; 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.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Check the links for your kind reference -&lt;/P&gt;&lt;P&gt;&lt;A class="jive_macro jive_macro_message" href="https://community.sap.com/" __jive_macro_name="message" modifiedtitle="true" __default_attr="3435767"&gt;&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;A class="jive_macro jive_macro_message" href="https://community.sap.com/" __jive_macro_name="message" modifiedtitle="true" __default_attr="3562829"&gt;&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Cheers !&lt;/P&gt;&lt;P&gt;Moqeeth.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 10 Jul 2007 04:07:22 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/synchronous-and-asynchronous/m-p/2517683#M569684</guid>
      <dc:creator>mohammed_moqeeth</dc:creator>
      <dc:date>2007-07-10T04:07:22Z</dc:date>
    </item>
  </channel>
</rss>

