cancel
Showing results for 
Search instead for 
Did you mean: 

Getting /IWBEP/CX_SBCM_FATAL from SEGW

former_member182374
Active Contributor

Hello Experts,

I don't know why but since this morning every time I want to check/generate from SEGW I'm getting dump:

Category               ABAP Programming Error

Runtime Errors         UNCAUGHT_EXCEPTION

Except.                /IWBEP/CX_SBCM_FATAL

ABAP Program           /IWBEP/CL_SBUI_CONTROLLER=====CP

Application Component  OPU-BSE-SB

Date and Time          16.11.2015 10:07:39

An exception has occurred that was not caught.

What happened?

     Exception '/IWBEP/CX_SBCM_FATAL' was raised, but it was not caught anywhere

      along the

     call hierarchy.

     Since exceptions represent error situations, and this error was not

     adequately responded to, ABAP program '/IWBEP/CL_SBUI_CONTROLLER=====CP' had

     to be terminated.

    

Error analysis

    An exception has occurred which is explained in more detail below. The

    exception, which is assigned to class '/IWBEP/CX_SBCM_FATAL' was not caught and

    therefore caused a runtime error. The reason for the exception is:

    Fatal error in Service Builder

    This exception is closely related to a previous exception "CX_SY_NO_HANDLER",

     which

    was raised in program "/IWBEP/CL_SBDSP_DATA_SOURCE===CP", in line 1 of

     (include) program "/IWBEP/CL_SBDSP_DATA_SOURCE===CM00T". The

    reason for the exception occurring was:

    An exception with the type CX_SY_REF_IS_INITIAL occurred, but was neither

    handled locally, nor declared in a RAISING clause

    This exception is closely related to a previous exception

     "CX_SY_REF_IS_INITIAL", which

    was raised in program "/IWBEP/CL_SBDSP_DATA_SOURCE===CP", in line 11 of

     (include) program "/IWBEP/CL_SBDSP_DATA_SOURCE===CM00T". The

    reason for the exception occurring was:

    Dereferencing of the NULL reference

How to correct the error

    If the error occurs in a non-modfied SAP program, you might be able to

    find a solution in the SAP Notes system. If you have access to the SAP

    Notes system, check there first using the following keywords:

    "UNCAUGHT_EXCEPTION" /IWBEP/CX_SBCM_FATAL

    "/IWBEP/CL_SBUI_CONTROLLER=====CP" bzw. /IWBEP/CL_SBUI_CONTROLLER=====CM00C

    "/IWBEP/IF_SBUI_CONTROLLER~ON_COMMAND_REQUESTED"

Chain of Exception Objects

Attrib. Name                   Value

Level    1     Class    /IWBEP/CX_SBCM_FATAL

Program  /IWBEP/CL_SBUI_CONTROLLER=====CP Include  /IWBEP/CL_SBUI_CONTROLLER=====CM00C Row   152

Short Te

Long Tex

T100_MSGID                     /IWBEP/SBCM

T100_MSGNO                     000

IS_RESUMABLE

KERNEL_ERRID

Level    2     Class    CX_SY_NO_HANDLER

Program  /IWBEP/CL_SBDSP_DATA_SOURCE===CP Include  /IWBEP/CL_SBDSP_DATA_SOURCE===CM00T Row   1

Short Te An exception with the type CX_SY_REF_IS_INITIAL occurred, but was neither handled locally

, nor declared in a RAISING clause

Long Tex

An exception of type 'CX_SY_REF_IS_INITIAL' occurred, that was not caught anywhere in

the call hierarchy. It was not handled locally or declared using a RAISING clause.

CLASSNAME                      CX_SY_REF_IS_INITIAL

IS_RESUMABLE

KERNEL_ERRID                   UNCAUGHT_EXCEPTION

Level    3     Class    CX_SY_REF_IS_INITIAL

Program  /IWBEP/CL_SBDSP_DATA_SOURCE===CP Include  /IWBEP/CL_SBDSP_DATA_SOURCE===CM00T Row   11

Short Te Dereferencing of the NULL reference

Long Tex

An attempt was made to execute a dynamic method callon an initial(NULL-) object

reference. The reference must refer to an object.

IS_RESUMABLE

KERNEL_ERRID

Information on where terminated

    The termination occurred in ABAP program "/IWBEP/CL_SBUI_CONTROLLER=====CP",

     in "/IWBEP/IF_SBUI_CONTROLLER~ON_COMMAND_REQUESTED". The main program

    was "/IWBEP/R_SBUI_SERVICE_BUILDER".

    In the source code, the termination point is in line 152 of (Include)

    program "/IWBEP/CL_SBUI_CONTROLLER=====CM00C".

   

Source Code Extract

Line  SourceCde

  122           WHEN gc_cc_sb_cancel.

  123             mr_active_call->exit_command_active = abap_true.

  124             cancel_input_validation( ).

  125           WHEN gc_lc_wz_back.

  126             mr_active_call->exit_command_active = abap_true.

  127             cancel_input_validation( ).

  128           WHEN OTHERS.

  129             fetch_pending_user_input( ).                          " fetch pending input befo

  130         ENDCASE.

  131 *       --- move current selection ---

  132         IF mr_active_call->command_in_process-select EQ abap_true.

  133           mr_active_call->nav_state_current-marked = mr_active_call->command_in_process-requ

  134           mr_active_call->nav_state_current-marked_nodes = mr_active_call->command_in_proces

  135           mr_active_call->navigation_mandatory = abap_true.

  136         ENDIF.

  137 *       --- do process the command ---

  138         mr_active_call->command_in_process-rcode = handle_command( io_sender = mr_active_cal

  139         CASE mr_active_call->command_in_process-rcode.

  140           WHEN gc_rc_cancelled.

  141             MESSAGE ID '/IWBEP/SBUI' TYPE 'S' NUMBER '024' DISPLAY LIKE 'S'.

  142             LOG-POINT ID /iwbep/sbui FIELDS mr_active_call->command_in_process-request-fcode

  143           WHEN gc_rc_error.

  144             MESSAGE ID '/IWBEP/SBUI' TYPE 'S' NUMBER '026' DISPLAY LIKE 'S'.

  145             LOG-POINT ID /iwbep/sbui FIELDS mr_active_call->command_in_process-request-fcode

  146           WHEN gc_rc_rejected.

  147             LOG-POINT ID /iwbep/sbui FIELDS mr_active_call->command_in_process-request-fcode

  148           WHEN gc_rc_undefined.

  149             LOG-POINT ID /iwbep/sbui FIELDS mr_active_call->command_in_process-request-fcode

  150         ENDCASE.

  151       CATCH /iwbep/cx_sbcm_exception cx_sy_no_handler INTO lx_error.

>>>>>         RAISE EXCEPTION TYPE /iwbep/cx_sbcm_fatal EXPORTING previous = lx_error.

  153     ENDTRY.

  154   ENDLOOP.

  155 * --- unlock queue processing ---

  156   CLEAR mr_active_call->command_in_process.

  157

  158 ENDMETHOD.

How can I solve this error?

Regards,

Omri

Accepted Solutions (1)

Accepted Solutions (1)

former_member182374
Active Contributor

Solved it on my own.

Service uses (in design time) two RFC connections (to the same system but different clients): CLD250, CLD270.

CLD270 destination unicode parameters was changed.

Since the unicode settings for both destination were different an exception was thrown each time I tried to change gateway object (ONLY gateway objects and not classes generated from gateway).

It took me a few hours to find it out.

It would be nice if an error message like "Check that your RFC destinations are defined the same" would be written to ST22.

Regards,

Omri

damien_crowe2
Explorer
0 Kudos

I was getting this error too but it turned out to be an authorisation issue. Check su53 too.

Answers (0)