FPM - SEARCH UIBB - Input Help Dump when Search Criteria not in First Group Criteria

[Former Member]

HI Experts,

  I have a problem with a SERACH UIBB when I perform an Input Field (MATCH CODE), I have a DUMP.

I have a SEARCH UIBB with 2 GROUP CRITERIA.

Then I have a Search Criteria referred to a Data Element with a Match Code link. 

When the Search Criteria is in the First Group everything works fine (the Input Filed show the PopUp with the Match Code):

But if I move the Search Criteria to the Second Group, when I perform the Input Filed : I have a DUMP.

This is the DUMP error:

The ASSERT condition was violated. (termination: RABAX_STATE)

The program goes in errror in this point:

IF_WDR_SHLP_CTX_MNGR_PROVIDER~GET_SHLP_CONTEXT_MANAGER

  DATA lv_attribute TYPE string.
  FIELD-SYMBOLS: <ls_attributes> TYPE ts_attributes,
                 <ls_attr_range_conv> TYPE ts_range_attribute.
  context_element->get_attribute( EXPORTING name = 'ATTR'
                                  IMPORTING value = lv_attribute ).
  READ TABLE mt_attributes ASSIGNING <ls_attributes> WITH KEY attr-attribute = lv_attribute.

--->  ASSERT sy-subrc = 0.

It seems that in the table MT_ATTRIBUTES the system load only the attribute of the FIRST GROUP CRITERIA:

Here my SERACH UIBB "GET_DEFINITION" Method (nothing in particular😞

  METHOD if_fpm_guibb_search~get_definition.
    DATA ls_field_descr TYPE fpmgb_s_searchfield_descr.

    eo_field_catalog_attr   ?= cl_abap_structdescr=>describe_by_name( 'ZNP_SEARCH_DOC_S' ).
    eo_field_catalog_result ?= cl_abap_tabledescr=>describe_by_name( 'ZNP_SEARCH_DOC_T').
    mo_field_catalog        = eo_field_catalog_attr.

    get_fieldescr( CHANGING  ct_field_description_attr = et_field_description_attr ).

So...How can I avoid this DUMP?

Is there a particolar custmozing to do in UIBB Configuration schema, or is it a Program error?

My SP is:

SAP_BASIS 731 --> SAPKB73104

SAP_ABA 731    --> SAPKA73104

Thank you in advance,

LUCA MAIONCHI

[mick_pichaloff2]

Hi Luca,

I am experiencing the same issue.

How id you reolve this issue?

Thanks,

Mick.