<?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 question in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/bapi-question/m-p/3869648#M930058</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Sharma,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Award points if useful&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;BAPI cannot have exceptions in them.&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;BAPIs themselves must not trigger any messages (such as MESSAGE xnnn) in the coding. In particular they must not generate terminations or display dialog boxes. Instead, all messages must be intercepted internally and reported back to the calling program in the Return parameter. Otherwise the BAPI will not be processed correctly and control may not be given back to the calling program&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;BAPI cannot use commit work stmt instead&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Commit work is used when you code directly in ABAP and make changes in the database and &lt;/P&gt;&lt;P&gt;want to commit the database. &lt;/P&gt;&lt;P&gt;BAPI_TRANSACTION_COMMIT is used when you make changes to the SAP database by calling &lt;/P&gt;&lt;P&gt;a BAPI from outside SAP and want to commit the database. When you use a BAPI, you can not &lt;/P&gt;&lt;P&gt;directly use commit work, instead you are allowed to use only  &lt;/P&gt;&lt;P&gt;BAPI_TRANSACTION_COMMIT. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Why Release?&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You cannot use the same structures used in existing applications because BAPI structures are frozen when BAPIs are released and then there are restrictions on changing them.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Mon, 19 May 2008 10:58:31 GMT</pubDate>
    <dc:creator>Former Member</dc:creator>
    <dc:date>2008-05-19T10:58:31Z</dc:date>
    <item>
      <title>Bapi question</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/bapi-question/m-p/3869647#M930057</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi All ,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have some doubts in Bapi&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;1) why we can not use exception in Bapi ?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;2)  BAPI must not execute a COMMIT-WORK command. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;3) why its necessary to released the bapi &amp;amp; how ?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;4) In Bapi there is a test  for Example IF 1 = 2. If the test is true a message is displayed. The condition will obviously never be true, and we will never want to display a message in a BAPI&lt;/P&gt;&lt;P&gt; then why it is necessary ?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks in advance &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Rahul&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 19 May 2008 10:42:22 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/bapi-question/m-p/3869647#M930057</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2008-05-19T10:42:22Z</dc:date>
    </item>
    <item>
      <title>Re: Bapi question</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/bapi-question/m-p/3869648#M930058</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Sharma,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Award points if useful&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;BAPI cannot have exceptions in them.&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;BAPIs themselves must not trigger any messages (such as MESSAGE xnnn) in the coding. In particular they must not generate terminations or display dialog boxes. Instead, all messages must be intercepted internally and reported back to the calling program in the Return parameter. Otherwise the BAPI will not be processed correctly and control may not be given back to the calling program&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;BAPI cannot use commit work stmt instead&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Commit work is used when you code directly in ABAP and make changes in the database and &lt;/P&gt;&lt;P&gt;want to commit the database. &lt;/P&gt;&lt;P&gt;BAPI_TRANSACTION_COMMIT is used when you make changes to the SAP database by calling &lt;/P&gt;&lt;P&gt;a BAPI from outside SAP and want to commit the database. When you use a BAPI, you can not &lt;/P&gt;&lt;P&gt;directly use commit work, instead you are allowed to use only  &lt;/P&gt;&lt;P&gt;BAPI_TRANSACTION_COMMIT. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Why Release?&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You cannot use the same structures used in existing applications because BAPI structures are frozen when BAPIs are released and then there are restrictions on changing them.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 19 May 2008 10:58:31 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/bapi-question/m-p/3869648#M930058</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2008-05-19T10:58:31Z</dc:date>
    </item>
  </channel>
</rss>

