<?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: BDC in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/bdc/m-p/2241370#M483276</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Ashok,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You use the UPDATE parameter to specify how updates produced by a transaction should be processed. You can select between these modes: &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;lt;b&amp;gt;A Asynchronous updating&amp;lt;/b&amp;gt;. 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;&amp;lt;b&amp;gt;S Synchronous updating.&amp;lt;/b&amp;gt; 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;&amp;lt;b&amp;gt;L Local updating&amp;lt;/b&amp;gt;. 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.)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;Reward If helpful.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Fri, 25 May 2007 08:50:03 GMT</pubDate>
    <dc:creator>Former Member</dc:creator>
    <dc:date>2007-05-25T08:50:03Z</dc:date>
    <item>
      <title>BDC</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/bdc/m-p/2241368#M483274</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;HAI,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;       IN CALLTRANACTION WHAT IS MEANT &amp;lt;b&amp;gt;LOCAL UPDATE&amp;lt;/b&amp;gt;.&lt;/P&gt;&lt;P&gt;WHAT IS THE DIFF BETWEEN LOCAL ,SYNCHRONOUS, ASYNCHRONOUS UPDATE&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;ASHOK KUMAR&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 25 May 2007 08:45:17 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/bdc/m-p/2241368#M483274</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-05-25T08:45:17Z</dc:date>
    </item>
    <item>
      <title>Re: BDC</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/bdc/m-p/2241369#M483275</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;Hi.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;lt;b&amp;gt;A mode itself indicates asynchronus update means donot wait for execution of Commit work...the mode u r using is correct..&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Asynchronous update. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Updates of called programs are executed in the same way as if in the COMMIT WORK statement the AND WAIT addition was not specified.&amp;lt;/b&amp;gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Sree&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 25 May 2007 08:47:57 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/bdc/m-p/2241369#M483275</guid>
      <dc:creator>sreeramkumar_madisetty</dc:creator>
      <dc:date>2007-05-25T08:47:57Z</dc:date>
    </item>
    <item>
      <title>Re: BDC</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/bdc/m-p/2241370#M483276</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Ashok,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You use the UPDATE parameter to specify how updates produced by a transaction should be processed. You can select between these modes: &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;lt;b&amp;gt;A Asynchronous updating&amp;lt;/b&amp;gt;. 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;&amp;lt;b&amp;gt;S Synchronous updating.&amp;lt;/b&amp;gt; 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;&amp;lt;b&amp;gt;L Local updating&amp;lt;/b&amp;gt;. 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.)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;Reward If helpful.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 25 May 2007 08:50:03 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/bdc/m-p/2241370#M483276</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-05-25T08:50:03Z</dc:date>
    </item>
    <item>
      <title>Re: BDC</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/bdc/m-p/2241371#M483277</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;hi ashok,&lt;/P&gt;&lt;P&gt;L Local updating &lt;/P&gt;&lt;P&gt;the update data is not stored in the database, but in ABAP/4 Memory difference is that it is not performed in a separate process, but in the same process as the calling program&lt;/P&gt;&lt;P&gt;processing does not continue until all the update requests have been performed. In the standard setting, the normal update task is always active. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;S Synchronous updating. &lt;/P&gt;&lt;P&gt;In this mode, the called transaction waits for any updates that it produces to be completed&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 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;regards,&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 25 May 2007 09:05:09 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/bdc/m-p/2241371#M483277</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-05-25T09:05:09Z</dc:date>
    </item>
    <item>
      <title>Re: BDC</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/bdc/m-p/2241372#M483278</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Ashok,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Here is some info about the UPDATE option for CALL TRANSACTION from the SAP help:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;... UPDATE upd &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Effect &lt;/P&gt;&lt;P&gt;The UPDATE addition determines the processing mode for batch input processing. You can specify a character-type object for upd. Its possible content and its effect are displayed in the following table. Without use of one of the additions UPDATE or OPTIONS FROM, the effect is the same as if upd had the content "A". &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;upd Effect &lt;/P&gt;&lt;P&gt;"A" Asynchronous update. Updates of called programs are executed in the same way as if in the COMMIT WORK statement the AND WAIT addition was not specified. &lt;/P&gt;&lt;P&gt;"S" Synchronous processing. Updates of the called programs are executed in the same way as if in the COMMIT WORK statement the AND WAIT addition had been specified. &lt;/P&gt;&lt;P&gt;"L" Local update. Updates of the called program are executed in such a way as if the SET UPDATE TASK LOCAL statement had been executed in it. &lt;/P&gt;&lt;P&gt;Other As for "A". &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Note &lt;/P&gt;&lt;P&gt;This option is not available for execution of actual batch input sessions. There the update is always synchronous. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;In synchronous method incase if there is any change in the table all the related tables will be changed accordingly and then sy-subrc will be returned.In asynchronous method in case if there is any change in the table the s-subrc will be immediatel returned and then the related tables will be updated. the diffrence between these two is in asynchronous even if the related tables are not updated the sy-subrc will still be returned as 0.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Younus&lt;/P&gt;&lt;P&gt;&amp;lt;b&amp;gt;Reward Helpful Answers:-)&amp;lt;/b&amp;gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 25 May 2007 09:05:51 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/bdc/m-p/2241372#M483278</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-05-25T09:05:51Z</dc:date>
    </item>
    <item>
      <title>Re: BDC</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/bdc/m-p/2241373#M483279</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Ashok,&lt;/P&gt;&lt;P&gt;    &lt;/P&gt;&lt;P&gt;Local Update: For Example: A program asks the system to perform a certain task end than either waits or doesn't  wait for the task to finish..&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Synchronous: Processing the program waots control returns to the programme only when the task has been completed.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Asychronous: Process the program does not wait for the system returns control after mempry logging the required for execution..&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;Satya Kumar..&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 25 May 2007 12:41:55 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/bdc/m-p/2241373#M483279</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-05-25T12:41:55Z</dc:date>
    </item>
    <item>
      <title>Re: BDC</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/bdc/m-p/2241374#M483280</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Ashok,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Local Update: For Example: A program asks the system to perform a certain task end than either waits or doesn't wait for the task to finish..&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Synchronous: Processing the program waits control returns to the programme only when the task has been completed.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Asychronous: Process the program does not wait for the system returns control after memory logging the required for execution..&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;Satya Kumar..&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 25 May 2007 12:43:45 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/bdc/m-p/2241374#M483280</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-05-25T12:43:45Z</dc:date>
    </item>
  </channel>
</rss>

