SEARCH HELP HANDLING

Hi Gurus,
Up tp now i am using elementary search helps.but now i am phasing the problem with collective search help.now in my scenario i want to use collective search help.but values are not getting with collective search help.Please give the suggetion.its very needful .
Regards,
Bixamaiah.

Hi Caíque Escaler,
I am using standard COM_PARTNER collective search help .already i was tried and implemented method GET_V* and GET_P* .I was tested in web ui also but whenever i was click on this input search help pop is also coming but records are not coming.Please give me the suggestion its very needful to for us..
Regards,
Bixamaiah.B.

Similar Messages

ALV search help handling

Is there anyone who has experience on providing self-defined search help for the input field in ALV .
Any help would be greatly appreciated.
Thanks in advance!

if you want to have dynamic search help, Pl. see this sample code..may be it will help u.
REPORT zooalvf14 .
Global data definitions for ALV.......................................
DATA : alvgrid TYPE REF TO cl_gui_alv_grid, custom_container TYPE REF TO cl_gui_custom_container, fieldcatalog TYPE lvc_t_fcat.
table to contain fields that require f4............................... DATA : lt_f4 TYPE lvc_t_f4 WITH HEADER LINE.
ok_code declaration................................................... DATA : ok_code TYPE sy-ucomm.
Tables declaration.................................................... TABLES : zemployee_c7.
Types declaration..................................................... TYPES : BEGIN OF ty_emp, empid LIKE zemployee_c7-empid, empname LIKE zemployee_c7-empname, END OF ty_emp.
Internal table declaration............................................ DATA : i_emp TYPE TABLE OF ty_emp.
Workarea declaration.................................................. DATA : wa_emp TYPE ty_emp.
Selection screen parameters........................................... SELECT-OPTIONS : s_empid FOR zemployee_c7-empid.
CLASS lcl_event_handler DEFINITION ---------------------------------------------------------------------
CLASS lcl_event_handler DEFINITION. PUBLIC SECTION. METHODS : handle_on_f1 FOR EVENT onf1 OF cl_gui_alv_grid IMPORTING e_fieldname es_row_no er_event_data, handle_on_f4 for event onf4 of cl_gui_alv_grid importing e_fieldname es_row_no er_event_data . ENDCLASS. ----
CLASS lcl_event_handler IMPLEMENTATION ---------------------------------------------------------------------
CLASS lcl_event_handler IMPLEMENTATION. METHOD handle_on_f1.
custom f1 help for empid field....................................... IF e_fieldname = 'EMPID'. CALL SCREEN 3001. ENDIF.
to prevent processing of standard f1 help............................ er_event_data->m_event_handled = 'X'. ENDMETHOD. Method handle_on_f4. standard f4 help will be invoked...................................... endmethod.
ENDCLASS.
start of selection....................................................
START-OF-SELECTION. SELECT empid empname FROM zemployee_c7 INTO CORRESPONDING FIELDS OF TABLE i_emp WHERE empid IN s_empid. CALL SCREEN 3000. &---- *& Module STATUS_3000 OUTPUT &---- * text ----
MODULE status_3000 OUTPUT. SET PF-STATUS 'ZTOOL'. SET TITLEBAR 'ZTITLE'. IF alvgrid IS INITIAL. CREATE OBJECT custom_container EXPORTING container_name = 'ZCONTAINER'. CREATE OBJECT alvgrid EXPORTING i_parent = custom_container. PERFORM prepare_f4. CALL METHOD alvgrid->register_f4_for_fields EXPORTING it_f4 = lt_f4[] . creating instance for event handler.................................. DATA : event_handler TYPE REF TO lcl_event_handler. CREATE OBJECT event_handler. SET HANDLER event_handler->handle_on_f1 FOR alvgrid. SET HANDLER event_handler->handle_on_f4 FOR alvgrid.
preparing field catalog.............................................. PERFORM prepare_fieldcatalog CHANGING fieldcatalog. CALL METHOD alvgrid->set_table_for_first_display * EXPORTING * I_BYPASSING_BUFFER = * I_BUFFER_ACTIVE = * I_CONSISTENCY_CHECK = * I_STRUCTURE_NAME = * IS_VARIANT = * I_SAVE = * I_DEFAULT = 'X' * IS_LAYOUT = * IS_PRINT = * IT_SPECIAL_GROUPS = * IT_TOOLBAR_EXCLUDING = * IT_HYPERLINK = * IT_ALV_GRAPHICS = * IT_EXCEPT_QINFO = CHANGING it_outtab = i_emp it_fieldcatalog = fieldcatalog * IT_SORT = * IT_FILTER = * EXCEPTIONS * INVALID_PARAMETER_COMBINATION = 1 * PROGRAM_ERROR = 2 * TOO_MANY_LINES = 3 * others = 4 . IF sy-subrc 0. * MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO * WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4. ENDIF. ENDIF. ENDMODULE. " STATUS_3000 OUTPUT
preparing field catalog............................................... FORM prepare_fieldcatalog CHANGING i_fieldcatalog TYPE lvc_t_fcat. DATA : ls_fcat TYPE lvc_s_fcat. ls_fcat-fieldname = 'EMPID'. ls_fcat-ref_table = 'ZEMPLOYEE_C7'. ls_fcat-coltext = 'EMPLOYEE ID'. APPEND ls_fcat TO i_fieldcatalog. CLEAR ls_fcat. ls_fcat-fieldname = 'EMPNAME'. ls_fcat-ref_table = 'ZEMPLOYEE_C7'. ls_fcat-coltext = 'EMPLOYEE NAME'. APPEND ls_fcat TO i_fieldcatalog. ENDFORM.
&---- *& Module USER_COMMAND_3000 INPUT &---- * text ----
MODULE user_command_3000 INPUT.
CASE ok_code.
WHEN 'BACK'.
LEAVE TO SCREEN 0.
WHEN 'EXIT'.
LEAVE PROGRAM.
ENDCASE.
ENDMODULE.
" USER_COMMAND_3000 INPUT &---- *&
Module USER_COMMAND_3001 INPUT &---- * text ---- MODULE user_command_3001 INPUT.
CASE ok_code.
WHEN 'SAVE'.
LEAVE TO SCREEN 0.
WHEN 'BACK'.
LEAVE TO SCREEN 0.
ENDCASE.
ENDMODULE.
" USER_COMMAND_3001 INPUT &---- *& Module STATUS_3001 OUTPUT &---- * text ---- MODULE status_3001 OUTPUT. SET PF-STATUS 'GUI'. SET TITLEBAR 'TITLE'. ENDMODULE. " STATUS_3001 OUTPUT preparing fields to be registered for f4 help......................... FORM prepare_f4. lt_f4-fieldname = 'EMPNAME'. lt_f4-register = 'X'. lt_f4-getbefore = 'X'. lt_f4-chngeafter = 'X'. APPEND lt_f4. ENDFORM.
hope this will help you.

Event Handling for free programmed search help bond dynamically in SO

Dear Expert,
I met a problem of how to handle an event raised by a free programmed search help - (F4), and this F4 is invoked
by a field defined in a Selection Option component (WDR_SELECT_OPTIONS) - SO.
The scenario is that I would like to update the SO after the user multiple select some entries in the F4. I could tranfer
back all the value chosen in the F4 to the consumer SO, but I can not update the icon in the SO(e.g in SO, multiple values will be
displayed with a green arrow icon), because I could not define a handler in SAP standard component SO, and it looks like there is no chance to catch the event triggered at the end of selection in F4. (this event belonged to this F4)
Welcome any suggestions or ideas, Thanks very very much.
In Addition, I use this way to enable the F4 for SO
lo_so_component->create_cmp_usage_group(
name = 'F4_TRANSPORT'
used_component = 'ZTRANSPORT').

thanks all

Handling the search help exporting parameters.

Hi all,
I am using a search help for an input field.My requirement is that on the selection of a row in the displayed result for search help two other fields needs to be populated in the UI , which actually are the exporting parametrs of the search help.I mean to say how to handle the exporting parameters of a search help so as to populate other input fields in the UI.

This is possible with the DDic Search help. From the online help:
If an input help structure is stored in a field in the ABAP Dictionary, and if you want to use the field mapping of search help parameters stored in the ABAP Dictionary as the field name for the structure for your Web Dynpro input help, then map your context nodes to this structure. This ensures that all components of the structure are available dynamically at runtime as attributes of the node.
If the context node is not mapped to the structure, the data element's input help can be used if there is one.
http://help.sap.com/saphelp_nw70ehp1/helpdata/en/47/9f724642314aabe10000000a42189b/frameset.htm

Event handler on search help PREM how to?

Hello!
I'm new to webdynpro and did already some basic tutorials.
One thing which isn't covered there i want to know...
I have for example to attributes.
PERSNO and ENAME.
On Perso i have the basic search help PREM
In my webdynpro i have these 2 Input fields. Now i need an event which fills the ENAME, after i selected a PERNR via the search help.
How can i handle these events?
greets thomas

Hi
see standard component WDR_TEST_OVS
this link will be helpful
https://www.sdn.sap.com/irj/sdn/wiki?path=/display/wdabap/abap%2bwd%2bobject%2bvalue%2bselector(OVS)
Abhi

Search help is not working

Hi All,
when am trying to search some ids using search help it is showing all ids.
For Ex: i want to search which ids starts with 'A', am give 'A*' but it is showing all ids.
Thanks in Advance

{FUNCTION /VIRSA/ZVIRFFOWNER.
""Local interface:
*" TABLES
*"      SHLP_TAB TYPE SHLP_DESCR_TAB_T
*"      RECORD_TAB STRUCTURE SEAHLPRES
*" CHANGING
*"     REFERENCE(SHLP) TYPE SHLP_DESCR_T
*"     REFERENCE(CALLCONTROL) LIKE DDSHF4CTRL STRUCTURE DDSHF4CTRL
EXIT immediately, if you do not want to handle this step
IF CALLCONTROL-STEP <> 'SELONE' AND
     CALLCONTROL-STEP <> 'SELECT' AND
     " AND SO ON
     CALLCONTROL-STEP <> 'DISP'.
    EXIT.
ENDIF.
STEP SELONE (Select one of the elementary searchhelps)
This step is only called for collective searchhelps. It may be used
to reduce the amount of elementary searchhelps given in SHLP_TAB.
The compound searchhelp is given in SHLP.
If you do not change CALLCONTROL-STEP, the next step is the
dialog, to select one of the elementary searchhelps.
If you want to skip this dialog, you have to return the selected
elementary searchhelp in SHLP and to change CALLCONTROL-STEP to
either to 'PRESEL' or to 'SELECT'.
IF CALLCONTROL-STEP = 'SELONE'.
PERFORM SELONE .........
    EXIT.
ENDIF.
STEP PRESEL (Enter selection conditions)
This step allows you, to influence the selection conditions either
before they are displayed or in order to skip the dialog completely.
If you want to skip the dialog, you should change CALLCONTROL-STEP
to 'SELECT'.
Normaly only SHLP-SELOPT should be changed in this step.
IF CALLCONTROL-STEP = 'PRESEL'.
PERFORM PRESEL ..........
    EXIT.
ENDIF.
STEP SELECT    (Select values)
This step may be used to overtake the data selection completely.
To skip the standard seletion, you should return 'DISP' as following
step in CALLCONTROL-STEP.
Normally RECORD_TAB should be filled after this step.
Standard function module F4UT_RESULTS_MAP may be very helpfull in this
step.
IF CALLCONTROL-STEP = 'SELECT'.
    EXIT. "Don't process STEP DISP additionally in this call.
ENDIF.
STEP DISP     (Display values)
This step is called, before the selected data is displayed.
You can e.g. modify or reduce the data in RECORD_TAB
according to the users authority.
If you want to get the standard display dialog afterwards, you
should not change CALLCONTROL-STEP.
If you want to overtake the dialog on you own, you must return
the following values in CALLCONTROL-STEP:
- "RETURN" if one line was selected. The selected line must be
the only record left in RECORD_TAB. The corresponding fields of
this line are entered into the screen.
- "EXIT" if the values request should be aborted
- "PRESEL" if you want to return to the selection dialog
Standard function modules F4UT_PARAMETER_VALUE_GET and
F4UT_PARAMETER_RESULTS_PUT may be very helpfull in this step.
IF CALLCONTROL-STEP = 'DISP'.
PERFORM AUTHORITY_CHECK TABLES RECORD_TAB SHLP_TAB
                          CHANGING SHLP CALLCONTROL.
    data: begin of i_idowner,
            zvirffid like /virsa/zvirffids-zvirffid,
            zvirffowner like /VIRSA/zvirffids-zvirffowner,
          end of i_idowner.
    data: wa_shlp TYPE SHLP_DESCR_T,
          iface like DDSHIFACE occurs 0 with header line.
   authority-check object 'GRCFF_0002' id 'YACTVT' field 'OWNR'.
   if sy-subrc = 0.
    select distinct zvirffowner into i_idowner from
       /VIRSA/ZVIRFFIDS.
      record_tab = i_idowner.
      append record_tab.
      clear: record_tab, i_idowner.
    endselect.
   else.
     select distinct zvirffrole into i_rolemonapvr from
        /VIRSA/ZFFROLES.
        where zvirffowner = sy-uname.
       record_tab = i_rolemonapvr.
       append record_tab.
       clear: record_tab, i_rolemonapvr.
     endselect.
endif.
    EXIT.
ENDIF.
ENDFUNCTION.}

How to implement F4IF_INT_TABLE_VALUE_REQUEST in search help User Exit?

Hi,
I need to enhanse search help and add F4 functionality to display list of company codes when cursor is in PBUKR field. I put F4IF_INT_TABLE_VALUE_REQUEST
into the user exit but nothing works.
I get error that PROCESS is not defined. If I remove that line there is no error but nothing works.
Can someone tell me what is wrong in the code below.
Thank you.
FUNCTION z_hr_shlp_wbs_element.
""Local interface:
*" TABLES
*"      SHLP_TAB TYPE SHLP_DESCR_TAB_T
*"      RECORD_TAB STRUCTURE SEAHLPRES
*" CHANGING
*"     VALUE(SHLP) TYPE SHLP_DESCR_T
*"     VALUE(CALLCONTROL) LIKE DDSHF4CTRL STRUCTURE DDSHF4CTRL
TABLES: prps.
DATA: it_prps LIKE prps OCCURS 0 WITH HEADER LINE.
DATA: status_tab LIKE jstat OCCURS 0 WITH HEADER LINE.
DATA: l_posid LIKE prps-posid.
DATA: l_subrc LIKE sy-subrc.
DATA: l_pbukr LIKE prps-pbukr,   " Added by vr
        value TYPE DDSHIFACE-VALUE.
EXIT immediately, if you do not want to handle this step
IF callcontrol-step <> 'SELONE' AND
     callcontrol-step <> 'SELECT' AND
                                       " AND SO ON
     callcontrol-step <> 'DISP'.
    EXIT.
ENDIF.
------------------------------------------------------ added by vr
PROCESS ON VALUE-REQUEST.
FIELD PRPS-PBUKR MODULE PBUKR.
DATA: BEGIN OF VALUE_TAB OCCURS 0,
LPBUKR LIKE PRPS-PBUKR,
LPOSID LIKE PRPS-POSID,
END OF VALUE_TAB.
DATA: BEGIN OF RETURN_TAB OCCURS 0.
INCLUDE STRUCTURE DDSHRETVAL.
DATA END OF RETURN_TAB.
SELECT PBUKR POSID FROM PRPS UP TO 20 ROWS
INTO TABLE VALUE_TAB WHERE SLWID = 'QLT UDF'.
CALL FUNCTION 'F4IF_INT_TABLE_VALUE_REQUEST'
EXPORTING
RETFIELD = 'PBUKR'
WINDOW_TITLE = 'Statusselektion'
VALUE_ORG = 'S' "hierdurch kann die Struktur genommen werden
TABLES
VALUE_TAB = VALUE_TAB
RETURN_TAB = RETURN_TAB
EXCEPTIONS
PARAMETER_ERROR = 1
NO_VALUES_FOUND = 2
OTHERS = 3.
end of additions
STEP SELONE (Select one of the elementary searchhelps)
This step is only called for collective searchhelps. It may be used
to reduce the amount of elementary searchhelps given in SHLP_TAB.
The compound searchhelp is given in SHLP.
If you do not change CALLCONTROL-STEP, the next step is the
dialog, to select one of the elementary searchhelps.
If you want to skip this dialog, you have to return the selected
elementary searchhelp in SHLP and to change CALLCONTROL-STEP to
either to 'PRESEL' or to 'SELECT'.
IF callcontrol-step = 'SELONE'.
PERFORM SELONE .........
    EXIT.
ENDIF.
STEP PRESEL (Enter selection conditions)
This step allows you, to influence the selection conditions either
before they are displayed or in order to skip the dialog completely.
If you want to skip the dialog, you should change CALLCONTROL-STEP
to 'SELECT'.
Normaly only SHLP-SELOPT should be changed in this step.
IF callcontrol-step = 'PRESEL'.
PERFORM PRESEL ..........
    EXIT.
ENDIF.
STEP SELECT    (Select values)
This step may be used to overtake the data selection completely.
To skip the standard seletion, you should return 'DISP' as following
step in CALLCONTROL-STEP.
Normally RECORD_TAB should be filled after this step.
Standard function module F4UT_RESULTS_MAP may be very helpfull in this
step.
IF callcontrol-step = 'SELECT'.
Maximum records are set to 0 because the counter for Max records keeps
running, even if you filter out certain records. This is a similar
problem as described in OSS Note 148525.
Feb 3, 2004 LS: devk907353
                (maxrecords = 0 defaults to maxrecords 500)
                As of release 4.7, it appears that maxrecords is
                being considered on the read of the view, rather
                than prior to presenting the selection list.
                When only 500 records are passed into this exit,
                the subsequent evaluation yields very few records
                in the selection list. By setting maxrecords to
                8000, the entire contents of the view are passed
                to this user exit, and therefor the search help
                yields a reasonable selection list to the user
                (as was the case in release 4.6b).
callcontrol-maxrecords = 0.        " devk907353
    callcontrol-maxrecords = 8000.     " devk907353
PERFORM STEP_SELECT TABLES RECORD_TAB SHLP_TAB
                      CHANGING SHLP CALLCONTROL RC.
IF RC = 0.
    CALLCONTROL-STEP = 'DISP'.
ELSE.
    CALLCONTROL-STEP = 'EXIT'.
ENDIF.
    EXIT. "Don't process STEP DISP additionally in this call.
ENDIF.
Added by vr, Nov. 2007 ---------------------------
CALL FUNCTION 'F4UT_PARAMETER_VALUE_GET'
EXPORTING
    PARAMETER               = 'PBUKR' " Reference to search help parameter
IMPORTING
    VALUE                   = value
TABLES
    SHLP_TAB                = shlp_tab
    RECORD_TAB              = record_tab
CHANGING
    SHLP                    = shlp
    CALLCONTROL             = callcontrol.
l_pbukr = value.
End of additions by vr ---------------------------
STEP DISP     (Display values)
This step is called, before the selected data is displayed.
You can e.g. modify or reduce the data in RECORD_TAB
according to the users authority.
If you want to get the standard display dialog afterwards, you
should not change CALLCONTROL-STEP.
If you want to overtake the dialog on you own, you must return
the following values in CALLCONTROL-STEP:
- "RETURN" if one line was selected. The selected line must be
the only record left in RECORD_TAB. The corresponding fields of
this line are entered into the screen.
- "EXIT" if the values request should be aborted
- "PRESEL" if you want to return to the selection dialog
Standard function modules F4UT_PARAMETER_VALUE_GET and
F4UT_PARAMETER_RESULTS_PUT may be very helpfull in this step.
IF callcontrol-step = 'DISP'.
DEVK909420 Begin
SELECT * FROM prps INTO TABLE it_prps
     WHERE belkz = 'X'.
Changed by vr, Nov. 2007
IF l_pbukr <> ''.
    SELECT * FROM prps INTO TABLE it_prps
       WHERE belkz = 'X'
         AND fkstl <> ''
         AND pbukr = l_pbukr.
    ELSE.
    SELECT * FROM prps INTO TABLE it_prps
       WHERE belkz = 'X'
         AND fkstl <> ''.
    ENDIF.
End of changes
DEVK909420 End
    SORT it_prps BY posid.
    LOOP AT record_tab.
      l_posid = record_tab+96(24).
      READ TABLE it_prps WITH KEY posid = l_posid.
      IF sy-subrc = 0.
        CALL FUNCTION 'STATUS_READ'
             EXPORTING
                  objnr       = it_prps-objnr
                  only_active = 'X'
             TABLES
                  status      = status_tab.
DEVK909329 Begin
        read table status_tab with key inact = ''
                                       stat = 'E0001'.
        if sy-subrc is initial.
          read table status_tab with key inact = ''         "DEVK909345
                                         stat = 'I0002'.   "DEVK909345
        endif.
DEVK909329 End
      ENDIF.
      IF sy-subrc NE 0.
        DELETE record_tab.
      ELSE.
       IF record_tab+114(1) EQ '.' AND
          record_tab+115(1) EQ '9'.
         DELETE record_tab.
       ELSE.
DEVK909420 Begin
        IF record_tab+102(1) EQ '9'.
          DELETE record_tab.
        ELSEIF record_tab+104(1) EQ '9'.
          DELETE record_tab.
        ENDIF.
DEVK909420 End
       ENDIF.
      ENDIF.
    ENDLOOP.
    EXIT.
ENDIF.
ENDFUNCTION.

Hi Vitaly,
Process on Value Request and search help exit is entirely two idea to display the f4 values.please remove the PROCESS ON VALUE REQUEST from the function module.write the required select statements after   CHECK callcontrol-step EQ 'SELECT' . and pass the value to the function module
CALL FUNCTION 'F4UT_RESULTS_MAP'
      TABLES
        shlp_tab          = shlp_tab
        record_tab        = record_tab
        source_tab        = l_record
      CHANGING
        shlp              = shlp
        callcontrol       = callcontrol
      EXCEPTIONS
        illegal_structure = 1
        OTHERS            = 2.
    IF sy-subrc <> 0.
      MESSAGE ID sy-msgid TYPE sy-msgty NUMBER sy-msgno
              WITH sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
    ENDIF.
    IF ( sy-subrc = 0 AND l_record IS INITIAL ).
      MESSAGE 'No values found' TYPE 'S'.
    ENDIF.
    callcontrol-step = 'DISP'.
Find the documentaion for this function module for further help
message edited by
shibu

SELECT-OPTIONS Values via DYNP_VALUES_READ in a Search Help Exit

Hi all,
I appended a standard search help of a standard report with a search help of my own. Now I am trying to retrieve the values the user has entered into the selection screen of the report using the FM DYNP_VALUES_READ in my search help exit FM. It works fine for single values defined by PARAMETERS and for low and high values of SELECT-OPTIONS (so_example-LOW and so_example-HIGH), but I need the entire SELECT-OPTIONS table. I cannot make any changes in the report, so do you have any solutions I could implement in my search help exit FM?
Many thanks!
Vladan
P.S.
I found several questions on this topic but they either just different enough not to be applicable in my case or the formatting has made the replies useless.

Most of the time we just copy the standard FM F4IF_SHLP_EXIT_EXAMPLE to a new one and give our own name.
You can see that on the 12th line there is the following code
* EXIT immediately, if you do not want to handle this step
IF CALLCONTROL-STEP <> 'SELONE' AND
     CALLCONTROL-STEP <> 'SELECT' AND
     " AND SO ON
     CALLCONTROL-STEP <> 'DISP'.
     EXIT.
ENDIF.
you should comment those line in order for the control to reach the PRESEL step (which is already defined in the SH Exit FM) which is on line 44.
Most of the time, when someone says they don't hit PRESEL, this is the problem.
Edited by: ajithkpunnoose on Jan 5, 2012 12:00 PM

About Running Remote Search Helps in SRM via Webdynpro ABAP

Hi there,
I am having troubles trying to implement an input help for a custom field in the standard Shopping Cart Portal page for item level.
I would like to implement the same input help used in field Network of Activities, but as I can see in WDA component '/SAPSRM/WDC_UI_DO_ACC', it seems to use another component in order to run a remote Search Help (I assume it is an original search help from PS system).
Does anybody know how to use this backend search help WDA Component? (/SAPSRM/WDC_UI_BACKEND_SH)
I haven´t found any information regarding that :S.
Another option would be to create a new RFC FM in PS returning the expected values, and use these entries to build a list value selector associated to the corresponding context attribute (This is not what I would like...)
Thanks in advance!

Vicente Ángel Lopez Romero wrote:
> Hi there,
>
> I am having troubles trying to implement an input help for a custom field in the standard Shopping Cart Portal page for item level.
>
> I would like to implement the same input help used in field Network of Activities, but as I can see in WDA component '/SAPSRM/WDC_UI_DO_ACC', it seems to use another component in order to run a remote Search Help (I assume it is an original search help from PS system).
>
> Does anybody know how to use this backend search help WDA Component? (/SAPSRM/WDC_UI_BACKEND_SH)
>
> I haven´t found any information regarding that :S.
>
>
> Another option would be to create a new RFC FM in PS returning the expected values, and use these entries to build a list value selector associated to the corresponding context attribute (This is not what I would like...)
>
> Thanks in advance!
Figured it out.
/SAPSRM/WDC_UI_BACKEND_SH is a 'freely programmed' search help used in SRM.
1. Add this helpview (HV) component usage to your component controller, and view controller.
2. Map HV SELECTION context to your view
3. Modify the context attribute you want backend searchhelp to 'freely programmed', and select the component usage created in step above (note this is done dynamically in SAP code, b/c attribute is defined as dictionary search help in SAP components) -- this took a bit to figure out.
4. IMPORTANT: Give your context attributes the SAME NAME (COST_CTR in my case) as those in structure /SAPSRM/S_CH_WD_MAP_ACC (how obvious was that)
5. IMPORTANT: Set your LOGSYS in /SAPSRM/CL_PDO_VALHELP_FACTORY class - love those those factories (tic)
DATA: lo_helper TYPE REF TO /SAPSRM/IF_PDO_ACCT_ASSGT_HLPR,
CALL METHOD /SAPSRM/CL_PDO_VALHELP_FACTORY=>GET_ACCT_ASSGT_HELPER
RECEIVING
RO_ACC_ASSGT_HELPER = lo_helper.
CALL METHOD lo_helper->set_searchhelp_control
EXPORTING
iv_logsys = ls_logsys-logsys.
6. Now handle event DATA_SELECTED to get data from SELECTION, and move to your Context field.
How simple was that? Yikes. I should have just built a custom dictionary search help to RFC over and call the BAPI for Cost Center List.
- Tim

Need some help in creating Search Help for standard screen/field

I need some help in adding a search-help to a standard screen-field.
Transaction Code - PP01,
Plan Version - Current Plan (PLVAR = '01'),
Object Type - Position ( OTYPE = 'S'),
Click on Infotype Name - Object ( Infotype 1000) and Create.
I need to add search help to fields Object Abbr (P1000-SHORT) / Object Name (P1000-STEXT).
I want to create one custom table with fields, Position Abb, Position Name, Job. Position Abb should be Primary Key. And when object type is Position (S), I should be able to press F4 for Object Abb/Object Name fields and should return Position Abbr and Position Name.
I specify again, I have to add a new search help to standard screen/field and not to enhance it.
This is HR specific transaction. If someone has done similar thing with some other transation, please let me know.
There is no existing search help for these fields. If sm1 ever tried or has an idea how to add new search help to a standard screen/field.
It's urgent.
Thanks in advace. Suitable answers will be rewarded

Hi Pradeep,
Please have a look into the below site which might be useful
Enhancing a Standard Search Help
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/daeda0d7-0701-0010-8caa-
edc983384237
http://help.sap.com/saphelp_nw04/helpdata/en/cf/21ee93446011d189700000e8322d00/frameset.htm
A search help exit is a function module for making the input help process described by the search help more flexible than possible with the standard version.
This function module must have the same interface as function module F4IF_SHLP_EXIT_EXAMPLE. The search help exit may also have further optional parameters (in particular any EXPORTING parameters).
A search help exit is called at certain timepoints in the input help process.
Note: The source text and long documentation of the above-specified function module (including the long documentation about the parameters) contain information about using search help exits.
Function modules are provided in the function library for operations that are frequently executed in search help exits. The names of these function modules begin with the prefix F4UT_. These function modules can either be used directly as search help exits or used within other search help exits. You can find precise instructions for use in the long documentation for the corresponding function module.
During the input help process, a number of timepoints are defined that each define the beginning of an important operation of the input help process.
If the input help process is defined with a search help having a search help exit, this search help exit is called at each of these timepoints. If required, the search help exit can also influence the process and even determine that the process should be continued at a different timepoint.
timepoints
The following timepoints are defined:
1. SELONE
Call before selecting an elementary search help. The possible elementary search helps are already in SHLP_TAB. This timepoint can be used in a search help exit of a collective search help to restrict the selection possibilities for the elementary search helps.
Entries that are deleted from SHLP_TAB in this step are not offered in the elementary search help selection. If there is only one entry remaining in SHLP_TAB, the dialog box for selecting elementary search helps is skipped. You may not change the next timepoint.
The timepoint is not accessed again if another elementary search help is to be selected during the dialog.
2. PRESEL1
After selecting an elementary search help. Table INTERFACE has not yet been copied to table SELOPT at this timepoint in the definition of the search help (type SHLP_DESCR_T). This means that you can still influence the attachment of the search help to the screen here. (Table INTERFACE contains the information about how the search help parameters are related to the screen fields).
3. PRESEL
Before sending the dialog box for restricting values. This timepoint is suitable for predefining the value restriction or for completely suppressing or copying the dialog.
4. SELECT
Before selecting the values. If you do not want the default selection, you should copy this timepoint with a search help exit. DISP should be set as the next timepoint.
5. DISP
Before displaying the hit list. This timepoint is suitable for restricting the values to be displayed, e.g. depending on authorizations.
6. RETURN (usually as return value for the next timepoint)
The RETURN timepoint should be returned as the next step if a single hit was selected in a search help exit.
It can make sense to change the F4 flow at this timepoint if control of the process sequence of the Transaction should depend on the selected value (typical example: setting SET/GET parameters). However, you should note that the process will then depend on whether a value was entered manually or with an input help.
7. RETTOP
You only go to this timepoint if the input help is controlled by a collective search help. It directly follows the timepoint RETURN. The search help exit of the collective search help, however, is called at timepoint RETTOP.
8. EXIT (only for return as next timepoint)
The EXIT timepoint should be returned as the next step if the user had the opportunity to terminate the dialog within the search help exit.
9. CREATE
The CREATE timepoint is only accessed if the user selects the function "Create new values". This function is only available if field CUSTTAB of the control string CALLCONTROL was given a value not equal to SPACE earlier on.
The name of the (customizing) table to be maintained is normally entered there. The next step returned after CREATE should be SELECT so that the newly entered value can be selected and then displayed.
10. APP1, APP2, APP3
If further pushbuttons are introduced in the hit list with function module F4UT_LIST_EXIT, these timepoints are introduced. They are accessed when the user presses the corresponding pushbutton.
Note: If the F4 help is controlled by a collective search help, the search help exit of the collective search help is called at timepoints SELONE and RETTOP. (RETTOP only if the user selects a value.) At all other timepoints the search help exit of the selected elementary search help is called.
If the F4 help is controlled by an elementary search help, timepoint RETTOP is not executed. The search help exit of the elementary search help is called at timepoint SELONE (at the
F4IF_SHLP_EXIT_EXAMPLE
This module has been created as an example for the interface and design of Search help exits in Search help.
All the interface parameters defined here are mandatory for a function module to be used as a search help exit, because the calling program does not know which parameters are actually used internally.
A search help exit is called repeatedly in connection with several
events during the F4 process. The relevant step of the process is passed on in the CALLCONTROL step. If the module is intended to perform only a few modifications before the step, CALLCONTROL-STEP should remain unchanged.
However, if the step is performed completely by the module, the following step must be returned in CALLCONTROL-STEP.
The module must react with an immediate EXIT to all steps that it does not know or does not want to handle.
Hope this info will help you.
***Reward points if found useful
Regards,
Naresh

Search Help for input field2 based on value entered in input field 1

Hi All,
I have a requirement where in my view, i have two fields.
1. PO
2. PO Item
For PO i could get the standard search help from DDIC, but i need to provide search help for PO Item based on PO selected.
How can i do that. Any help is highly appreciated.
Thanks,
Ajay

Hi Ajay ,
following steps cn help u :
1 Declare the WDR_OVS Component in the used component list in your WD component .
2 Now go to the View, in the Properties Tab click the Create Controller Usage Button.
3 It will open a screen with Component Use Entries. There select the Component Use OVS with Interface Controller . Press Enter.
4 Go to the Context Tab, Right Click the Context and select Create à Attribute , for PO item in ur case .
5 In the Input Help Mode Field, Select u2018Object Value Selectoru2019 from the dropdown. Then press F4 in the Field OVS Component Usage.
6 Declare one event handler method with Name ON_OVS in the Method tab of the view. Then Press F4 in the Column Event.
Select the Event OVS as shown below and Press Enter.
for more info and illustration , also refer :
http://help.sap.com/saphelp_erp2005/helpdata/EN/30/d7fa41c915da6fe10000000a1550b0/content.htm
https://wiki.sdn.sap.com/wiki/display/WDABAP/ABAPWDObjectValueSelector(OVS)
http://wiki.sdn.sap.com/wiki/display/Snippets/OVSSearchHelpinWebDynproAbap
regrds,
amit

Steps for creation of search help exit for a search help

Hi,
I have created a search help. I need to create a search help exit for this search help.
Please let me know how to create a search help exit as well as how to link it to my search help.

1)Copy the FM F4IF_SHLP_EXIT_EXAMPLE to write your own FM. (check the documentation and coding of FM F4IF_SHLP_EXIT_EXAMPLE).
2)write your code depending upon the functionality you want.
3)attach the FM in search help through SE11 in "search help exit" field.
A search help exit is a function module for making the input help process described by the search help more flexible than possible with the standard version.
This function module must have the same interface as function module F4IF_SHLP_EXIT_EXAMPLE. The search help exit may also have further optional parameters (in particular any EXPORTING parameters).
A search help exit is called at certain timepoints in the input help process.
Note: The source text and long documentation of the above-specified function module (including the long documentation about the parameters) contain information about using search help exits.
Function modules are provided in the function library for operations that are frequently executed in search help exits. The names of these function modules begin with the prefix F4UT_. These function modules can either be used directly as search help exits or used within other search help exits. You can find precise instructions for use in the long documentation for the corresponding function module.
This module has been created as an example for the interface and design of Search help exits in Search help.
All the interface parameters defined here are mandatory for a function module to be used as a search help exit, because the calling program does not know which parameters are actually used internally.
A search help exit is called repeatedly in connection with several events during the F4 process. The relevant step of the process is passed on in the CALLCONTROL step. If the module is intended to perform only a few modifications before the step, CALLCONTROL-STEP should remain unchanged.
However, if the step is performed completely by the module, the following step must be returned in CALLCONTROL-STEP.
For more detailed information please refer to the documentation describing the concept of the search help exit.
The module must react with an immediate EXIT to all steps that it does not know or does not want to handle.

How to Enhance search help for product groups. Currently no ability to add multiple lines from result list

Hi All,
In CRM Web UI, there is no multi selection option for product group id f4 help for Custmer event creation or edit screen under “Product” tab=> Product Group ID field.
Web UI Component Details -
UI component : TPMOE
View : TPMOE/ProductEOL
Context: PRODUCT Attribute : -PRODUCT_GRUOP
Click on Product Group ID field then below F4 Help screen appears.
In the product group results list, user can select only one row and Then all the product will be queried for selected product group, transferred to product list tab.
Current technical design for Product Group F4:
a) SE11 Data Dictionary search help “CRM_MKTPL_PGRP1” is used and data is fetched displayed based it( Refer method GET_V_PRODUCT_GROUP of context node class CL_TPMOE_PRODUCTEOL_CN00)
b) In UI, F4 pop up is handled by UI Framework in SAP generic manner so no multi selection is allowed.
c) A round trip event is triggered after selection of row from results which reload view with queried product result based group selected.
Requirement :-
In the product group F4 results list View, user should be able to select multiple row .As SAP GUI has the option of multiple entry selection from search help window with the help of field called MULTISEL.
System should query for products with all selected product group, transferred to product list tab.
Note: - The multi select options works fine for GUI, but for UI standard SAP code ignores this or never is this structure taken into consideration. Standard class to display F4 help on UI is CL_THTMLB_F4HELP.
Can we enforce same behavior like DDIC search help in Web UI too Or suggest how we can achieve this requirement?
Thanks in advance
Regards,
Arjun

Hello All,
We have achieved this requirement by Custom development and approach followed as -
Define UI object model zprgrp & zprgrpquery and object relationship in table ZCRM_OBJTAB
Query Strcuture : ZCRMST_PRGRP_SEARCH & Result List structure : ZCRMST_PRGRP_RESULT
Created Custom component : ZPRGRP with Search /Result view and with GENIL Class, search logic
Defined custom ComponentUsage “ProductGroup1SearchHelp” for ZPRGRP in Standard Component TPMOE
e. Called F4 application for field product _group with help component usage created in step d.
Regards,
Arjun

Enhancing F4 Search Help Issue - Standard Component

Hello All,
We have a requirement in SRM to customize couple of standard Search helps attached to the Webdynpro components. As such I know the concept of how we can handle this requirement but hitting an issue.
Standard Working scenario -
1) Standard Structure available with multiple fields. Two fields that are of our interest are SH_VALUE and SH_VALUE_LABEL.
2) Standard Search help for this being used has fields VALUE and VALUE_LABEL.
3) In the Structure the both the fields SH_VALUE and SH_VALUE_LABEL are mapped to the Search help VALUE and VALUE_LABEL.
4) In the WD component the node is mapped to the standard structure.
Running the application and the picking up the values from F4 on the SH_VALUE field will return its corresponding value and also map the SH_VALUE_LABEL field with the Label from the F4 since the structure and Search help mapping are there.
So far good when its standard.
Issue I am facing -
We need to modify this standard search help to customize our needs.
1) Did a Copy of the standard Search help and then modified to suit our needs. The output structure of the search is still the same as the standard one.
2) Did a Post Exit in the WD component to call our custom search help through the below code -
data lo_nd_attrib type ref to if_wd_context_node.
data lo_nd_attrib_info type ref to if_wd_context_node_info.
lo_nd_attrib = wd_context->path_get_node( path = `ATTRIBUTES_DATA.ATTR_DTLS_MULT` ).
lo_nd_attrib_info = lo_nd_attrib->get_node_info( ).
lo_nd_attrib_info->set_attribute_value_help( name = 'SH_VALUE' value_help_mode = '121' value_help = 'Z_ORG_ATTR' ).
lo_nd_attrib_info->set_attribute_value_help( name = 'SH_VALUE_LABEL' value_help_mode = '121' value_help = 'Z_ORG_ATTR' ).
Running the application just returns the SH_VALUE field but does not get the data for the SH_VALUE_LABEL.
Is there something wrong in the way I am calling the Custom Search help or should I need to approach this differently?
Thanks,
Nagarajan.

Hi Nagarajan,
Well, you are trying to set the search help to both attributes ( sh_value, sh_value_label) individually and it is having no link between these two attributes
i.e. once you select a value from search help of SH_VALUE, its no where linked that the other details to be passed to SH_VALUE_LABEL.
We generally, do the linking of attributes to search help parameters at structure level as below
So, if you need the same behaviour, then you need to assign the Zsearch help at strucuture field SH_VALUE and link the parameters to both fields SH_VALUE & SH_VALUE_LABEL
In case, if find it not possible to to this way,
You need to populate the value of field SH_VALUE_LABEL upon selection of value from search help of SH_VALUE.
i.e. by registering the search help selection event to an OnEnter action and write the logic to populate the value to SH_VALUE_LABEL
Please refer the below link
Automatically Trigger onEnter event after selecting value from the Value Help(F4 Help)
Hope this helps you.
Regards,
Rama

Problem in Search Help Exit

Hi Experts,
I have aproblem in Search help Exit. I have added tab to the standard search help by creating elemntry search help and assigned that search help to standard search help. I am calling function module for search help exit. I dont have any selection method.
I am getting the epected results by using the funtion module F4UT_RESULTS_MAP. This funtion module displays all the results list. My only problem i have is when i select the value from the results list the value is not populating in to the field.
CALL FUNCTION 'F4UT_RESULTS_MAP'
    TABLES
      shlp_tab          = shlp_tab
      record_tab        = record_tab
      source_tab        = lt_export
    CHANGING
      shlp              = shlp
      callcontrol       = callcontrol
    EXCEPTIONS
      illegal_structure = 1
      OTHERS            = 2.
The callcontrol-step = 'RETURN'.
how can i handle this step to populate the select record in the field.
Thanks,
Edited by: FRANCIS REDDY on Jun 11, 2008 5:42 PM

Hi check my weblog: https://wiki.sdn.sap.com/wiki/x/du0

SEARCH HELP HANDLING

Similar Messages

Maybe you are looking for