Popup in FPM Message Manager

Hi experts,
I`m using FPM and want to display certain warnings as popup. When I use the FPM Message Manager, method  REPORT_MESSAGE, REPORT_T100_MESSAGE or REPORT_BAPIRET2_MESSAGE and set import parameter IV_LIFETIME = 'POPUP_AUT' I get a popup, however this popup looks really ugly:
The text of the message is displayed just to about 28 characters and a horizontal scrollbar appears. Is there any way to influence the attributes (size and so on) of the popup?
Thanks,
Markus

hi,
Resizing the popup window is not support for the current version.
There are some class & methods available for  that but those are not played well with script.
So my advice is donu2019t waste your time for that.
Already i spend my time in this for R&D, after that i come to know this.
regards,
vijay

Similar Messages

  • FPM Message Manager message's HyperLink does not work in Table

    Hi FPM experts,
    I use FPM in my application and I want to use FPM Message Manager with hyperlink pointing to cells with errors in a table with report_bapiret2_message. The hyperlink does work when pointing on stand alone input field, but it does not work when pointing on a input field in a table.
    Here is a piece of my code. What's wrong?
      data is_message type bapiret2.
      is_message-type = 'E'.
      is_message-id = 'TEST'.
      is_message-number = '1'.
    wd_comp_controller->mr_fpm_message_manager->
       report_bapiret2_message( is_bapiret2 = is_message
                                             io_component = wd_comp_controller
                                             io_element = lo_el_table_elements " point on the element in my context
                                             iv_attribute_name = 'VALUE' ).  " Name of my attribute in context
    Thanks
    Davy
    Edited by: Davy Veilleux on Jan 4, 2009 4:19 PM

    Any answers to this question?
    I am facing the same issue. Using FPM Message Manager  with the io_element and iv_attribute parameters pointing to an element in an context node having cardinality = "0...n" does not show the hyper link.
    Any Help is Appreciated.

  • Message (of message manager) gets lost by opening a popup window

    Hi all,
    On behalf of a better error/exception handling, I would like to show the stacktrace in a popup window, that means, if the application reports an error message (through the message manager in the view controller), the user (administrator, developer) can optionally click a link (LinkToAction => opening a modal window) to see the stacktrace in a separat popup window.
    Unfortunately if the popup window now gets displayed, the error message on the main view (background of the popup window) will be cleared, so this - for the common user more readable - information is not anymore displayed, also when the popup will be cleared.
    Of course, I could backup the error message in a context value and redisplay it after closing the popup window, but I suppose that's not a very cool solution...
    Other any good ideas?
    Thanks,
    Stefan

    Hi Stefan
    Usually showing a stack-trace to the end-user of your application is not so helpful as might appear. My experience shows that the information is too technical for the end-user and does not help him/her to resolve the issue/problem. It's better to display error messages pointing him to some solution or directions that he might do in order to fix the error.
    If you still want to show a stack-trace I'd advise the following. You have to prepare the UI control with the stack-trace in the same server response (round trip) which shows the message manager's messages. The messages will not disappear until a client sends a new request to the server. When you open the popup such request definitely takes place.
    Maybe try to display the stack-trace in the bottom of the screen so user have to scroll down a little bit to show the trace.
    Or maybe Tray control will help in the case. Try to put the trace in a text view and put the view in a tray. Then user has to expand the tray to see the trace. But do not assign any event handlers to the tray to avoid additional request to the server while it's expanding.
    BR, Sergei

  • Web Dynpro message manager and popups

    Hi,
    I am using IF_WD_MESSAGE_MANAGER to issue error messages to screen with methods REPORT_ERROR_MESSAGE and REPORT_EXCEPTION. This works fine and the messages appear on the top of the screen. Both methods have a parameter SHOW_AS_POPUP, but setting this to TRUE does not result in a popup being shown. Does anyone have any idea whether this is supposed to work on 7.01 ?
    thanks!

    HI Frank,
    That should work.
    please go to the thread link posted by me in my first post.
    there go to the last reply.
    there what is required is opening the window2 first manually then calling the message manager with view = view2.
    means your view will be opened by you only but the message will come only on the second view.
    i know it is not a gud approach.
    As we can easily get it done without using the message manger at all and just creating the window as popup.
    So yeah you are right they need to modfiy this thing.
    thanks
    sarbjeet singh

  • How to create a navigateable messages for SALV in FPM message area

    We have some problems raising messages for errors in a ALV table. Messages reported by the ALV table itself (like a character entered in a number field) are displayed in the FPM message area and the message is mapped to the field causing the error (navigation link). When we try to raise an own message out of the application controller of our building block which carries the ALV, we didnu2019t manage to have the mapping between the error message and the ALV-field.
    We already tried several versions of calling the message method (using the elements of the context of the calling application as well as the context of the mapped ALV compontent):
    CALL METHOD wd_this->gr_msg_manager->report_t100_message
          EXPORTING
            iv_msgid              = '/ISDFPS/MSG_GAF_PE'
            iv_msgno              = '047'
            iv_parameter_1        = lv_par1
            iv_parameter_2        = lv_par2
            io_component          = lo_INTERFACECONTROLLER
            io_controller         = lo_api_interfacecontroller
            io_element            = lo_element
            IV_ATTRIBUTE_NAME     = lv_attribute
            iv_severity           = if_fpm_message_manager=>gc_severity_error
            iv_lifetime           = if_fpm_message_manager=>gc_life_visibility_automatic
            is_navigation_allowed = abap_true
            it_attributes         = lt_attributes.
    Does anybody know a solution or maybe an example where a error message is linked to an field in the SALV and reported in the FPM message area using the above mentioned method call?
    Thanks and best regards
      Gerald
    Edited by: Gerald Reinhard  on Mar 31, 2009 10:56 AM

    Just to clarify, what I am having trouble with is finding where exactly to plug in the name of the plant to be filtered? If using a message type such as MATMAS in a distribution model, it is very straight forward to navigate down from the 'Data filter active', and assign a value to whatever field you wish to filter via the 'List of Values'.  But in this example, message type QPMK required use of the BAPI MasterInspectionChar, and therefore the different method in creating the filter. 
    I cannot find similar functionality when navigating the BAPI related row, for MasterInspectionChar. The 'Change Filter' dialog popup displays a row for 'Container' and then 3 more rows containing 'BAPI structure...'.   Clicking the 'Attribute' checkbox on any of these rows sets 'Data filter active' as a node under the BAPI.  Double clicking the 'Data filter active' brings me back into the same dialog, and selecting any row with an attempt at this point to create a filter results in the 'Select node: content-dependent parameter filtering' warning.  Is this warning occuring because of missing configuration?
    Thanks - Mike

  • Exception in message manager (CX_WD_ABORT_MESSAGE_MANAGER)

    I have a Web Dynpro application with popup views (using the window manager) to create/change data.  All works well in one view , when the method to create/change the data returns an error I relay it to the message manager and it is displayed on the screen.  In one of the views I have the same code to relay messages but method raise_t100_error raises exception CX_WD_ABORT_MESSAGE_MANAGER.  Both screen have a message area in the layout, I cannot find any significant differences between them.
    Here is the relevant code:
    Error Handling
    get message manager
      l_current_controller ?= wd_this->wd_get_api( ).
      CALL METHOD l_current_controller->get_message_manager
        RECEIVING
          message_manager = l_message_manager.
      CALL METHOD l_message_manager->clear_messages.
    report message
      LOOP AT li_return INTO lwa_return
        WHERE type EQ 'E'.
    report message
        l_msgno = lwa_return-number.
        CALL METHOD l_message_manager->raise_t100_error
          EXPORTING
            msgid = lwa_return-id
            msgno = l_msgno
            msgty = lwa_return-type
            p1    = lwa_return-message_v1
            p2    = lwa_return-message_v2
            p3    = lwa_return-message_v3
            p4    = lwa_return-message_v4.
      ENDLOOP.

    Hi Ingo,
    Please use <b>report</b>_t100_error instead of raise_t100_error.
    Regina

  • WD Application always display 'No Message' in FPM Message Region

    I don't know why WD Application always automatically display 'No Message' in FPM Message Region.  I cannot find
    any places to prompt this message in my application. Who can tell me to disable this message?
    Thanks, boer

    Hi,
    I assume that, the messages are retunrd from a BAPI .
    DATA: es_message type bapret2 or any strcutre of your type or message manager messages table type.
    (Refer IF_WD_MESSAGE_MANAGER).
    loop at lt_msg into ls_msg.
        MESSAGE ID 'DEMO' TYPE 'E' NUMBER '139'
        WITH liv_id INTO es_messages-message.
        es_messages-id         = 'DEMO'. "Mesage class
        es_messages-type       = 'E'.
        es_messages-number     = '139'.
        es_messages-message_v1 = liv_id.
    or
    if ls_msg-type eq 'E'.
    lv_str = "Success ful'.
    endif.
    es_message-id = ls_msg-id.
    es_message-message = lv_str.
    endif.
    Maintain the messages in the Se91.
    By defalut as per the message type the framwork handles
    the Icon.
    But if you want some specific icon  to be displayed then you
    need have your own table that shows these meesages with custom icons.
    Regards,
    Lekha.
    Edited by: Lekha on Sep 3, 2009 3:17 PM

  • Message Manager

    Hi,
    I have few q' s which i felt will get answered over here.
    a) Is it possible to count the number of messages that gets collected by the message manager at the run time.
    b) Is it possible to stop the further collection of messages using message manager post a certain limit or count.
    c) Can we have a scrollbar to the message area.
    Any (pointers/ answers) will be highly appreciated.
    Thanks in Advance,
    Vipin.

    Hi Govindu,
    Thanks for your quick reply.
    I opened the thread due to the reason that i was getting the below exception
    com.sap.tc.webdynpro.progmodel.controller.MessageManagerOverflowException: The MessageManager contains already 1,000 messages. Assuming loop. The first messages: ........
    Now the requirement from the user is to stop further collection of error messages the moment 100 messages are collected.
    Any (pointers/ answers) on how i can restrict this exception and limit the collection to 100 will be highly appreciated.
    Thanks in Advance,
    Vipin.

  • My JMS 2 wish list - Part 2, poison messages management

    I attended the JavaOne 2010 session on future JMS evolutions. During the session I described some current limitations or issues I'd like to be solved in a portable way. I've been adviced to share the issues to get feedback from the community. I will post each issue in a dedicated thread.
    Issue 2 - Poison messages management
    Poison messages are messages that are redelivered again and again when an untreated error occurs, possibly resulting in CPU eating long lasting loops.
    This is a well known messaging related issue, but it is not fully adressed by the JMS specification. The Message:getJMSRedelivered method can tell if a message is being redelivered. But this is not good enough and application servers implement their own solutions. Such solutions are based, for example, on redelivery limit and error destinations.
    With WebSphere 6, it is possible to specify, at the SI Bus destination level, an exception destination and a maximum failed deliveries threshold. When messages consumption fails more than the threshold allows, messages are moved to the exception destination.
    JBoss 4 has equivalent features, with a dead letter queue where messages that reached the redelivery limit are moved. It is also possible to use the specific 'JMS_JBOSS_REDELIVERY_DELAY' message property to specify a redelivery delay from the message producer side. JBoss 5 has the same features with the 'dead-letter-address', 'max-delivery-attempts' and 'redelivery-delay' destination configuration parameters.
    WebLogic has equivalent features, see 'Error Destination', 'Redelivery Limit' and 'Redelivery Delay' parameters.
    A portable mechanism should be defined.
    Edited by: 807264 on Nov 3, 2010 6:01 AM

    gimbal2 wrote:
    A portable solution would be useful.You could already do it now by leveraging the Timer functionality that has been part of the EJB spec since JEE 1.4. In stead of sending the message directly, let the timer do it after the delay you specify. That would make it portable with current tech.
    I can't be sure what other implications that might have though, such as in the area of performance and resource usage - I can imagine you wouldn't want to use a timer when you need to send large volumes of messages.In the original requirement, the message is put in the queue immediately by a call to queuesender.send(message) and there's a delivery in delay to a consumer.
    Whereas in this solution, the delay is in the message delivery to the queue itself.
    IMHO there's a subtle but important difference here.What would for example happen if posting the message to the queue is in the scope of a distributed JTA transaction? You can definitely include the timer call to be in the scope of the transaction, but now you will have to account for the fact and there may be an error when the message is delivered which has to be handled explicitly. In the original scenario the tx would automatically rollback.
    cheers,
    ram.

  • WDA - Contrast Using Message Manager & Application Logs

    Hi there, I'm trying to figure out when it is appropriate to use each.  Thus far, it seems that the conclusion that I am coming upon is that the message manager is used for issuing messages at an application user, whereas the application logs should be used to address issues meant for an administrator of the application - basically someone who may be more technical.  How is this assumption?  Can someone provide me with more inside.  I'd love to understand some real life usages.   I've read documentation after documentation, but in short, it would be great to leverage off of some who have actually used this in practice.
    Thanks in advance.

    Hi Michael
    > Thus far, it seems that the
    > conclusion that I am coming upon is that the message
    > manager is used for issuing messages at an
    > application user, whereas the application logs should
    > be used to address issues meant for an administrator
    > of the application - basically someone who may be
    > more technical.
    As I can see from my point of view the main area of using IWDMessageManager is to indicate to user what is wrong with data he or she is trying to change over UI. For example, to show message "The field XXX must not be empty" or to make another kind of validation of input data on UI level.
    The main purpose of logging is to trace possible Java exceptions, to trace debugging information (with severity DEBUG), to log some critical errors for technical staff or administrators. The information from the logs can be unhelpful for end-user.
    BR
    Sergei

  • Program exits when message manager capture an error

    Hi Buddies,
    I am new to web dynpro for ABAP and now I am doing some exercises.
    In method check_input, I coded to capture an error using message manager. However, I find method FLIGHTTAB_FILL continue to run. I am wondering if there are some indicators (I find sy-subrc is still initial...any other indicators??) I could use to stop the program when an error is captured? Please advice. Thanks.
    method FLIGHTTAB_FILL .
      wd_this->check_input(
    endmethod.
    Kind Regards,
    Clark

    Hi,
    If you use is_empty method, you can identify.
    ABAP_TRUE if Message List Is Empty. So in your case, if messages are populated, space will be the value of the Boolean.
    ** get message manager
    DATA lo_api_controller     TYPE REF TO if_wd_controller.
    DATA lo_message_manager    TYPE REF TO if_wd_message_manager.
    data lv_bool type abap_bool.
    data lt_messages type if_wd_message_manager=>ty_t_messages.
    lo_api_controller ?= wd_this->wd_get_api( ).
    CALL METHOD lo_api_controller->get_message_manager
      RECEIVING
        message_manager = lo_message_manager
        .DATA lv_message            TYPE string.
    DATA lv_message_type       TYPE i.
    lv_message_type = if_wd_message_manager=>co_type_standard.
    * report message
    CALL METHOD lo_message_manager->report_success
      EXPORTING
        message_text              =  'Success'.
    * report message
    "ABAP_TRUE if Message List Is Empty

  • Display Massages from context within message manager

    Hello,
    i have got a bapireturn in my context with a node named "return" an some attributes like "type" and "message", .
    If I run the Bapi this node get some infos like:
    Type: E message: Error1
    Type: W message: warning1
    Type: W message: warning2
    how could I get this messages and warnings into the Message manager?
    If i implement the Message Manager with the code-wizard, i only get one Message with my own text, but I want every massage with the original text of the warning...
    Is this possible?
    Could you can give me some advise and code?
    That would be really nice!!
    Thank you for your help!
    Edited by: john Thompson on May 20, 2008 12:53 PM

    Hi,
    Just loop at your bapiret table and using the message manager just report the error. All the errors are displayed in the message manager.
      data: l_current_controller type ref to if_wd_controller,
                   l_message_manager    type ref to if_wd_message_manager.
      l_current_controller ?= wd_this->wd_get_api( ).
      call method l_current_controller->get_message_manager
        receiving
          message_manager = l_message_manager.
    loop at bapiret.
    call method l_message_manager->report_t100_message
                    exporting
                      msgid = bapiret-msgid
                      msgno = bapiret-msgno
                      msgty = bapiret-msgtyp  .
    endloop.
    Regards,
    Shruthi

  • Issues with Messaging Manager in ATG 10

    Hi,
    We are facing an issue with messaging manager. In weblogic we have configured datasource as 'coreDataSource', somehow MessagingManager is looking for coreDataSource_shop and throwing error that Datasource is not available?
    How to resolve this? I am using ATG 10.3 and Weblogic 10.3.5.
    **** Error     Tue Nov 29 04:28:20 IST 2011     1322521100638     /atg/dynamo/messaging/MessagingManager     limbo : error querying for messages     CONTAINER:atg.repository.RepositoryException; SOURCE:java.sql.SQLException: Unexpected exception while enlisting XAConnection java.sql.SQLException: XA error: XAResource.XAER_RMFAIL start() failed on resource 'coreDataSource_shop': XAER_RMFAIL : Resource manager is unavailable
    **** Error     Tue Nov 29 04:28:20 IST 2011     1322521100638     /atg/dynamo/messaging/MessagingManager     oracle.jdbc.xa.OracleXAException
    **** Error     Tue Nov 29 04:28:20 IST 2011     1322521100638     /atg/dynamo/messaging/MessagingManager          at oracle.jdbc.xa.OracleXAResource.checkError(OracleXAResource.java:1110)
    **** Error     Tue Nov 29 04:28:20 IST 2011     1322521100638     /atg/dynamo/messaging/MessagingManager          at oracle.jdbc.xa.client.OracleXAResource.start(OracleXAResource.java:240)
    **** Error     Tue Nov 29 04:28:20 IST 2011     1322521100638     /atg/dynamo/messaging/MessagingManager          at weblogic.jdbc.wrapper.VendorXAResource.start(VendorXAResource.java:50)
    **** Error     Tue Nov 29 04:28:20 IST 2011     1322521100638     /atg/dynamo/messaging/MessagingManager          at weblogic.jdbc.jta.DataSource.start(DataSource.java:729)
    **** Error     Tue Nov 29 04:28:20 IST 2011     1322521100638     /atg/dynamo/messaging/MessagingManager          at weblogic.transaction.internal.XAServerResourceInfo.start(XAServerResourceInfo.java:1231)
    **** Error     Tue Nov 29 04:28:20 IST 2011     1322521100638     /atg/dynamo/messaging/MessagingManager          at weblogic.transaction.internal.XAServerResourceInfo.xaStart(XAServerResourceInfo.java:1164)
    **** Error     Tue Nov 29 04:28:20 IST 2011     1322521100638     /atg/dynamo/messaging/MessagingManager          at weblogic.transaction.internal.XAServerResourceInfo.enlist(XAServerResourceInfo.java:285)
    **** Error     Tue Nov 29 04:28:20 IST 2011     1322521100638     /atg/dynamo/messaging/MessagingManager          at weblogic.transaction.internal.ServerTransactionImpl.enlistResource(ServerTransactionImpl.java:522)
    **** Error     Tue Nov 29 04:28:20 IST 2011     1322521100638     /atg/dynamo/messaging/MessagingManager          at weblogic.transaction.internal.ServerTransactionImpl.enlistResource(ServerTransactionImpl.java:449)
    **** Error     Tue Nov 29 04:28:20 IST 2011     1322521100638     /atg/dynamo/messaging/MessagingManager          at weblogic.jdbc.jta.DataSource.enlist(DataSource.java:1599)
    **** Error     Tue Nov 29 04:28:20 IST 2011     1322521100638     /atg/dynamo/messaging/MessagingManager          at weblogic.jdbc.jta.DataSource.refreshXAConnAndEnlist(DataSource.java:1503)
    Thanks
    Gopi

    still the issue is exist.
    At one point of time, Database is not able to provide connection for coreDataSource. After that shop is trying to get connection from JNDI coreDataSource_shop, which is not available in weblogic.

  • Popup BAPI return messages

    Hello experts,
    I would like a way to quickly handle the BAPI return table (TYPE TABLE OF bapiret2).  I would like to pass the table into a function module or helper method to popup all the messages at once.  This is the same way MIGO (and many other programs) do a popup of messages with little red, yellow, and green icons to the left.  Currently I am using a series of calls to function module BAL_LOG_... and I feel there has to be a better way.
    I tried searching for the answer to this question, but if the answer exists, it is buried within the noise of a million people saying use 'POPUP_TO_CONFIRM' and other function modules.  To clarify: I do not want buttons to confirm.  I want a popup of a list of messages with red, yellow, and green icons on the left.
    Whoever answers my question correctly will henceforth be referred to by me as "the Magnificent."

    My 2 cents ...
    IF_RECA_MESSAGE_LIST is the most convenient message handler i have used so far So i would use it in this way -
    Get the instance using the factory class CF_RECA_MESSAGE_LIST=>CREATE( ).
    Add the BAPI messages using the method ADD_FROM_BAPI( ).
    Get the handle via GET_HANDLE( ) & display using function BAL_DSP_LOG_DISPLAY.
    DATA(o_msg_list) = cf_reca_message_list=>create( ).
    o_msg_list->add_from_bapi(
      EXPORTING
        it_bapiret = VALUE #( id = 'BC_IBF'
                            ( type = 'I'  number = '008' )
                              type = 'E' ( number = '050' message_v1 = 'AA')
                                         ( number = '051' message_v1 = 'BB')
                                         ( number = '055' message_v1 = 'CC')
    DATA st_log_disp_prof TYPE bal_s_prof.
    CALL FUNCTION 'BAL_DSP_PROFILE_POPUP_GET'
      IMPORTING
        e_s_display_profile = st_log_disp_prof.
    st_log_disp_prof-use_grid   = abap_true.
    st_log_disp_prof-disvariant
      = VALUE #( handle = o_msg_list->get_handle( )
                 report = sy-repid
    CALL FUNCTION 'BAL_DSP_LOG_DISPLAY'
      EXPORTING
        i_s_display_profile  = st_log_disp_prof
      EXCEPTIONS
        profile_inconsistent = 1
        internal_error       = 2
        no_data_available    = 3
        no_authority         = 4
        OTHERS               = 5.
    IF sy-subrc <> 0.
    * Implement suitable error handling here
    ENDIF.
    BR,
    Suhas

  • Message management in WM

    Hi guys.
    Does anyone have material  about  message management in WMS ?
    Thanks.

    Hi Marcos Cesar,
    You can define the Reduce message types and Activate message types in transaction BD53.
    SAP recommends that you use message types:
    "MATMAS" (material master tables) and 
    "DEBMAS" (customer master) as a template.
    Be aware that only those fields that are absolutely necessary are transferred from the master data tables in  the ERP system to the decentralized WMS.
    Thanks & Regards,
    Sudhakar

Maybe you are looking for