<?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: What are exceptions?.... in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/what-are-exceptions/m-p/2682619#M620175</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Error situation during execution of an ABAP program. Exceptions are treatable (statements TRY, CATCH) or untreatable. Untreated exceptions result in a runtime error. An exception is triggered either by the ABAP runtime environment due to error situations that are not foreseeable by the static program check, or by the RAISE EXCEPTION statement. Before release 6.10, exceptions could be defined only in interfaces of function modules and methods. As of release 6.10, there are class-based exceptions, which include the catchable runtime errors.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Treatable Exception &lt;/P&gt;&lt;P&gt;Exception that can be treated in the program and that does not lead to a runtime error when treated. As of Release 6.10, all treatable exceptions are implemented by means of exception objects and can be treated using TRY-CATCH-ENDTRY statements. Before Release 6.10, selected runtime errors could be caught with CATCH-ENDCATCH.&lt;/P&gt;&lt;P&gt; &lt;/P&gt;&lt;P&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;&lt;/P&gt;&lt;P&gt;Preeti&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 14 Aug 2007 08:43:05 GMT</pubDate>
    <dc:creator>Former Member</dc:creator>
    <dc:date>2007-08-14T08:43:05Z</dc:date>
    <item>
      <title>What are exceptions?....</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/what-are-exceptions/m-p/2682618#M620174</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;    What are exceptions?...and how to rectify if exceptions occurs while executing &lt;/P&gt;&lt;P&gt;a programme.&lt;/P&gt;&lt;P&gt;Thanks in Advance.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Ashok kumar&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 14 Aug 2007 08:40:01 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/what-are-exceptions/m-p/2682618#M620174</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-08-14T08:40:01Z</dc:date>
    </item>
    <item>
      <title>Re: What are exceptions?....</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/what-are-exceptions/m-p/2682619#M620175</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Error situation during execution of an ABAP program. Exceptions are treatable (statements TRY, CATCH) or untreatable. Untreated exceptions result in a runtime error. An exception is triggered either by the ABAP runtime environment due to error situations that are not foreseeable by the static program check, or by the RAISE EXCEPTION statement. Before release 6.10, exceptions could be defined only in interfaces of function modules and methods. As of release 6.10, there are class-based exceptions, which include the catchable runtime errors.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Treatable Exception &lt;/P&gt;&lt;P&gt;Exception that can be treated in the program and that does not lead to a runtime error when treated. As of Release 6.10, all treatable exceptions are implemented by means of exception objects and can be treated using TRY-CATCH-ENDTRY statements. Before Release 6.10, selected runtime errors could be caught with CATCH-ENDCATCH.&lt;/P&gt;&lt;P&gt; &lt;/P&gt;&lt;P&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;&lt;/P&gt;&lt;P&gt;Preeti&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 14 Aug 2007 08:43:05 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/what-are-exceptions/m-p/2682619#M620175</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-08-14T08:43:05Z</dc:date>
    </item>
    <item>
      <title>Re: What are exceptions?....</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/what-are-exceptions/m-p/2682620#M620176</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Exceptions are situations that occur while an ABAP program is being executed, in which normal continuation of the program does not make any sense. Exceptions can be raised either implicitly in the ABAP runtime environment or explicitly in the ABAP program. For example, division by zero leads to an exception in the ABAP runtime environment. It is possible to determine this situation through a query in the ABAP program and to trigger an exception there. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;There are two main types of exceptions:  those that can be handled and those that cannot be handled.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;·         Exceptions that can be handled occur in error situations in the runtime environment or in the ABAP program, where the program can continue executing after the ABAP program has handled the exception, without the system ending up in a critical state. If such an exception is not handled, a runtime error occurs. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;·         The second type of exceptions are those that cannot be handled. These are critical error situations in the runtime environment. Handling with ABAP means is not possible and they always cause a runtime error. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;As of Release 6.10, exceptions and their handling are generally based on exception classes. This concept covers the functions of the preceding concepts, enhances them, and thus replaces them.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt; &lt;/P&gt;&lt;P&gt;For More Info,&lt;/P&gt;&lt;P&gt;&lt;A href="http://help.sap.com/saphelp_nw04s/helpdata/en/a0/ff934258a5c76ae10000000a155106/frameset.htm" target="test_blank"&gt;http://help.sap.com/saphelp_nw04s/helpdata/en/a0/ff934258a5c76ae10000000a155106/frameset.htm&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://help.sap.com/saphelp_nw04s/helpdata/en/cf/f2bbc8142c11d3b93a0000e8353423/frameset.htm" target="test_blank"&gt;http://help.sap.com/saphelp_nw04s/helpdata/en/cf/f2bbc8142c11d3b93a0000e8353423/frameset.htm&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://help.sap.com/saphelp_nw04/helpdata/en/83/636d1d12fc11d5991e00508b5d5211/frameset.htm" target="test_blank"&gt;http://help.sap.com/saphelp_nw04/helpdata/en/83/636d1d12fc11d5991e00508b5d5211/frameset.htm&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Padmam.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 14 Aug 2007 08:43:30 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/what-are-exceptions/m-p/2682620#M620176</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-08-14T08:43:30Z</dc:date>
    </item>
    <item>
      <title>Re: What are exceptions?....</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/what-are-exceptions/m-p/2682621#M620177</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi..&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Exceptions are the Situations that cannot be handled by the Runtime system during the Execution of a Program.&lt;/P&gt;&lt;P&gt;For Eg: DIVIDE BY ZERO&lt;/P&gt;&lt;P&gt;            ARITHMETIC OVERFLOW.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;We can use the CATCH .. ENDCATCH statements to handle the Exceptions in a program to Prevent the runtime errors.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Press F1 ON CATCH statement to See more info..&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;lt;b&amp;gt;Reward if Helpful&amp;lt;/b&amp;gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 14 Aug 2007 08:46:33 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/what-are-exceptions/m-p/2682621#M620177</guid>
      <dc:creator>varma_narayana</dc:creator>
      <dc:date>2007-08-14T08:46:33Z</dc:date>
    </item>
    <item>
      <title>Re: What are exceptions?....</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/what-are-exceptions/m-p/2682622#M620178</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Ashok&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;exceptions are nothing but breaking the shortdump errors, instead of sisplaying shortdump errors( end users dont know shortdump informations) so in this cases we use exceptions by checking the sy-subrc value and we can define our own messages accordingg to exceptions....&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;reward points to all helpful answers &lt;/P&gt;&lt;P&gt;kiran.M&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 14 Aug 2007 08:47:34 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/what-are-exceptions/m-p/2682622#M620178</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-08-14T08:47:34Z</dc:date>
    </item>
    <item>
      <title>Re: What are exceptions?....</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/what-are-exceptions/m-p/2682623#M620179</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi &lt;/P&gt;&lt;P&gt;reward if  usefull&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Definition:-&lt;/P&gt;&lt;P&gt;An exception is an event, which occurs during the execution of a program, that disrupts the normal flow of the program's instructions. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;if an exception occurs you can handle that exception by througing an Error message like this &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;example :-&lt;/P&gt;&lt;P&gt;when creating the function module &lt;/P&gt;&lt;P&gt;&amp;lt;b&amp;gt;&lt;/P&gt;&lt;P&gt;RAISE EXECPTION NAME&amp;lt;/b&amp;gt; &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;in report program &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;CALL FUNCTION 'GUI_UPLOAD'&lt;/P&gt;&lt;P&gt;  EXPORTING&lt;/P&gt;&lt;P&gt;    FILENAME                      = 'C:\NARESH\NARESH.TXT'&lt;/P&gt;&lt;UL&gt;&lt;LI level="1" type="ul"&gt;&lt;P&gt;  FILETYPE                      = 'ASC'&lt;/P&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;   HAS_FIELD_SEPARATOR           = 'X'&lt;/P&gt;&lt;UL&gt;&lt;LI level="1" type="ul"&gt;&lt;P&gt;  HEADER_LENGTH                 = 0&lt;/P&gt;&lt;/LI&gt;&lt;LI level="1" type="ul"&gt;&lt;P&gt;  READ_BY_LINE                  = 'X'&lt;/P&gt;&lt;/LI&gt;&lt;LI level="1" type="ul"&gt;&lt;P&gt;  DAT_MODE                      = ' '&lt;/P&gt;&lt;/LI&gt;&lt;LI level="1" type="ul"&gt;&lt;P&gt;  CODEPAGE                      = ' '&lt;/P&gt;&lt;/LI&gt;&lt;LI level="1" type="ul"&gt;&lt;P&gt;  IGNORE_CERR                   = ABAP_TRUE&lt;/P&gt;&lt;/LI&gt;&lt;LI level="1" type="ul"&gt;&lt;P&gt;  REPLACEMENT                   = '#'&lt;/P&gt;&lt;/LI&gt;&lt;LI level="1" type="ul"&gt;&lt;P&gt;  CHECK_BOM                     = ' '&lt;/P&gt;&lt;/LI&gt;&lt;LI level="1" type="ul"&gt;&lt;P&gt;  VIRUS_SCAN_PROFILE            =&lt;/P&gt;&lt;/LI&gt;&lt;LI level="1" type="ul"&gt;&lt;P&gt;  NO_AUTH_CHECK                 = ' '&lt;/P&gt;&lt;/LI&gt;&lt;LI level="1" type="ul"&gt;&lt;P&gt;IMPORTING&lt;/P&gt;&lt;/LI&gt;&lt;LI level="1" type="ul"&gt;&lt;P&gt;  FILELENGTH                    =&lt;/P&gt;&lt;/LI&gt;&lt;LI level="1" type="ul"&gt;&lt;P&gt;  HEADER                        =&lt;/P&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;  TABLES&lt;/P&gt;&lt;P&gt;    DATA_TAB                      = ITAB&lt;/P&gt;&lt;P&gt; &amp;lt;b&amp;gt;EXCEPTIONS&lt;/P&gt;&lt;P&gt;   FILE_OPEN_ERROR               = 1&lt;/P&gt;&lt;P&gt;   FILE_READ_ERROR               = 2&lt;/P&gt;&lt;P&gt;   NO_BATCH                      = 3&lt;/P&gt;&lt;P&gt;   GUI_REFUSE_FILETRANSFER       = 4&lt;/P&gt;&lt;P&gt;   INVALID_TYPE                  = 5&lt;/P&gt;&lt;P&gt;   NO_AUTHORITY                  = 6&lt;/P&gt;&lt;P&gt;   UNKNOWN_ERROR                 = 7&lt;/P&gt;&lt;P&gt;   BAD_DATA_FORMAT               = 8&lt;/P&gt;&lt;P&gt;   HEADER_NOT_ALLOWED            = 9&lt;/P&gt;&lt;P&gt;   SEPARATOR_NOT_ALLOWED         = 10&lt;/P&gt;&lt;P&gt;   HEADER_TOO_LONG               = 11&lt;/P&gt;&lt;P&gt;   UNKNOWN_DP_ERROR              = 12&lt;/P&gt;&lt;P&gt;   ACCESS_DENIED                 = 13&lt;/P&gt;&lt;P&gt;   DP_OUT_OF_MEMORY              = 14&lt;/P&gt;&lt;P&gt;   DISK_FULL                     = 15&lt;/P&gt;&lt;P&gt;   DP_TIMEOUT                    = 16&lt;/P&gt;&lt;P&gt;   OTHERS                        = 17&lt;/P&gt;&lt;P&gt;          .&lt;/P&gt;&lt;P&gt;IF SY-SUBRC &amp;lt;&amp;gt; 0.&lt;/P&gt;&lt;P&gt;  MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO&lt;/P&gt;&lt;P&gt;          WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.&lt;/P&gt;&lt;P&gt;ENDIF.&amp;lt;/b&amp;gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 14 Aug 2007 09:03:25 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/what-are-exceptions/m-p/2682623#M620179</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-08-14T09:03:25Z</dc:date>
    </item>
  </channel>
</rss>

