<?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: Catching a runtime error in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/catching-a-runtime-error/m-p/2342857#M516584</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;According to help, these are the catchable exceptions for a form call:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Catchable Exceptions &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;CX_SY_PROGRAM_NOT_FOUND &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Cause: The specified program was not found. &lt;/P&gt;&lt;P&gt;Runtime Error: LOAD_PROGRAM_NOT_FOUND &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Cause: The specified program cannot exist because the program name is longer than 40 characters. &lt;/P&gt;&lt;P&gt;Runtime Error: PERFORM_PROGRAM_NAME_TOO_LONG &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;CX_SY_DYN_CALL_ILLEGAL_FORM &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Cause: The specified subroutine was not found. &lt;/P&gt;&lt;P&gt;Runtime Error: PERFORM_NOT_FOUND &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Cause: The specified index was too small. &lt;/P&gt;&lt;P&gt;Runtime Error: PERFORM_INDEX_0 &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Cause: The specified index was negative. &lt;/P&gt;&lt;P&gt;Runtime Error: PERFORM_INDEX_NEGATIVE &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Cause: The specified index was too large. &lt;/P&gt;&lt;P&gt;Runtime Error: PERFORM_INDEX_TOO_LARGE &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;CX_SY_DYN_CALL_PARAM_MISSING &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Cause: The called FORM expects more parameters than were specified. &lt;/P&gt;&lt;P&gt;Runtime Error: PERFORM_PARAMETER_MISSING &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;CX_SY_DYN_CALL_PARAM_NOT_FOUND &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Cause: More parameters were specified than expected by FORM. &lt;/P&gt;&lt;P&gt;Runtime Error: PERFORM_TOO_MANY_PARAMETERS &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;CX_SY_DYN_CALL_ILLEGAL_TYPE &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Cause: In the parameter transfer using the addition STRUCTURE, the addressing offsets/&amp;gt; do not match in the current and target structures. &lt;/P&gt;&lt;P&gt;Runtime Error: PERFORM_BASE_WRONG_ALIGNMENT &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Cause: The deep components contained in the current and target structures cannot be passed to each other. This error can only occur in parameter transfer using STRUCTURE. &lt;/P&gt;&lt;P&gt;Runtime Error: PERFORM_CAST_DEEP_MISMATCH &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Cause: During the transfer of a generically defined type to the form, a type conflict occurred. &lt;/P&gt;&lt;P&gt;Runtime Error: PERFORM_CONFLICT_GENERIC_TYPE &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Cause: The table type of the current parameter does not match the table type of the parameter defined in the form. &lt;/P&gt;&lt;P&gt;Runtime Error: PERFORM_CONFLICT_TAB_TYPE &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Cause: The type of current parameter does not match the type of parameter defined in the form. &lt;/P&gt;&lt;P&gt;Runtime Error: PERFORM_CONFLICT_TYPE &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Cause: The current parameter occupies less storage space than the target parameter defined in the form. This error occurs only with parameter specification using STRUCTURE. &lt;/P&gt;&lt;P&gt;Runtime Error: PERFORM_PARAMETER_TOO_SHORT &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Cause: During parameter transfer with the addition STRUCTURE, the fragment views of the current and target parameters do not match. This error only occurs in Unicode programs in &lt;/P&gt;&lt;P&gt;Runtime Error: PERFORM_CONFLICT_UC_STRUCT &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Cause:When the form is called, an internal table is expected as current parameter. &lt;/P&gt;&lt;P&gt;Runtime Error: PERFORM_TABLE_REQUIRED &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Cause: A hash table was passed to a parameter defined using TABLES. &lt;/P&gt;&lt;P&gt;Runtime Error: PERFORM_STD_TAB_REQUIRED&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 12 Jun 2007 18:37:12 GMT</pubDate>
    <dc:creator>Former Member</dc:creator>
    <dc:date>2007-06-12T18:37:12Z</dc:date>
    <item>
      <title>Catching a runtime error</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/catching-a-runtime-error/m-p/2342855#M516582</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;A runtime error for overflow (type p) occurs with the following details:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Runtime Errors         COMPUTE_BCD_OVERFLOW     &lt;/P&gt;&lt;P&gt;Exception              CX_SY_ARITHMETIC_OVERFLOW&lt;/P&gt;&lt;P&gt;Date and Time          06/12/2007 11:33:13      &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Instead of displaying the dump screen, i'd like to catch the runtime error and display a message instead. The following is the code that causes the error (onhand is too large):&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;      REQRMENT = FORECAST - ONHAND - OPENQTY.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Please help,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Points will be rewarded and all help will be greatly appreciated.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;John&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 12 Jun 2007 17:50:40 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/catching-a-runtime-error/m-p/2342855#M516582</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-06-12T17:50:40Z</dc:date>
    </item>
    <item>
      <title>Re: Catching a runtime error</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/catching-a-runtime-error/m-p/2342856#M516583</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Wrap it with a CATCH.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;PRE&gt;&lt;CODE&gt;


catch system-exceptions compute_bcd_overflow = 1.
 REQRMENT = FORECAST - ONHAND - OPENQTY.
endcatch.

if sy-subrc  = 1.
* Handle the exception
Endif.

&lt;/CODE&gt;&lt;/PRE&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Rich Heilman&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 12 Jun 2007 17:55:05 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/catching-a-runtime-error/m-p/2342856#M516583</guid>
      <dc:creator>RichHeilman</dc:creator>
      <dc:date>2007-06-12T17:55:05Z</dc:date>
    </item>
    <item>
      <title>Re: Catching a runtime error</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/catching-a-runtime-error/m-p/2342857#M516584</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;According to help, these are the catchable exceptions for a form call:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Catchable Exceptions &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;CX_SY_PROGRAM_NOT_FOUND &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Cause: The specified program was not found. &lt;/P&gt;&lt;P&gt;Runtime Error: LOAD_PROGRAM_NOT_FOUND &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Cause: The specified program cannot exist because the program name is longer than 40 characters. &lt;/P&gt;&lt;P&gt;Runtime Error: PERFORM_PROGRAM_NAME_TOO_LONG &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;CX_SY_DYN_CALL_ILLEGAL_FORM &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Cause: The specified subroutine was not found. &lt;/P&gt;&lt;P&gt;Runtime Error: PERFORM_NOT_FOUND &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Cause: The specified index was too small. &lt;/P&gt;&lt;P&gt;Runtime Error: PERFORM_INDEX_0 &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Cause: The specified index was negative. &lt;/P&gt;&lt;P&gt;Runtime Error: PERFORM_INDEX_NEGATIVE &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Cause: The specified index was too large. &lt;/P&gt;&lt;P&gt;Runtime Error: PERFORM_INDEX_TOO_LARGE &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;CX_SY_DYN_CALL_PARAM_MISSING &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Cause: The called FORM expects more parameters than were specified. &lt;/P&gt;&lt;P&gt;Runtime Error: PERFORM_PARAMETER_MISSING &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;CX_SY_DYN_CALL_PARAM_NOT_FOUND &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Cause: More parameters were specified than expected by FORM. &lt;/P&gt;&lt;P&gt;Runtime Error: PERFORM_TOO_MANY_PARAMETERS &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;CX_SY_DYN_CALL_ILLEGAL_TYPE &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Cause: In the parameter transfer using the addition STRUCTURE, the addressing offsets/&amp;gt; do not match in the current and target structures. &lt;/P&gt;&lt;P&gt;Runtime Error: PERFORM_BASE_WRONG_ALIGNMENT &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Cause: The deep components contained in the current and target structures cannot be passed to each other. This error can only occur in parameter transfer using STRUCTURE. &lt;/P&gt;&lt;P&gt;Runtime Error: PERFORM_CAST_DEEP_MISMATCH &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Cause: During the transfer of a generically defined type to the form, a type conflict occurred. &lt;/P&gt;&lt;P&gt;Runtime Error: PERFORM_CONFLICT_GENERIC_TYPE &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Cause: The table type of the current parameter does not match the table type of the parameter defined in the form. &lt;/P&gt;&lt;P&gt;Runtime Error: PERFORM_CONFLICT_TAB_TYPE &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Cause: The type of current parameter does not match the type of parameter defined in the form. &lt;/P&gt;&lt;P&gt;Runtime Error: PERFORM_CONFLICT_TYPE &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Cause: The current parameter occupies less storage space than the target parameter defined in the form. This error occurs only with parameter specification using STRUCTURE. &lt;/P&gt;&lt;P&gt;Runtime Error: PERFORM_PARAMETER_TOO_SHORT &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Cause: During parameter transfer with the addition STRUCTURE, the fragment views of the current and target parameters do not match. This error only occurs in Unicode programs in &lt;/P&gt;&lt;P&gt;Runtime Error: PERFORM_CONFLICT_UC_STRUCT &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Cause:When the form is called, an internal table is expected as current parameter. &lt;/P&gt;&lt;P&gt;Runtime Error: PERFORM_TABLE_REQUIRED &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Cause: A hash table was passed to a parameter defined using TABLES. &lt;/P&gt;&lt;P&gt;Runtime Error: PERFORM_STD_TAB_REQUIRED&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 12 Jun 2007 18:37:12 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/catching-a-runtime-error/m-p/2342857#M516584</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-06-12T18:37:12Z</dc:date>
    </item>
  </channel>
</rss>

