topic Re: Runtime Errors"MESSAGE_TYPE_X" in Application Development and Automation Discussions

Runtime Errors"MESSAGE_TYPE_X"

Former Member — Tue, 21 Dec 2010 08:17:02 GMT

Hi,

I am getting a short dump below provided is the source code extract , any one knows the cause of this error .

Source Code Extract

________________

Line SourceCde

1 METHOD if_swf_run_wim_utl_internal~get_system_user .

2 DATA: l_excp TYPE REF TO cx_swf_run_wim.

4 TRY.

5 IF me->m_int_state-system_user IS INITIAL.

6 me->m_int_state-system_user = cl_swf_run_workflow_properties=>get_rfc_destination_us

7 ENDIF.

8 re_user = me->m_int_state-system_user.

9 CATCH cx_swf_run_wim INTO l_excp.

>>>>> MESSAGE ID l_excp->t100_msg-msgid

11 TYPE 'X'

12 NUMBER l_excp->t100_msg-msgno

13 WITH l_excp->t100_msg-msgv1 l_excp->t100_msg-msgv2

14 l_excp->t100_msg-msgv3 l_excp->t100_msg-msgv4.

15 ENDTRY.

17 ENDMETHOD. "

Edited by: Thomas Zloch on Dec 21, 2010 9:26 AM

Re: Runtime Errors"MESSAGE_TYPE_X"

Former Member — Tue, 21 Dec 2010 08:19:38 GMT

Hi,

Here its trying to call a RFC Destination and that getting the error.

The error is getting into the exceptions and that exceptions are captured in the catch statement.

Hope this might help you,

With Regards,

Sumodh.P

Re: Runtime Errors"MESSAGE_TYPE_X"

Clemenss — Tue, 21 Dec 2010 20:42:59 GMT

Hi prem,

SAP programmer use the message type X frequently to abort the current program because a method or form has been called out of context with fatal wrong data.

In such cases, the code where the message is raised is not the reason for the error.

In debugger you can look at the call hierarchy and find out what's fatally wrong (or missing).

Regards,

Clemens

Re: Runtime Errors"MESSAGE_TYPE_X"

Former Member — Wed, 22 Dec 2010 05:28:05 GMT

Look for error in your TRY block while debugging. Something there might be throwing the error which is caught in CATCH statement.