cancel
Showing results for 
Search instead for 
Did you mean: 

Runtime Errors RAISE_EXCEPTION CAST_ERROR

Former Member
0 Kudos

Hello!

I was looking for a similar problem on the forum but did not find.

Please help me solve the problem:

Short text

Exception condition "CAST_ERROR" raised.

Error analysis
    A RAISE statement in the program "CL_EXITHANDLER================CP" raised the exception
    condition "CAST_ERROR".
    Since the exception was not intercepted by a superior program, processing was terminated.

    Short description of exception condition:


    For detailed documentation of the exception condition, use Transaction SE37 (Function Library). You can take the called function module from the display of active calls.

User and Transaction

    Language key........ "R"
    Transaction......... "START_REPORT "
    Transactions ID..... "51354336852B0990E1000000AC10150A"

    Program............. "CL_EXITHANDLER================CP"
    Screen.............. "SAPMSSY0 1000"
    Screen line......... 6

Information on where terminated
    Termination occurred in the ABAP program "CL_EXITHANDLER================CP" - in "GET_INSTANCE".
    The main program was "RGRGEN00 ".

    In the source code you have the termination point in line 101 of the (Include) program "CL_EXITHANDLER================CM001".

    75       ENDIF.
    76
    77       SELECT SINGLE is_impl FROM badiisimpled INTO is_impl
    78         WHERE badi_name = mig_badi_name.
    79       IF sy-subrc NE 0.
    80 *       not yet filled
    81         is_impl = cl_enh_badi_tool_utilities=>update_badiisimpled( mig_badi_name ).
    82       ENDIF.
    83
    84       IF is_impl = 'X'.
    85 *       ok at least one implementation found, then do your job
    86         act_imp_existing = 'X'.
    87         CREATE OBJECT exit TYPE (abs_type_classname).
    88         CATCH SYSTEM-EXCEPTIONS move_cast_error = 1.
    89           instance ?= exit.
    90         ENDCATCH.
    91         IF sy-subrc = 1.
    92           RAISE cast_error.
    93         ENDIF.
    94       ENDIF.
    95     ELSE.
    96       CREATE OBJECT exit TYPE (abs_type_classname).
    97       CATCH SYSTEM-EXCEPTIONS move_cast_error = 1.
    98         instance ?= exit.
    99       ENDCATCH.
   100       IF sy-subrc = 1.
>>>>>         RAISE cast_error.
   102       ENDIF.
   103       IF act_imp_existing IS REQUESTED.
   104         CLEAR act_imp_existing.
   105 *       simulate act_imp_existing behaviour

Thank you in advance!

Accepted Solutions (0)

Answers (1)

Answers (1)

Former Member
0 Kudos

Hello Fomin,

Do you have any information regarding this issue? I'm having similar ussues.

Grts, Martin

AtulKumarJain
Active Contributor
0 Kudos

Hi Fomin,

You can check SAP Note No. 1702676 for this.

Best Regards,

Atul

Former Member
0 Kudos

Funny thing is that according to this note correction should be delivered in package SAPKH60412, whereas our troubles started with importing it

Former Member
0 Kudos

Yes, I also noticed that this problem started when I installed the package SAPKH60412

AtulKumarJain
Active Contributor
0 Kudos

Than it will be good if you raise the message to SAP .

Regards

Atul

Former Member
0 Kudos

And right you are

I have raised the message and although this issue should be solved by importing the supportpack, this note must be imported manually. Following the instructions of this note (as instructed by SAP Support) solved my issue.

Thanks Atul.