<?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: bapi in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/bapi/m-p/3201990#M763168</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;As of Release 4.0 BAPIs must not execute 'COMMIT WORK' commands.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Reason : The caller should have control of the transaction. Several BAPIs should be able to be combined within one LUW.  &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The following commands must not be used:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;CALL TRANSACTION &lt;/P&gt;&lt;P&gt;SUBMIT REPORT &lt;/P&gt;&lt;P&gt;SUBMIT REPORT AND RETURN&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Check the link for further details on this.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://help.sap.com/saphelp_nw04/helpdata/en/e0/9eb2370f9cbe68e10000009b38f8cf/frameset.htm" target="test_blank"&gt;http://help.sap.com/saphelp_nw04/helpdata/en/e0/9eb2370f9cbe68e10000009b38f8cf/frameset.htm&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;Abhishek Jolly&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 13 Dec 2007 19:25:47 GMT</pubDate>
    <dc:creator>former_member195698</dc:creator>
    <dc:date>2007-12-13T19:25:47Z</dc:date>
    <item>
      <title>bapi</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/bapi/m-p/3201989#M763167</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;hi&lt;/P&gt;&lt;P&gt;if the bapi doesnt  update databsse&lt;/P&gt;&lt;P&gt;we have to use BAPI_TRANSACTION_COMMIT it will update the databse&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;by checking only we are knowing it.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;so&lt;/P&gt;&lt;P&gt;how to know when we have to use BAPI_TRANSACTION_COMMIT without checking(whether the main bapi will update).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;is there any difference to between the    &lt;/P&gt;&lt;P&gt; bapis   &lt;/P&gt;&lt;P&gt;1) . which are not use BAPI_TRANSACTION_COMMIT&lt;/P&gt;&lt;P&gt;2) . which are use BAPI_TRANSACTION_COMMIT&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 13 Dec 2007 16:33:56 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/bapi/m-p/3201989#M763167</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-12-13T16:33:56Z</dc:date>
    </item>
    <item>
      <title>Re: bapi</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/bapi/m-p/3201990#M763168</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;As of Release 4.0 BAPIs must not execute 'COMMIT WORK' commands.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Reason : The caller should have control of the transaction. Several BAPIs should be able to be combined within one LUW.  &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The following commands must not be used:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;CALL TRANSACTION &lt;/P&gt;&lt;P&gt;SUBMIT REPORT &lt;/P&gt;&lt;P&gt;SUBMIT REPORT AND RETURN&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Check the link for further details on this.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://help.sap.com/saphelp_nw04/helpdata/en/e0/9eb2370f9cbe68e10000009b38f8cf/frameset.htm" target="test_blank"&gt;http://help.sap.com/saphelp_nw04/helpdata/en/e0/9eb2370f9cbe68e10000009b38f8cf/frameset.htm&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;Abhishek Jolly&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 13 Dec 2007 19:25:47 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/bapi/m-p/3201990#M763168</guid>
      <dc:creator>former_member195698</dc:creator>
      <dc:date>2007-12-13T19:25:47Z</dc:date>
    </item>
    <item>
      <title>Re: bapi</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/bapi/m-p/3201991#M763169</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;thanku abhisek&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;wt finally i understood is&lt;/P&gt;&lt;P&gt;so internally commit work calls with only 'BAPI_TRANSACTION_COMMIT'&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 14 Dec 2007 06:43:38 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/bapi/m-p/3201991#M763169</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-12-14T06:43:38Z</dc:date>
    </item>
    <item>
      <title>Re: bapi</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/bapi/m-p/3201992#M763170</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Yes, the BAPI's created with new guidelines will not have COMMIT WORK or ROLLBACK Statement in it. Based on the Failure/Success of the BAPI we have to explicitly call BAPI_TRANSACTION_ROLLBACK and  BAPI_TRANSACTION_COMMIT  which will have ROLLBACK WORK or COMMIT WORK Respectively in it.&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;Abhishek&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 14 Dec 2007 10:14:23 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/bapi/m-p/3201992#M763170</guid>
      <dc:creator>former_member195698</dc:creator>
      <dc:date>2007-12-14T10:14:23Z</dc:date>
    </item>
    <item>
      <title>Re: bapi</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/bapi/m-p/3201993#M763171</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Srinu,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Check the below link,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://publib.boulder.ibm.com/infocenter/wbihelp/v6rxmx/index.jsp?topic=/com.ibm.wbia_adapters.doc/doc/mysap4/mysap472.htm" target="test_blank"&gt;http://publib.boulder.ibm.com/infocenter/wbihelp/v6rxmx/index.jsp?topic=/com.ibm.wbia_adapters.doc/doc/mysap4/mysap472.htm&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;lt;b&amp;gt;Kindly Reward points if you found this reply helpful&amp;lt;/b&amp;gt;,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Cheers,&lt;/P&gt;&lt;P&gt;Chaitanya.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 14 Dec 2007 10:25:49 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/bapi/m-p/3201993#M763171</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-12-14T10:25:49Z</dc:date>
    </item>
  </channel>
</rss>

