<?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: Passing Error message to BAPI Structure in RFC in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/passing-error-message-to-bapi-structure-in-rfc/m-p/5249418#M1212824</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Like already mentioned before, every Standard SAP BAPI, has an export or tables parameter which is called something like RETURN with structure BAPIRET2. In here, you can store all the messages that are generated during the BAPI Call.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;However, if you also want to catch errors like system exceptions and communication errors, you will have to add these exceptions manually:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;EXCEPTIONS&lt;/P&gt;&lt;P&gt;     SYSTEM_FAILURE        = 1 MESSAGE RFC_MESS&lt;/P&gt;&lt;P&gt;     COMMUNICATION_FAILURE = 2 MESSAGE RFC_MESS.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;However, not sure if this addition works when calling BAPI from NON-sap application.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Declaration:&lt;/P&gt;&lt;P&gt;DATA: RFC_MESS(128).&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Fri, 20 Feb 2009 07:32:39 GMT</pubDate>
    <dc:creator>Sm1tje</dc:creator>
    <dc:date>2009-02-20T07:32:39Z</dc:date>
    <item>
      <title>Passing Error message to BAPI Structure in RFC</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/passing-error-message-to-bapi-structure-in-rfc/m-p/5249416#M1212822</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Experts,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I would like to know how we pass error message to BAPI structurre in RFC?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Plz some one give the details about how we handle the errors.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks in advance.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 20 Feb 2009 06:56:29 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/passing-error-message-to-bapi-structure-in-rfc/m-p/5249416#M1212822</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2009-02-20T06:56:29Z</dc:date>
    </item>
    <item>
      <title>Re: Passing Error message to BAPI Structure in RFC</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/passing-error-message-to-bapi-structure-in-rfc/m-p/5249417#M1212823</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;hi:&lt;/P&gt;&lt;P&gt;In RFC function module, there should have an export parameter like BAPIRETURN &lt;/P&gt;&lt;P&gt;which would carry the error message.&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;Shashi&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 20 Feb 2009 06:59:22 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/passing-error-message-to-bapi-structure-in-rfc/m-p/5249417#M1212823</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2009-02-20T06:59:22Z</dc:date>
    </item>
    <item>
      <title>Re: Passing Error message to BAPI Structure in RFC</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/passing-error-message-to-bapi-structure-in-rfc/m-p/5249418#M1212824</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Like already mentioned before, every Standard SAP BAPI, has an export or tables parameter which is called something like RETURN with structure BAPIRET2. In here, you can store all the messages that are generated during the BAPI Call.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;However, if you also want to catch errors like system exceptions and communication errors, you will have to add these exceptions manually:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;EXCEPTIONS&lt;/P&gt;&lt;P&gt;     SYSTEM_FAILURE        = 1 MESSAGE RFC_MESS&lt;/P&gt;&lt;P&gt;     COMMUNICATION_FAILURE = 2 MESSAGE RFC_MESS.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;However, not sure if this addition works when calling BAPI from NON-sap application.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Declaration:&lt;/P&gt;&lt;P&gt;DATA: RFC_MESS(128).&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 20 Feb 2009 07:32:39 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/passing-error-message-to-bapi-structure-in-rfc/m-p/5249418#M1212824</guid>
      <dc:creator>Sm1tje</dc:creator>
      <dc:date>2009-02-20T07:32:39Z</dc:date>
    </item>
    <item>
      <title>Re: Passing Error message to BAPI Structure in RFC</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/passing-error-message-to-bapi-structure-in-rfc/m-p/5249419#M1212825</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Use table BAPIRET2 to get the error messages, when you are using BAPI as RFC you will not get return parameters. You have to call it in synchronous task and wait till the BAPI returns and catch the errors.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 20 Feb 2009 07:51:42 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/passing-error-message-to-bapi-structure-in-rfc/m-p/5249419#M1212825</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2009-02-20T07:51:42Z</dc:date>
    </item>
  </channel>
</rss>

