topic Re: Exception catch in Application Development and Automation Discussions

Exception catch

Former Member — Fri, 13 Jun 2008 14:06:04 GMT

Hello Friends,

I have a form routine, and I try to read an excel file, I would like to know ( as there could be different kind of exceptions happends ) is there any standard or top most exceptoin class which I can use to catch all exception ?

I know this way from java, would like to konw if we have something like this in abap as welll....

Regards,

Re: Exception catch

Former Member — Fri, 13 Jun 2008 14:26:47 GMT

Hi,

If you are using TRY then you can catch all the all the exceptions in CX_ROOT.

TRY.

CATCH CX_ROOT.

ENDTRY.

Re: Exception catch

sivasatyaprasad_yerra — Fri, 13 Jun 2008 14:29:17 GMT

Hi,

We can use CX_DYNAMIC_CHECK for root exception.

The following text is from ABAP help.

Exception Classes for ABAP Statements

Exceptions in ABAP statements that can be handled can be caught using the predefined exception classes listed below. These exception classes are all subclasses of the CX_DYNAMIC_CHECK and CX_NO_CHECK classes. They replace the previous catchable runtime errors. The keyword documentation lists all the exceptions that can occur for each statement.

To improve the structure, intermediate abstract classes were introduced so that groups of exceptions can be caught simultaneously.

Each exception class includes message texts, which you can display by choosing the Texts tab in the Class Builder. The following links open the Class Builder for the corresponding exception class.

CX_ROOT

|--CX_STATIC_CHECK

|--CX_DYNAMIC_CHECK

| |

| |--CX_SY_ARITHMETIC_ERROR

| | |

| | |--CX_SY_ZERODIVIDE

| | |

| | |--CX_SY_ARITHMETIC_OVERFLOW

| | |

| | |--CX_SY_ARG_OUT_OF_DOMAIN

| | |

| | |--CX_SY_PRECISION_LOSS

| |

| |--CX_SY_ASSIGN_ERROR

| | |

| | |--CX_SY_ASSIGN_CAST_ERROR

| | | |

| | | |--CX_SY_ASSIGN_CAST_ILLEGAL_CAST

| | | |

| | | |--CX_SY_ASSIGN_CAST_UNKNOWN_TYPE

| | |

| | |--CX_SY_ASSIGN_OUT_OF_RANGE

| |

| |--CX_SY_CODEPAGE_CONVERTER_INIT

| |

| |--CX_SY_CONVERSION_ERROR

| | |

| | |--CX_SY_CONVERSION_CODEPAGE

| | |

| | |--CX_SY_CONVERSION_DATA_LOSS

| | |

| | |--CX_SY_CONVERSION_NO_BOOLEAN

| | |

| | |--CX_SY_CONVERSION_NO_DATE_TIME

| | |

| | |--CX_SY_CONVERSION_NO_NUMBER

| | |

| | |--CX_SY_CONVERSION_NO_RAW

| | |

| | |--CX_SY_CONVERSION_NO_UUID

| | |

| | |--CX_SY_CONVERSION_OVERFLOW

| | |

| | |--CX_SY_CONVERSION_ROUNDING

| | |

| | |--CX_SY_CONVERSION_UNKNOWN_LANGU

| |

| |--CX_SY_CREATE_ERROR

| | |

| | |--CX_SY_CREATE_OBJECT_ERROR

| | |

| | |--CX_SY_CREATE_DATA_ERROR

| |

| |--CX_SY_DATA_ACCESS_ERROR

| | |

| | |--CX_SY_RANGE_OUT_OF_BOUNDS

| | |

| | |--CX_SY_TAB_RANGE_OUT_OF_BOUNDS

| | |

| | |--CX_SY_OFFSET_NOT_ALLOWED

| |

| |--CX_SY_DYN_CALL_ERROR

| | |

| | |--CX_SY_DYN_CALL_ILLEGAL_CLASS

| | |

| | |--CX_SY_DYN_CALL_ILLEGAL_FORM

| | |

| | |--CX_SY_DYN_CALL_ILLEGAL_FUNC

| | |

| | |--CX_SY_DYN_CALL_ILLEGAL_METHOD

| | |

| | |--CX_SY_DYN_CALL_PARAMETER_ERROR

| | |

| | |--CX_SY_DYN_CALL_EXCP_NOT_FOUND

| | |

| | |--CX_SY_DYN_CALL_ILLEGAL_TYPE

| | |

| | |--CX_SY_DYN_CALL_PARAM_MISSING

| | |

| | |--CX_SY_DYN_CALL_PARAM_NOT_FOUND

| |

| |--CX_SY_EXPORT_NO_SHARED_MEMORY

| |

| |--CX_SY_FILE_ACCESS_ERROR

| | |

| | |--CX_SY_FILE_AUTHORITY

| | |

| | |--CX_SY_FILE_CLOSE

| | |

| | |--CX_SY_FILE_IO

| | |

| | |--CX_SY_FILE_OPEN

| | |

| | |--CX_SY_FILE_OPEN_MODE

| | |

| | |--CX_SY_FILE_POSITION

| | |

| | |--CX_SY_FILE_TRUNCATE

| |

| |--CX_SY_FIND_INFINITE_LOOP

| |

| |--CX_SY_GEN_SOURCE_TOO_WIDE

| |

| |--CX_SY_IMPORT_MISMATCH_ERROR

| | |

| | |--CX_SY_IMPORT_FORMAT_ERROR

| |

| |--CX_SY_ITAB_ERROR

| | |

| | |--CX_SY_ITAB_DUPLICATE_KEY

| |

| |--CX_SY_MATCHER

| | |

| | |--CX_SY_REGEX_TOO_COMPLEX

| | |

| | |--CX_SY_INVALID_REGEX_FORMAT

| |

| |--CX_SY_MOVE_CAST_ERROR

| |

| |--CX_SY_PROGRAM_NOT_FOUND

| |

| |--CX_SY_PROVIDE_EXCEPTION

| | |

| | |--CX_SY_PROVIDE_INTERVAL_OVERLAP

| | |

| | |--CX_SY_PROVIDE_TABLE_NOT_SORTED

| |

| |--CX_SY_READ_SRC_LINE_TOO_LONG

| |

| |--CX_SY_REF_IS_INITIAL | |

| |--CX_SY_REGEX

| | |

| | |--CX_SY_INVALID_REGEX

| |

| |--CX_SY_REPLACE_INFINITE_LOOP

| |

| |--CX_SY_SCAN_SOURCE_TOO_WIDE

| |

| |--CX_SY_SQL_ERROR

| | |

| | |--CX_SY_OPEN_SQL_ERROR

| | | |

| | | |--CX_SY_OPEN_SQL_DB

| | | |

| | | |--CX_SY_DYNAMIC_OSQL_ERROR

| | | |

| | | |--CX_SY_DYNAMIC_OSQL_SEMANTICS

| | | |

| | | |--CX_SY_DYNAMIC_OSQL_SYNTAX

| | |

| | |--CX_SY_NATIVE_SQL_ERROR

| |

| |--CX_SY_UNKNOWN_CURRENCY

| |

| |--CX_SY_WRITE_INVALID_STYLE

| |

| |--CX_SY_WRITE_SRC_LINE_TOO_LONG

| |

| |--CX_TRANSFORMATION_ERROR

| |

| |--CX_ST_ERROR

| | |

| | |--CX_ST_CALL_ERROR

| | |

| | |--CX_ST_CALL_METHOD_ERROR

| | |

| | |--CX_ST_CONSTRAINT_ERROR

| | |

| | |--CX_ST_CONDITION

| | |

| | |--CX_ST_DESERIALIZATION_ERROR

| | |

| | |--CX_ST_FORMAT_ERROR

| | |

| | |--CX_ST_INVALID_XML

| | |

| | |--CX_ST_MATCH

| | |

| | |--CX_ST_REF_ACCESS

| | |

| | |--CX_ST_RUNTIME_ERROR

| | |

| | |--CX_ST_SERIALIZATION_ERROR

| |

| |--CX_XSLT_EXCEPTION

| |

| |--CX_XSLT_SYSTEM_ERROR

| |

| |--CX_XSLT_ABAP_CALL_ERROR

| |

| |--CX_XSLT_DESERIALIZATION_ERROR

| |

| |--CX_XSLT_FORMAT_ERROR

| |

| |--CX_XSLT_RUNTIME_ERROR

| |

| |--CX_XSLT_SERIALIZATION_ERROR

|--CX_NO_CHECK

|--CX_BADI

| |

| |--CX_BADI_CONTEXT_ERROR

| |

| |--CX_BADI_FILTER_ERROR

| |

| |--CX_BADI_INITIAL_CONTEXT

| |

| |--CX_BADI_INITIAL_REFERENCE

| |

| |--CX_BADI_NOT_SINGLE_USE

| | |

| | |--CX_BADI_MULTIPLY_IMPLEMENTED

| | |

| | |--CX_BADI_NOT_IMPLEMENTED

| |

| |--CX_BADI_UNKNOWN_ERROR

|--CX_SY_EXPORT_BUFFER_NO_MEMORY

|--CX_SY_GENERATE_SUBPOOL_FULL

|--CX_SY_ILLEGAL_HANDLER

|--CX_SY_LOCALIZATION_ERROR

|--CX_SY_NESTED_PRINT_ON

|--CX_SY_NO_HANDLER

|--CX_SY_PIPES_NOT_SUPPORTED

|--CX_SY_PIPE_REOPEN

|--CX_SY_REMOTE_CALL_ERROR

| |

| |--CX_SY_RMC_COMM_FAILURE

| |

| |--CX_SY_RMC_INVALID_STATUS

| |

| |--CX_SY_RMC_SYSTEM_FAILURE

|--CX_SY_TOO_MANY_FILES

Reward points if useful

Regards,

Siva.

Re: Exception catch

Former Member — Fri, 13 Jun 2008 14:34:57 GMT

Hi,

As mentioned above CX_ROOT is the Parent class of all exceptions, however it wont give you specific messages back.

If you want to know what exceptions are thrown by a statment , press F1 and in the help of that statment you will generally get the exceptions it throws. So you must catch them and in the end catch the cx_root exception.

Here is a code snippet which tries to open a file on the application server and when failed it catches certian exceptions and displays message :


* Try to open the data set and catch the appropriate exception
  TRY.

      OPEN DATASET l_fsap FOR OUTPUT IN BINARY MODE.

    CATCH cx_sy_file_open INTO lex_file_open.
      MESSAGE lex_file_open->errortext TYPE 'I'.
    CATCH cx_sy_file_access_error INTO lex_file_access.
      MESSAGE lex_file_access->filename TYPE 'I'.
   CATCH cx_root INTO lex_root.
      MESSAGE 'Exception occured TYPE 'I'.


  ENDTRY.

  IF sy-subrc = 0.
    LOOP AT it_binarcobj INTO w_binarcobj.

      TRY.

          TRANSFER w_binarcobj TO l_fsap.

        CATCH cx_sy_file_io INTO lex_file_io.
          MESSAGE lex_file_io->errortext TYPE 'I'.
        CATCH cx_sy_file_access_error INTO lex_file_access.
          MESSAGE lex_file_access->filename TYPE 'I'.
   CATCH cx_root INTO lex_root.
      MESSAGE 'Exception occured TYPE 'I'.

      ENDTRY.
    ENDLOOP.
  ENDIF.

Re: Exception catch

Former Member — Fri, 13 Jun 2008 14:44:43 GMT

Hi,

http://help.sap.com/saphelp_nw04/helpdata/en/83/636d1712fc11d5991e00508b5d5211/content.htm

http://help.sap.com/saphelp_nw70/helpdata/en/02/c4e6aa19e911d5969b00a0c94260a5/content.htm

https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/f86c9290-0201-0010-7a93-dda3716dc0d2

Class-based exceptions are handled in the following control structure:

TRY.

... " TRY block (application coding)

CATCH cx_... cx_... ...

... " CATCH block (exception handler)

CATCH cx_... cx_... ...

... " CATCH block (exception handler)

...

CLEANUP.

... " CLEANUP block (cleanup context)

ENDTRY.

The TRY statement opens a control structure to be ended with ENDTRY, in which three statement blocks can be listed in a specified order (this is not obligatory).

1. A TRY block, in which exceptions can occur.

This exception block consists of all the statements between the TRY and the CATCH statement.

2. One or more CATCH blocks for catching exceptions.

These exception blocks are initiated with CATCH and ended with a further CATCH, CLEANUP, or ENDTRY.

3. A CLEANUP block for cleanup work after the exceptions have been caught.

This statement block is initiated by CLEANUP and ended with ENDTRY. A TRY-ENDTRY structure must not contain more than one CLEANUP block in precisely this position.

Like all ABAP control structures, TRY-ENDTRY structures can be nested in any statement blocks (see Controlling the Program Flow). In particular, the three statements blocks above can also contain complete TRY-ENDTRY blocks. Like all ABAP control structures, each TRY-ENDTRY structure must be contained fully in a processing block (event block, dialog module, procedure). This means that the application coding of a TRY-ENDTRY structure cannot include several processing blocks.

TRY Block

The TRY block contains the application coding whose exceptions are to be handled. This statement block is processed sequentially. It can contain further control structures and calls of procedures or other ABAP programs.

If an exception occurs in the TRY block or in a procedure called up here, the system starts by searching for a CATCH statement of the same TRY-ENDTRY structure. It then searches from the inside out for a CATCH statement in any enclosing TRY-ENDTRY structures that handle the event. The system may call this handler. If the system does not find a handler, but the TRY-ENDTRY structure is contained in a procedure, it tries to propagate the exception to the caller (see also Propagating Exceptions). Exceptions cannot be propagated in any processing blocks without a local data area (event blocks, dialog modules). A runtime error occurs immediately if the handler is missing.

If no exceptions occur in the TRY block, program execution is continued directly after ENDTRY after the block has been completed.

CATCH Block

A catch block contains the exception handler that is executed when a particular exception has occurred in the TRY block of the same TRY-ENDTRY structure. A TRY-ENDTRY structure can contain several exception handlers. The syntax for introducing an exception handler is:

CATCH cx_... cx_... INTO ref.

Any number of exception classes can be specified after CATCH. This defines an exception handler for all the specified exception classes and their subordinate classes.

After an exception occurs, the system searches through the listed exception handlers in the specified order. The first exception handler whose CATCH statement contains the corresponding exception class or one of its superclasses is executed. The system then continues program execution directly after ENDTRY. No subsequent exception handlers are considered. For this reason, the order of the different exception handlers within a TRY-ENDTRY structure must be based on the inheritance hierarchy of the specified exception classes.

The syntax check ensures that the handlers for more specific exceptions (subordinate classes) can only be listed before the handlers for more general exceptions (superclasses). For example, a handler for the most general exception class CX_ROOT can only ever be the last statement block before CLEANUP or ENTRY. Otherwise, none of the subsequent handlers would ever be reached.

With the INTO addition, a reference to the exception object can be placed a reference variable. This enables the attributes of the exception object to be accessed in the handler. The reference variable must be suitable for the exception. Its static type must be the exception class itself or one of its superclasses. You are advised to use an exception class below CX_ROOT or CX_ROOT itself rather than the general class OBJECT. Only these classes contain the methods relevant for exceptions.

Regards

Adil

Re: Exception catch

Former Member — Mon, 16 Jun 2008 15:35:58 GMT

hello friends,

in my form routine I wrote the following:

form xyz.

TRY.

**my code

Catch CX_SY_CONVERSION_NO_NUMBER.

CATCH cx_root.

WRITE 'exception occured'.

ENDTRY.

Endform

but i am still getting the shot-dump ??

any suggestion ?

Regards,

Re: Exception catch

Former Member — Mon, 16 Jun 2008 15:47:56 GMT

Hi,

try like this ,

give your catch (CX_SY_CONVERSION_NO_NUMBER).

DATA : 
  a TYPE i ,
  b TYPE i VALUE 10.
TRY.
    a = b / 0.
  CATCH cx_sy_zerodivide.
    WRITE 'shah'.
ENDTRY.

go through this link:

http://help.sap.com/saphelp_webas610/helpdata/en/c3/021950f06111d4b2eb0050dadfb92b/content.htm

if you have any furthur query let me knw.

Regards

Adil