Weird Dump " E CRMD_ORDER 015 can't be processed in HTTP Plug in mode "

Question

Dear Experts,
We are facing this strange issue with WEB UI.
On Production system, suddenly , a dump occurs as follows ->>
Business Server Page(BSP) Error
What Happened ?
Calling BSP page was terminated due to an error
SAP NOTE:
The following error text was processed in the system:
Message E CRMD_ORDER 015 can't be processed in HTTP Plug in mode
Exception Class: CX_SY_MESSAGE_IN_PLUGIN_MODE
Program           : CL_BSP_WD_VIEW_MANAGER=================CP
Include             : CL_BSP_WD_VIEW_MANAGER==========CM002
ABAP Class     : CL_BSP_WD_VIEW_MANAGER
Method            : DO_REQUEST
Line                : 43
Whenever this error was reported to me by client and i tried to log in to the production system to regenerate the error following the way it was reqorted, it never reappeared for that event.
Thus the cause of this dump is undefined and what makes it disappear is also undefined.
It keeps on occuring any time ,in any event of User Interaction with WEB UI.
Is there anyone who experienced the same behaviour ? Can you please share you thoughts/opinions on it as why this dump could be appearing ?
As i was unable to regenerate this error, i am still looking for the solution.
Please help.
Thanks & Regards,
Suchita
P.S
Error type is exception. Can not be found any detail in ST22 too.
This DUMP is occuring only in Sales Order processing Line editing/Saving/Changing order status/Creating Followup etc on some event like click on the edit button, or changing status by clickin on the status drop down.
This DUMP is not persisten. if its there today, It wont be there 2-3 days later or so.
Edited by: suchita on Apr 1, 2009 12:37 AM

Answer 1

Hi Suchita,
The HTTP Plug in mode errors generally occur when the error messages are raised on the Web UI without proper use of Message handler classes. I experienced similar situations when some coding is done at Web UI component and the message or exception is raised by any Function Module etc.,
Imagine a situation where you are coding at UI level and using a Function Module which raises exceptions with normal ABAP syntax:
MESSAGE ID sy-msgid TYPE sy-msgty NUMBER sy-msgno
        WITH sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
This type of messages do not get transferred to message log and result in dumps.
We use classes like cl_bsp_wd_message_service to raise messages at UI level.
Alternatively ,these type of dumps get triggered when any BADI Implementations raise the messages with this syntax.
MESSAGE ID sy-msgid TYPE sy-msgty NUMBER sy-msgno
      WITH sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
( Any error messages needed should be raised by passing to message log using FMs like CRM_MESSAGE_COLLECT or some classes).
Regards,
Masood Imrani S.