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

Question

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

Answer 1

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