Skip to Content
author's profile photo Former Member
Former Member

Error raised using 'CRM_MESSAGE_COLLECT' not displayed in Web UI

Hello,

I have implemented the badi CRM_ORDERADM_H_BADI and based on certain conditions i raise an exception and display the error message using function module 'CRM_MESSAGE_COLLECT'. The application log is populated with the error message and I am able to see the error message in SAP GUI . However when the same transaction is triggered via WebUI , even thought the exception is raised , the error message is not displayed.

I know i can use the method ADD_MESSAGE of the class CL_CRM_GENIL_GLOBAL_MESS_CONT if i want the error message to be displayed in Web UI .

However I want the message to be displayed either if the transaction is run from the SAP GUI or web UI .

Have anyone come across the similar situation , is there something I am missing.

Thanks & Regards ,

Sriram.

Add a comment
10|10000 characters needed characters exceeded

Related questions

1 Answer

  • author's profile photo Former Member
    Former Member
    Posted on Sep 20, 2008 at 11:56 AM

    Hi Sriram,

    I think there is no problem with the Function module for populating error messages which is CRM_MESSAGE_COLLECT. But it is the BADI which has to be used different.

    If you want the error message to get triggered while using WEB UI, then you need to use CRM_ISA_BASKET_HEAD.

    But this BADI will not work for SAP GUI.

    Hope this helps.

    Thanks.

    Best Regards,

    Arun Sankar.

    Add a comment
    10|10000 characters needed characters exceeded

    • Former Member Former Member

      Hello Arun ,

      I got the solution . The error message was raised properly . The problem is message filter at every view or viewset of a component is actually switched off by default.With standard components the filter gets activated at runtime if the component controller contains a BOL entity.

      In our case , since it was a custom component with no BOL entity the filter was switched off and hence the messages from the application level were not read.

      Therefore we redefined the filter method IF_BSP_WD_STATE_CONTEXT~GET_MESSAGE_FILTER at the view/viewset level and turned on the filter by default.hence even if the component does not return an entity the message filter gets activated.

      Thanks for your inputs.

      Thanks & Regards,

      Sriram

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.