Custom fields in ICWC

Question

Hi Gurus,
We added a custom field 'Channel' in agent inbox search view.This is to search the service tickets by communication channel.We implemented BADI CRM_IC_INBOX_BADI.
For search functionality , initially we had the following logic.
There is a method called CUSTOM_HIT_LIST_SORT. It receives table of records based on standard query. Inside this method we were looping at each record and were checking whether its communication channel was same as that of search parameter. If not equal, we were deleting it from table. But the method CUSTOM_HIT_LIST_SORT receives only the first 100 records which satisfy the standard query i.e. search is done based on standard fields which is wrong. According to SAP documentation, if we want to write custom query we should write in method BEFORE_SEARCH. But we do not know how to write it. So can any one help me regarding this.
Points will be rewarded for helpful answer.
Regards,
Raghu.

Answer 1

Hi,
I had the same issue with a field not part of the standard search
Found the actual database call, very good comment by the way:
CL_CRM_REPORT_ACC_DYNAMIC->GET_RESULTLIST_DYNAMIC
* here comes the real stuff
    IF <ft_guidlist> IS INITIAL.
      CALL METHOD database_access
        EXPORTING
          i_select    = g_select
          i_from      = g_from
          i_up_to_n   = g_up_to_n
          it_where    = gt_where
        IMPORTING
          et_guidlist = et_guidlist.
And I realized there was no way (or very complicated) to change the search to use my new field as well. The BAdI would not have helped so I just increased the number of hits from the standard 100, put in place same limits for the standard search criteria and also informed the user that the standard search stopped after the customized max. hits has been reached
Maximum number of hits is actually misleading in the case a search by custom field had been performed.
Let's say maximum number of hits (configurable parameter) is 1000 and to summarize it:
1.     Standard finds 900 hits of which only 100 will be displayed due to the non-standard search parameter.
2.     Standard stops at 1,000 hits but after 1,000 we could have other 20 items (or none at all and actually we do not have a way to know how many) so inform the user to change the search criteria (more restrictive) as to bring the standard result under 1,000 – good enough solution I think.
METHOD eh_onsearch .
        lr_result        TYPE REF TO if_bol_bo_col,
  counter = lr_result->SIZE( ).
  l_max_hits = cl_crm_aui_service=>gv_max_hits.
if counter = l_max_hits.
            CALL METHOD lr_msg_service->add_message
              EXPORTING
                iv_msg_type       = 'I'
endif.
Regards,
Mihai