<?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 Cascading exceptions through calling chain in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/cascading-exceptions-through-calling-chain/m-p/5754915#M1303818</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Debbuging SAP code over the years, I often witnessed a situation where exceptions were cascading automatically between successive nested function calls. I try to reproduce the same without success &lt;SPAN __jive_emoticon_name="sad"&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If I do not declare the exception at the call, I end up with a short dump(classic), if I do declare it, then I get the requested subrc but it does not casade back to the calling function.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;How the hell SAP manages this &lt;SPAN __jive_emoticon_name="wink"&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 27 May 2009 19:58:58 GMT</pubDate>
    <dc:creator>Former Member</dc:creator>
    <dc:date>2009-05-27T19:58:58Z</dc:date>
    <item>
      <title>Cascading exceptions through calling chain</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/cascading-exceptions-through-calling-chain/m-p/5754915#M1303818</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Debbuging SAP code over the years, I often witnessed a situation where exceptions were cascading automatically between successive nested function calls. I try to reproduce the same without success &lt;SPAN __jive_emoticon_name="sad"&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If I do not declare the exception at the call, I end up with a short dump(classic), if I do declare it, then I get the requested subrc but it does not casade back to the calling function.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;How the hell SAP manages this &lt;SPAN __jive_emoticon_name="wink"&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 27 May 2009 19:58:58 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/cascading-exceptions-through-calling-chain/m-p/5754915#M1303818</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2009-05-27T19:58:58Z</dc:date>
    </item>
    <item>
      <title>Re: Cascading exceptions through calling chain</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/cascading-exceptions-through-calling-chain/m-p/5754916#M1303819</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I don't exactly understand the situation, but if in the calling program, you put something like:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;CALL FUNCTION abc&lt;/P&gt;&lt;P&gt;  EXPORTING&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;  IMPORTING&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;  TABLES&lt;/P&gt;&lt;P&gt;  EXCEPTIONS&lt;/P&gt;&lt;P&gt;   error_message = 1.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Any A,E errors in the called FM will be handled/cascaded to the calling program.&lt;/P&gt;&lt;P&gt;For more information, check out the online documentation (t-code ABAPDOCU) for 'CALL FUNCTION' &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks &amp;amp; regards,&lt;/P&gt;&lt;P&gt;Hadiman&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 28 May 2009 01:56:01 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/cascading-exceptions-through-calling-chain/m-p/5754916#M1303819</guid>
      <dc:creator>hadiman_ngoei</dc:creator>
      <dc:date>2009-05-28T01:56:01Z</dc:date>
    </item>
  </channel>
</rss>

