<?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 session and call transaction doubt in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/session-and-call-transaction-doubt/m-p/2314435#M507271</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;1. Which is synchronous and which is asynchronous among session method and call transaction method and what is the reason behind it??&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Mon, 14 May 2007 17:02:57 GMT</pubDate>
    <dc:creator>Former Member</dc:creator>
    <dc:date>2007-05-14T17:02:57Z</dc:date>
    <item>
      <title>session and call transaction doubt</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/session-and-call-transaction-doubt/m-p/2314435#M507271</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;1. Which is synchronous and which is asynchronous among session method and call transaction method and what is the reason behind it??&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 14 May 2007 17:02:57 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/session-and-call-transaction-doubt/m-p/2314435#M507271</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-05-14T17:02:57Z</dc:date>
    </item>
    <item>
      <title>Re: session and call transaction doubt</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/session-and-call-transaction-doubt/m-p/2314436#M507272</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;- synchronous method: it means after CALL TRANSACTION is finished the calling program is waiting for the database is updated really,&lt;/P&gt;&lt;P&gt;- asynchronous method: the calling program doesn't wait for updting, so it'll go on while the dabase is being updated.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;So the system uses asynchronous method by default, because it's faster, u should use synchronous method only if you need to read the new data inserted/updated by CALL TRANSACTION.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Max&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 14 May 2007 17:11:02 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/session-and-call-transaction-doubt/m-p/2314436#M507272</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-05-14T17:11:02Z</dc:date>
    </item>
    <item>
      <title>Re: session and call transaction doubt</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/session-and-call-transaction-doubt/m-p/2314437#M507273</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;Look at the below link&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://www.sap-img.com/abap/difference-between-batch-input-and-call-transaction-in-bdc.htm" target="test_blank"&gt;http://www.sap-img.com/abap/difference-between-batch-input-and-call-transaction-in-bdc.htm&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="3390764"&gt;&lt;/A&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; Sudheer&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 14 May 2007 17:11:56 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/session-and-call-transaction-doubt/m-p/2314437#M507273</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-05-14T17:11:56Z</dc:date>
    </item>
    <item>
      <title>Re: session and call transaction doubt</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/session-and-call-transaction-doubt/m-p/2314438#M507274</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;For batch session, processing is asynchronous, while database updates using this method are synchronous.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Call transaction, processing is synchronous, and database updates can be either async or sync (you can specify in your call using UPDATE 'A' or 'S').&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You will find detailed information on the differences between batch session and call transaction in the document link below.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://help.sap.com/saphelp_46c/helpdata/en/fa/097097543b11d1898e0000e8322d00/frameset.htm" target="test_blank"&gt;http://help.sap.com/saphelp_46c/helpdata/en/fa/097097543b11d1898e0000e8322d00/frameset.htm&lt;/A&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 14 May 2007 17:16:23 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/session-and-call-transaction-doubt/m-p/2314438#M507274</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-05-14T17:16:23Z</dc:date>
    </item>
    <item>
      <title>Re: session and call transaction doubt</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/session-and-call-transaction-doubt/m-p/2314439#M507275</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;The most important aspects of the batch session interface are: - Asynchronous processing - Transfers data for multiple transactions - Synchronous database update During processing, no transaction is started until the previous transaction has been written to the database. - A batch input processing log is generated for each session - Sessions cannot be generated in parallel  &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The most important aspects of the CALL TRANSACTION USING interface are: - Synchronous processing - Transfers data for a single transaction - Synchronous and asynchronous database updating both possible The program specifies which kind of updating is desired. - Separate LUW for the transaction The system performs a database commit immediately before and after the CALL TRANSACTION USING statement.  - No batch input processing log is generated. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Bhaskar&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 14 May 2007 20:15:52 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/session-and-call-transaction-doubt/m-p/2314439#M507275</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-05-14T20:15:52Z</dc:date>
    </item>
  </channel>
</rss>

