<?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 exceptions in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/bapi-exceptions/m-p/3854178#M926464</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;when you are creating your own 'BAPI', you should not maintain the exceptions, but use the return table (structure BAPIRET2), to 'catch' all messages generated by the BAPI and send it back to the calling application.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;However, what you should do is add two standard exceptions when calling the BAPI for catching communication failures and system failures (short dumps for example) in the calling system. Just copy and paste this behind the BAPI when calling it:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;EXCEPTIONS&lt;/P&gt;&lt;P&gt;system_failure = 1 MESSAGE return_message&lt;/P&gt;&lt;P&gt;communication_failure = 2 MESSAGE return_message&lt;/P&gt;&lt;P&gt;OTHERS.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;return_message can be defined as type c length 255.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;[using predefined exceptions for RFC|http://help.sap.com/saphelp_nw70/helpdata/EN/22/0425e0488911d189490000e829fbbd/content.htm]&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Edited by: Micky Oestreich on May 21, 2008 9:28 PM&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 21 May 2008 19:27:08 GMT</pubDate>
    <dc:creator>Sm1tje</dc:creator>
    <dc:date>2008-05-21T19:27:08Z</dc:date>
    <item>
      <title>BAPI exceptions</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/bapi-exceptions/m-p/3854176#M926462</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Can I mantain exceptions in BAPI and how?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 21 May 2008 18:55:57 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/bapi-exceptions/m-p/3854176#M926462</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2008-05-21T18:55:57Z</dc:date>
    </item>
    <item>
      <title>Re: BAPI exceptions</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/bapi-exceptions/m-p/3854177#M926463</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;See these: &lt;SPAN __jive_macro_name="thread" id="425497"&gt;&lt;/SPAN&gt; and [How To Catch Exceptions When Using BAPI Callable Objects|https://www.sdn.sap.com/irj/sdn/weblogs?blog=/pub/wlg/3795] &lt;B&gt;[original link is broken]&lt;/B&gt; &lt;B&gt;[original link is broken]&lt;/B&gt; &lt;B&gt;[original link is broken]&lt;/B&gt;;.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If usefull please rewards.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 21 May 2008 18:58:22 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/bapi-exceptions/m-p/3854177#M926463</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2008-05-21T18:58:22Z</dc:date>
    </item>
    <item>
      <title>Re: BAPI exceptions</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/bapi-exceptions/m-p/3854178#M926464</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;when you are creating your own 'BAPI', you should not maintain the exceptions, but use the return table (structure BAPIRET2), to 'catch' all messages generated by the BAPI and send it back to the calling application.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;However, what you should do is add two standard exceptions when calling the BAPI for catching communication failures and system failures (short dumps for example) in the calling system. Just copy and paste this behind the BAPI when calling it:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;EXCEPTIONS&lt;/P&gt;&lt;P&gt;system_failure = 1 MESSAGE return_message&lt;/P&gt;&lt;P&gt;communication_failure = 2 MESSAGE return_message&lt;/P&gt;&lt;P&gt;OTHERS.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;return_message can be defined as type c length 255.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;[using predefined exceptions for RFC|http://help.sap.com/saphelp_nw70/helpdata/EN/22/0425e0488911d189490000e829fbbd/content.htm]&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Edited by: Micky Oestreich on May 21, 2008 9:28 PM&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 21 May 2008 19:27:08 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/bapi-exceptions/m-p/3854178#M926464</guid>
      <dc:creator>Sm1tje</dc:creator>
      <dc:date>2008-05-21T19:27:08Z</dc:date>
    </item>
  </channel>
</rss>

