topic Re: Catch CONVT_NO_NUMBER runtime error in OO ABAP Program in Application Development and Automation Discussions

Catch CONVT_NO_NUMBER runtime error in OO ABAP Program

Former Member — Tue, 13 Nov 2007 01:38:31 GMT

Hi all,

In our abap proxy program, sometimes the CONVT_NO_NUMBER will happen and cause the program dump. I noticed that this error cannot be caught by CX_ROOT exception class.

Some told me I can use the CATCH SYSTEM-EXCEPTIONS sentence to catch this runtime error, but it is a old-way syntax and cannot be used with the "try" and "catch".

So, how can I catch this runtime error and avoid the dump of our program?

Thanks,

YiNing

Re: Catch CONVT_NO_NUMBER runtime error in OO ABAP Program

Former Member — Tue, 13 Nov 2007 01:50:16 GMT

Hi,

Check below thread

/thread/69351 [original link is broken]

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

Regards,

Atish

Re: Catch CONVT_NO_NUMBER runtime error in OO ABAP Program

Former Member — Tue, 13 Nov 2007 03:14:23 GMT

Here's a link talking about the same issue.

Not all errors are catchable, is that true?

Re: Catch CONVT_NO_NUMBER runtime error in OO ABAP Program

Former Member — Tue, 13 Nov 2007 03:17:29 GMT

Not clear what are you asking?

Re: Catch CONVT_NO_NUMBER runtime error in OO ABAP Program

Former Member — Tue, 13 Nov 2007 03:51:27 GMT

How to catch the CONVT_NO_NUMBER error in a OO ABAP program.

Re: Catch CONVT_NO_NUMBER runtime error in OO ABAP Program

Former Member — Tue, 13 Nov 2007 03:53:15 GMT

Have you checked the links I provided. Aren't they useful?

Regards,

Atish

Re: Catch CONVT_NO_NUMBER runtime error in OO ABAP Program

Former Member — Tue, 13 Nov 2007 05:20:02 GMT

Hi, Atish. The 1st link you gave me suggests that "CATCH SYSTEM-EXCEPTIONS" can be used to solve this problem. But as I said, it seems that "Catch... End Catch" cannot be used with "try...catch".

The 2nd link suggests us to use the "CX_SY_CONVERSION_NO_NUMBER" Exception Class to catch the runtime error, I did have try it and has no effect.

Re: Catch CONVT_NO_NUMBER runtime error in OO ABAP Program

Former Member — Tue, 13 Nov 2007 05:23:01 GMT

What is the problem with the class CX_SY_CONVERSION_NO_NUMBER. It should work,

Regards,

Atish

Re: Catch CONVT_NO_NUMBER runtime error in OO ABAP Program

Former Member — Tue, 13 Nov 2007 06:17:30 GMT

No, it doesn't work.

Try the follwing code:

TRY.
    IF 'A' > 5.
    ENDIF.  
    CATCH CX_SY_CONVERSION_NO_NUMBER.
ENDTRY.

The program will still dump.

Re: Catch CONVT_NO_NUMBER runtime error in OO ABAP Program

Former Member — Tue, 13 Nov 2007 06:41:28 GMT

Hi,

You are not checking for conversion.

You are checking ofr logical expression.

Try below code, it works

DATA error_ref TYPE REF TO cx_sy_conversion_no_number.

DATA err_text TYPE string.

DATA a TYPE i.

TRY.

MOVE 'A' TO a.

CATCH cx_sy_conversion_no_number INTO error_ref.

err_text = error_ref->get_text( ).

WRITE err_text.

ENDTRY.

Regards,

Atish

Re: Catch CONVT_NO_NUMBER runtime error in OO ABAP Program

mujeebs_ww — Mon, 20 Jan 2020 05:54:39 GMT

use MOVE statement within TRY ... CATCH block. It will catch the run-time errors.

TRY.
MOVE 'abcd' TO lv_num.

CATCH cx_root INTO DATA(lv_cerr).

DATA(lv_mesg) = lv_cerr->get_text( ).
WRITE / lv_mesg.
CLEAR lv_num.

ENDTRY.

Re: Catch CONVT_NO_NUMBER runtime error in OO ABAP Program

former_member825071 — Thu, 12 Jan 2023 14:42:24 GMT

link not valid. SAP links and SAP forum links make no sense in case of sap, because SAP changes them all the time. Copy of original text is only solution.

Re: Catch CONVT_NO_NUMBER runtime error in OO ABAP Program

FredericGirod — Thu, 12 Jan 2023 15:20:09 GMT

17 years after, even in other forum, not sure the link on documentation survive this timelaps

Re: Catch CONVT_NO_NUMBER runtime error in OO ABAP Program

vonglan — Tue, 12 Nov 2024 08:41:58 GMT

You can also use

TRY.
  numeric_variable = EXACT #( character_variable ).
  CATCH cx_sy_conversion_no_number.
ENDTRY.