<?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: hai in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/hai/m-p/1868563#M365879</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;Synchrnonus updating means one by one updation.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Asynchrnous updating means totally 100 records means at a time updation. Compare to synchronous asynchrnous  updation is very fast.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Shankar&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 01 Feb 2007 10:00:25 GMT</pubDate>
    <dc:creator>p291102</dc:creator>
    <dc:date>2007-02-01T10:00:25Z</dc:date>
    <item>
      <title>hai</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/hai/m-p/1868561#M365877</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;what is the difference between synchronus updating and asynchronus updating&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 01 Feb 2007 09:57:21 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/hai/m-p/1868561#M365877</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-02-01T09:57:21Z</dc:date>
    </item>
    <item>
      <title>Re: hai</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/hai/m-p/1868562#M365878</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;please check yhis&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;lt;a href="http://help.sap.com/saphelp_nw04/helpdata/en/41/7af4cba79e11d1950f0000e82de14a/content.htm"&amp;gt;http://help.sap.com/saphelp_nw04/helpdata/en/41/7af4cba79e11d1950f0000e82de14a/content.htm&amp;lt;/a&amp;gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;regards&lt;/P&gt;&lt;P&gt;shiba dutta&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 01 Feb 2007 09:59:56 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/hai/m-p/1868562#M365878</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-02-01T09:59:56Z</dc:date>
    </item>
    <item>
      <title>Re: hai</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/hai/m-p/1868563#M365879</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;Synchrnonus updating means one by one updation.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Asynchrnous updating means totally 100 records means at a time updation. Compare to synchronous asynchrnous  updation is very fast.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Shankar&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 01 Feb 2007 10:00:25 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/hai/m-p/1868563#M365879</guid>
      <dc:creator>p291102</dc:creator>
      <dc:date>2007-02-01T10:00:25Z</dc:date>
    </item>
    <item>
      <title>Re: hai</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/hai/m-p/1868564#M365880</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;HI Goutham,&lt;/P&gt;&lt;P&gt;   Are you referring to Call transaction statement?&lt;/P&gt;&lt;P&gt;If yes, In Asynchrounous Update, the system when executing the call transaction statement doesn't wait for the transaction program to update all the tables and quickly return to the program which called the transaction.&lt;/P&gt;&lt;P&gt;In Synchrnous update, the call transaction statement will complete only after all the tables are updated in the transaction that has been called.&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Ravi&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 01 Feb 2007 10:00:34 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/hai/m-p/1868564#M365880</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-02-01T10:00:34Z</dc:date>
    </item>
    <item>
      <title>Re: hai</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/hai/m-p/1868565#M365881</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;go thru these urls&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://www.shef.ac.uk/psychology/gurney/notes/l5/subsection3_3_2.html" target="test_blank"&gt;http://www.shef.ac.uk/psychology/gurney/notes/l5/subsection3_3_2.html&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://help.sap.com/saphelp_nw04/helpdata/en/41/7af4d4a79e11d1950f0000e82de14a/content.htm" target="test_blank"&gt;http://help.sap.com/saphelp_nw04/helpdata/en/41/7af4d4a79e11d1950f0000e82de14a/content.htm&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://help.sap.com/saphelp_erp2004/helpdata/en/35/2a6c47aae85cd5e10000009b38f974/content.htm" target="test_blank"&gt;http://help.sap.com/saphelp_erp2004/helpdata/en/35/2a6c47aae85cd5e10000009b38f974/content.htm&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;regards&lt;/P&gt;&lt;P&gt;Shiva&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 01 Feb 2007 10:01:34 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/hai/m-p/1868565#M365881</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-02-01T10:01:34Z</dc:date>
    </item>
    <item>
      <title>Re: hai</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/hai/m-p/1868566#M365882</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;what are the types of  windows&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 01 Feb 2007 10:04:40 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/hai/m-p/1868566#M365882</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-02-01T10:04:40Z</dc:date>
    </item>
    <item>
      <title>Re: hai</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/hai/m-p/1868567#M365883</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Goutham,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;In synchronous update, you do not submit update requests using CALL FUNCTION &amp;#133; IN UPDATE TASK . Instead you use the ABAP statement COMMIT WORK AND WAIT. When the update is finished, control passes back to the program where as in asynchronous update, the update work processes are responsible for updating the database. If, in a dialog work process, the function modules stored in interim storage through CALL FUNCTION ... IN UPDATE TASK are released for processing by means of the ABAP statement COMMIT WORK, the dialog work process will not wait for the update process to finish. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;Vinay&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 01 Feb 2007 10:05:12 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/hai/m-p/1868567#M365883</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-02-01T10:05:12Z</dc:date>
    </item>
    <item>
      <title>Re: hai</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/hai/m-p/1868568#M365884</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Goutham,&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;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;Regards,&lt;/P&gt;&lt;P&gt;Priyanka.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 01 Feb 2007 10:10:41 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/hai/m-p/1868568#M365884</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-02-01T10:10:41Z</dc:date>
    </item>
  </channel>
</rss>

