<?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: Difference in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/difference/m-p/3113158#M739146</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 CALL TRANSACTION is - Asynchronous processing - Transfers data for a single transaction - &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;While for session method -It does not update transaction figures until the session has been processed. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Processing batch input data with CALL TRANSACTION USING is the faster of the two recommended data transfer methods. In this method, legacy data is processed inline in your data transfer program. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;lt;b&amp;gt;Reward if usefull&amp;lt;/b&amp;gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Sat, 17 Nov 2007 06:52:44 GMT</pubDate>
    <dc:creator>Former Member</dc:creator>
    <dc:date>2007-11-17T06:52:44Z</dc:date>
    <item>
      <title>Difference</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/difference/m-p/3113155#M739143</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Please Spot me the exact and important differences between call transaction and session method .&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Kesav &lt;SPAN __jive_emoticon_name="happy"&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 17 Nov 2007 06:32:23 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/difference/m-p/3113155#M739143</guid>
      <dc:creator>kesavadas_thekkillath</dc:creator>
      <dc:date>2007-11-17T06:32:23Z</dc:date>
    </item>
    <item>
      <title>Re: Difference</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/difference/m-p/3113156#M739144</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;There are so many:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Session method.&lt;/P&gt;&lt;P&gt;1) synchronous processing.&lt;/P&gt;&lt;P&gt;2) can tranfer large amount of data.&lt;/P&gt;&lt;P&gt;3) processing is slower.&lt;/P&gt;&lt;P&gt;4) error log is created&lt;/P&gt;&lt;P&gt;5) data is not updated until session is processed.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Call transaction.&lt;/P&gt;&lt;P&gt;1) asynchronous processing&lt;/P&gt;&lt;P&gt;2) can transfer small amount of data&lt;/P&gt;&lt;P&gt;3) processing is faster.&lt;/P&gt;&lt;P&gt;4) errors need to be handled explicitly&lt;/P&gt;&lt;P&gt;5) data is updated automatically &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Check these link:&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 href="http://www.sap-img.com/abap/question-about-bdc-program.htm" target="test_blank"&gt;http://www.sap-img.com/abap/question-about-bdc-program.htm&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://www.itcserver.com/blog/2006/06/30/batch-input-vs-call-transaction/" target="test_blank"&gt;http://www.itcserver.com/blog/2006/06/30/batch-input-vs-call-transaction/&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://www.planetsap.com/bdc_main_page.htm" target="test_blank"&gt;http://www.planetsap.com/bdc_main_page.htm&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="2491514"&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;Naimesh Patel&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 17 Nov 2007 06:39:25 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/difference/m-p/3113156#M739144</guid>
      <dc:creator>naimesh_patel</dc:creator>
      <dc:date>2007-11-17T06:39:25Z</dc:date>
    </item>
    <item>
      <title>Re: Difference</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/difference/m-p/3113157#M739145</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;In &amp;#145;Call Transaction&amp;#146;, the transactions are triggered at the time of processing itself and so the ABAP program must do the error handling. It can also be used for real-time interfaces and custom error handling &amp;amp; logging features. Whereas in&lt;/P&gt;&lt;P&gt;Batch Input Sessions, the ABAP program creates a session with all the transactional data, and this session can be viewed, scheduled and processed (using Transaction SM35) at a later time. The latter technique has a built-in error processing mechanism too.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;difference between batch input and call transaction in BDC&lt;/P&gt;&lt;P&gt;Session method.&lt;/P&gt;&lt;P&gt;1) synchronous processing.&lt;/P&gt;&lt;P&gt;2) can tranfer large amount of data.&lt;/P&gt;&lt;P&gt;3) processing is slower.&lt;/P&gt;&lt;P&gt;4) error log is created&lt;/P&gt;&lt;P&gt;5) data is not updated until session is processed.&lt;/P&gt;&lt;P&gt;Call transaction.&lt;/P&gt;&lt;P&gt;1) asynchronous processing&lt;/P&gt;&lt;P&gt;2) can transfer small amount of data&lt;/P&gt;&lt;P&gt;3) processing is faster.&lt;/P&gt;&lt;P&gt;4) errors need to be handled explicitly&lt;/P&gt;&lt;P&gt;5) data is updated automatically &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Processing batch input data with CALL TRANSACTION USING is the faster of the two recommended data transfer methods. In this method, legacy data is processed inline in your data transfer program&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Synchronous versus  Asynchronous&lt;/P&gt;&lt;P&gt;&amp;lt;b&amp;gt;synchronous updating&amp;lt;/b&amp;gt;&lt;/P&gt;&lt;P&gt;DO.&lt;/P&gt;&lt;P&gt;&amp;#133;&amp;#133;&amp;#133;&lt;/P&gt;&lt;P&gt;    PERFORM FILL_BDC_TAB.&lt;/P&gt;&lt;P&gt;    CALL TRANSACTION &amp;#145;FK02&amp;#146;&lt;/P&gt;&lt;P&gt;	USING 	BDC_TAB&lt;/P&gt;&lt;P&gt;	MODE	&amp;#145;N&amp;#146;&lt;/P&gt;&lt;P&gt;	UPDATE	&amp;#145;S&amp;#146;.&lt;/P&gt;&lt;P&gt;      IF SY-SUBRC &amp;lt; &amp;gt; 0.&lt;/P&gt;&lt;P&gt;	WRITE: /&amp;#145;ERROR&amp;#146;.	&lt;/P&gt;&lt;P&gt;      ENDIF.&lt;/P&gt;&lt;P&gt;ENDDO.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;With synchronous updating, we can check SY-SUBRC to determine the success of the transaction and the actual update to the database.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;lt;b&amp;gt; asynchronous updating&amp;lt;/b&amp;gt;&lt;/P&gt;&lt;P&gt;DO.&lt;/P&gt;&lt;P&gt;&amp;#133;&amp;#133;&amp;#133;&lt;/P&gt;&lt;P&gt;    PERFORM FILL_BDC_TAB.&lt;/P&gt;&lt;P&gt;    CALL TRANSACTION &amp;#145;FK02&amp;#146;&lt;/P&gt;&lt;P&gt;	USING 	BDC_TAB&lt;/P&gt;&lt;P&gt;	MODE	&amp;#145;N&amp;#146;&lt;/P&gt;&lt;P&gt;	UPDATE	&amp;#145;A&amp;#146;.&lt;/P&gt;&lt;P&gt;      IF SY-SUBRC &amp;lt; &amp;gt; 0.&lt;/P&gt;&lt;P&gt;	WRITE: /&amp;#145;ERROR&amp;#146;.	&lt;/P&gt;&lt;P&gt;      ENDIF.&lt;/P&gt;&lt;P&gt;ENDDO.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;With asynchronous updating, we can check SY-SUBRC to determine the success of the transaction only,  not the actual update to the database.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 17 Nov 2007 06:39:56 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/difference/m-p/3113157#M739145</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-11-17T06:39:56Z</dc:date>
    </item>
    <item>
      <title>Re: Difference</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/difference/m-p/3113158#M739146</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 CALL TRANSACTION is - Asynchronous processing - Transfers data for a single transaction - &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;While for session method -It does not update transaction figures until the session has been processed. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Processing batch input data with CALL TRANSACTION USING is the faster of the two recommended data transfer methods. In this method, legacy data is processed inline in your data transfer program. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;lt;b&amp;gt;Reward if usefull&amp;lt;/b&amp;gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 17 Nov 2007 06:52:44 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/difference/m-p/3113158#M739146</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-11-17T06:52:44Z</dc:date>
    </item>
  </channel>
</rss>

