Search Help Import Parameter as Listbox

How to make a search help parameter as Listbox( with Key ). Currently all search help parameters in F4 Dialog will be input fields with value help been fected from data element/domain.
I need the parameter as list box because only then I could populate the text along with the value.
Like there is a domain whose fixed values are 1- Active, 2 - Locked etc,
When I use a search help parameter with a data element of the above domain, then during F4, THE SEARCH HELP DIALOG has this parameter as 1. The text "Active also should appear ideally"
FYI: the parameter is an import parameter.
Best Regards,
Ragha.

Please check the below program...
REPORT ztest_sri.
TYPE-POOLS: vrm.
DATA: it_list TYPE vrm_values,
 wa_list LIKE LINE OF it_list,
 id TYPE vrm_id.
DATA: gv_menge TYPE menge_d.
PARAMETERS: p_box LIKE mara-matnr AS LISTBOX VISIBLE LENGTH 10.
INITIALIZATION.
REFRESH: it_list.
CLEAR: wa_list, p_box.
wa_list-key = 'Srinu'.
wa_list-text = 'Srinivasu'.
APPEND wa_list TO it_list.
wa_list-key = 'Radha'.
wa_list-text = 'Radha Krishna'.
APPEND wa_list TO it_list.
id = 'P_BOX'.
CALL FUNCTION 'VRM_SET_VALUES'
 EXPORTING
 id = id
 values = it_list
 EXCEPTIONS
 id_illegal_name = 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.
START-OF-SELECTION.
WRITE: p_box.
thanks,
Srinivas

Similar Messages

Search help import parameter

Hi,
I have 2 columns in my ALV table. COL_A and COL_B.
My requirement is to populate the search help entries of COL_B based on COL_A. but if COL_A is left blank then search help of COL_B should display all values based on user access.
Can I access value of import parameter (COL_A) of dictionary search help in search help exit so that i would know whether COL_A is empty or not.
Please let me know how can I access value of import parameter of dictionary search help in search help exit .
Thanks,
Feroz

Hi Feroz,
It is easy..
Just mention both column A and column B as importing paramenter.
and use this code skeleton..
use it in the "select" call control step
CALL FUNCTION 'F4UT_RESULTS_MAP'
    EXPORTING
      source_structure   = 'XXXXXXXXX'
      apply_restrictions = ' '
    TABLES
      shlp_tab           = shlp_tab
      record_tab         = record_tab
      source_tab         = 'XXXXXXXX'
    CHANGING
      shlp               = shlp
      callcontrol        = callcontrol
    EXCEPTIONS
      OTHERS             = 0.
    CALL FUNCTION 'F4UT_PARAMETER_RESULTS_PUT'
    EXPORTING
      PARAMETER   = 'XXXXXXX'    "this can be your column A
      fieldname   = 'XXXXXXXXX'
    TABLES
      shlp_tab    = shlp_tab
      record_tab = record_tab[]
      source_tab = lt_time_range
    CHANGING
      shlp        = shlp
      callcontrol = callcontrol.
callcontrol-step = 'DISP'.
    CALL FUNCTION 'F4UT_PARAMETER_RESULTS_PUT'
    EXPORTING
      PARAMETER   = 'XXXXXXX'    "this can be your column B
      fieldname   = 'XXXXXXXXX'
    TABLES
      shlp_tab    = shlp_tab
      record_tab = record_tab[]
      source_tab = lt_time_range
    CHANGING
      shlp        = shlp
      callcontrol = callcontrol.
callcontrol-step = 'DISP'.
here, source_structure is the structure of the table where the data is available which is the "source_tab".
Parameter field is the name of parameter specified in search help. and fieldname is the field corresponding to the paramer in the table "source_tab".

How to add search help to custom infotype listbox??

Hi All,
How to add search help to custom infotype listbox??
Thanks in advance

Hi Vinay,
We have search help and list box as 2 different options.
At a time we can make a field a list box or a search help.List box is restricted and we can pick values from the defined list whereas in search help we can allow more entries and then validate the value entered later.
Implementing a listbox or search help in infotype is same as that of implementing it in a modulepool .
for search help..we can create a custom search help or check for existing search help in se11
then in the screen on infotype field..assign the search help direcly at the screen painter level..
double click on the field in screen painter -> change mode and then in the space for "search help" enter the search helps name
for list box..in the screen painter ,make sure the field is selected as list box..then in PAI of screen we do a
(Process on value-request..field fieldname module module name)..check syntax and other details...
Using function module vrm_set_value fill the field and populate it as required
Pls check and revert
Regards
Byju

Need to create search help for parameter 2 based on values in parameter1

hi Specialists,
I need to create a search help for parameters field 2 ( Country ) based on the values the user inputs in parameters field 1 ( Currency ). The values of field Currency & Country will come from T001 table.
The logic is : Based on a unique currency value ( fetched from T001 table ) user needs to get/see all Countries on his selection -screen.
Can you guys let me know which FM can I use for above & how to pass various values i.e. parameters into that FM. EXplanation with an example/code is highly appreciable.
Thanks
Abhinav.

Hi Abhinav,
Use this demo code, its working:-
This code selects sale document item based on the user entry for sales document on the screen field.
REPORT ztg_f1f4.
CALL SCREEN 1010.
*& Module GET_F4_HELP INPUT
* text
MODULE get_f4_help INPUT.
TYPES : BEGIN OF it,
 posnr TYPE zvbap-posnr,
 END OF it.
DATA : itab TYPE STANDARD TABLE OF it WITH HEADER LINE,
 tb_dynpfields LIKE dynpread OCCURS 0 WITH HEADER LINE,
 vbeln TYPE zvbap-vbeln.
CLEAR: tb_dynpfields.
REFRESH: tb_dynpfields.
MOVE 'ZVBAP-VBELN' TO tb_dynpfields-fieldname. "screen field name
APPEND tb_dynpfields.
CALL FUNCTION 'DYNP_VALUES_READ'
 EXPORTING
 dyname = 'ZTG_F1F4'
 dynumb = '1010'
* TRANSLATE_TO_UPPER = ' '
* REQUEST = ' '
* PERFORM_CONVERSION_EXITS = ' '
* PERFORM_INPUT_CONVERSION = ' '
* DETERMINE_LOOP_INDEX = ' '
* START_SEARCH_IN_CURRENT_SCREEN = ' '
* START_SEARCH_IN_MAIN_SCREEN = ' '
* START_SEARCH_IN_STACKED_SCREEN = ' '
* START_SEARCH_ON_SCR_STACKPOS = ' '
* SEARCH_OWN_SUBSCREENS_FIRST = ' '
* SEARCHPATH_OF_SUBSCREEN_AREAS = ' '
 TABLES
 dynpfields = tb_dynpfields
* EXCEPTIONS
* INVALID_ABAPWORKAREA = 1
* INVALID_DYNPROFIELD = 2
* INVALID_DYNPRONAME = 3
* INVALID_DYNPRONUMMER = 4
* INVALID_REQUEST = 5
* NO_FIELDDESCRIPTION = 6
* INVALID_PARAMETER = 7
* UNDEFIND_ERROR = 8
* DOUBLE_CONVERSION = 9
* STEPL_NOT_FOUND = 10
* OTHERS = 11
IF sy-subrc <> 0.
* MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
* WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
READ TABLE tb_dynpfields INDEX 1.
IF sy-subrc EQ 0.
 vbeln = tb_dynpfields-fieldvalue.
ENDIF.
SELECT posnr FROM zvbap
 INTO TABLE itab
WHERE
 vbeln = vbeln.
CALL FUNCTION 'F4IF_INT_TABLE_VALUE_REQUEST'
 EXPORTING
* DDIC_STRUCTURE = ' '
 retfield = 'POSNR'
* PVALKEY = ' '
 dynpprog = 'ZTG_F1F4'
 dynpnr = '1010'
 dynprofield = 'POSNR'
* STEPL = 0
* WINDOW_TITLE =
* VALUE = ' '
 value_org = 'S'
* MULTIPLE_CHOICE = ' '
* DISPLAY = ' '
* CALLBACK_PROGRAM = ' '
* CALLBACK_FORM = ' '
* MARK_TAB =
* IMPORTING
* USER_RESET =
 TABLES
 value_tab = itab
* FIELD_TAB =
* RETURN_TAB =
* DYNPFLD_MAPPING =
* EXCEPTIONS
* PARAMETER_ERROR = 1
* NO_VALUES_FOUND = 2
* OTHERS = 3
IF sy-subrc <> 0.
* MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
* WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
ENDMODULE. " GET_F4_HELP INPUT
Hope this solves your problem.
Thanks & Regards,
Tarun Gambhir

Calling search Help with parameter/

I have selection-screen as follows
PARAMETERS : p_bukrs1 TYPE bukrs ,
p_kostl1 TYPE kostl .
PARAMETERS : p_bukrs2 TYPE bukrs ,
p_kostl2 TYPE kostl .
Req: When user press F4 on P_KOSTL1, it should display cost centers only for company code value entered in P_BUKRS1, similarly for P_KOSTL2 it should display cost centers for comapny code entered in P_BUKRS2.
I know I can select records on AT SELECTION-SCREEN .. ON VALUE-REQUEST for respective fields and display in F4 with some FM .
Is there any method by which I can call the search help specifying the company code as parameter?

by using FM DYNP_VALUES_READ u can get the values of BUKRS.
based on the values of BUKRS get values of Cost Centres from DB tables into Internal tables
F4IF_INT_TABLE_VALUE_REQUEST by using this u can display.
Regards
peram

Search help for Parameter

Hi all
i am using F4IF_INT_TABLE_VALUE_REQUEST
to display help request. but i need more then one field in the help
example ::
numner -
description
thanks in advance.
Naval Bhatt

*& Report Z4
REPORT Z4.
parameters: p_vbeln type vbak-vbeln default '0000004969',
            p_posnr type vbap-posnr.
at selection-screen on value-request for p_posnr.
data: begin of help_item occurs 0,
          posnr type vbap-posnr,
         matnr type vbap-matnr,
         arktx type vbap-arktx,
        end of help_item.
data: dynfields type table of dynpread with header line.
dynfields-fieldname = 'P_VBELN'.
append dynfields.
call function 'DYNP_VALUES_READ'
       exporting
            dyname               = sy-cprog
            dynumb               = sy-dynnr
            translate_to_upper   = 'X'
       tables
            dynpfields           = dynfields
       exceptions
            invalid_abapworkarea = 1
            invalid_dynprofield = 2
            invalid_dynproname   = 3
            invalid_dynpronummer = 4
            invalid_request      = 5
            no_fielddescription = 6
            invalid_parameter    = 7
            undefind_error       = 8
            double_conversion    = 9
            stepl_not_found      = 10
            others               = 11.
read table dynfields with key fieldname = 'P_VBELN'.
p_vbeln = dynfields-fieldvalue.
call function 'CONVERSION_EXIT_ALPHA_INPUT'
       exporting
            input = p_vbeln
       importing
            output = p_vbeln.
select posnr into table help_item    " cabn select multiple
                 from vbap
                      where vbeln = p_vbeln.
call function 'F4IF_INT_TABLE_VALUE_REQUEST'
       exporting
            retfield    = 'POSNR'
            dynprofield = 'P_POSNR'
            dynpprog    = sy-cprog
            dynpnr      = sy-dynnr
            value_org   = 'S'
       tables
            value_tab   = help_item.

Import screen field value into search help assigned to a different field

Hi,
I have created an elementary search help based on a custom DDIC table ZSH_SHHLDR. Dialog Type: Dialog depends on set of values, search help parameters:
Parameter Import Export LPos SPos SDis
FOLIO X 1 1 X
CERTN X 2 2
where FOLIO and CERTN are fields in my table.
There are two fields in my program defined as like FOLIO and CERTN respectively. These fields are screen fields in a custom dynpro created using Screen Painter. The search help is assigned to the CERTN field. In the screen, I want that the contents of the FOLIO field should be imported into the search help, i.e. on the screen:
FOLIO: 21353
CERTN: <F4>
When I click on F4 help for CERTN, I want that the FOLIO parameter in the search help should contain the value for FOLIO that I entered in the text box on the screen. Is there a way to do this, through an exit for instance? Help is appreciated, thanks.
Regards

Hi,
You need to use the below statement.
process on value-request.
field zcom_doa_users-zzjob_role module sub_tes_module.
Here I declared three fields in the screen fields from structure zcom_doa_users. Try to name the fields with table name-field name. So inside the module in structure zcom_doa_users you will get given value for the other fields also.
Now you can do your own processing for f4 help.
Thanks
Subhankar

Search Help parameter not passing in FM

A Search Help ZAMCH1 is included in collective search help MCH1.Within it an elementary search help ZMME_CHARG2 is included.In this Elementary Search Help, a parameter 'CHRUE' ( Inventary Indicator) is there with data element 'ZMM_CHARG_IND' and default value 'X'.
But this parameter is not passed into the search help exit i.e. the function module.All other parameters are passed correctly in structure 'shlp-selopt' except CHRUE.So the indicator is always blank in FM.what might may be the reason and remedy ?

Since your search help starts with the letter Z, it is a custom search help. So we can't look at the code to see what might be going on. You can try posting more specific information from the search helps here, and then someone might be able to help you.
- April King

How to create search help on a parameter

Hi all,
How to create search help on a parameter .Please tell me process .
Regards,

Hi,
If you want to create search help in parameter check that search help is available
by going to se11 or
create search help there ..
Please check the following links to create a search helps. They guide you step by ste.
Link:[http://www.sap-img.com/abap/attach-a-search-help-to-the-screen-field.htm]
Regards
Vinu.r

Field values are repeating for search help.

Hello Friends.
I have a problem. When I create a search help for a field the identical field values are repeating. What should I do to trigger only the first time.
for example:
Field-name- field-value
Supplier Nr --- Commodity
5001 -
 casting
5002 -
 casting
5003 -
 casting
So when I create the search help for commodity it is showing 'casting' 3 times in a pop-up window. It should not repeat. Can you please give me the solution what should I do?

Hi
Search helps
Standard search help
Types of search helps
Concept of search help
Search Help Interface
Dialog behavior of search helps
Selection method for search helps
Performance of search helps
Attaching search helps
Hierarchy of search helps
Standard Search Help
The input help (F4 help) is a standard function of the R/3 System. It permits the user to display a list of possible values for a screen field. A value can be directly copied to an input field by list selection.
The fields having an input help are shown in the R/3 System by the input help key to the right of the field. This key appears as soon as the cursor is positioned on the corresponding screen field. The help can be started either by clicking on this screen element or with function key F4.
If the number of possible entries for a field is very large, you can limit the set of displayed values by entering further restrictions.
Further meaningful information about the displayed values is included in the display of possible entries, especially if the field requires that a formal key be entered.
TYPES OF SEARCH HELPS
Elementary search helps
Describe a search path. The elementary search help must define where the data of the hit list should be read from (selection method), how the exchange of values between the screen template and selection method is implemented (interface of the search help) and how the online input help should be defined (online behavior of the search help).
Collective search help
Combine several elementary search helps. A collective search help thus can offer several alternative search paths.
Search Help Interface
Search help interface determines how the exchange of values between the screen template and the selection method is implemented.
The search help interface defines the context data that can be used in the input help and the data that can be returned to the input mask. Analogously to the interface of a function module, the search help interface comprises interface parameters.
When you define an interface parameter of a search help, you must also define whether it should be used to copy data to the input help (IMPORT parameter) or whether it should be used to return data from the input help (EXPORT parameter). A parameter of a search help can also have both attributes at the same time.
The location from which the IMPORT parameters of a search help get their values and the screen fields in which the contents of the EXPORT parameters of the search help are returned are defined in the search help attachment. The search help itself should always be attached to an EXPORT parameter of the search help. If this parameter is also the IMPORT parameter, its contents are only used in the input help if it is a search string (that is, if it contains a ´*´ or a ´+´).
You must define the parameter types of a search help. You can do this by assigning them data elements.
Value Transport for Input Helps
NOTE:In the above example, screen fields A, B and C are linked with parameters of the search help. As a result, values can only be transported between the screen and the search help for these three fields. Existing contents of screen fields A and B can be used for selecting the hit list since they are linked with an import parameter of the search help. The values of parameters A and C can be returned to the screen from the hit list since these parameters are declared as export parameters of the search help.
Description of dialog behavior
A hit list might contain plentiful number of entries. A
dialog provides the user with an option to restrict the
entries displayed on the hit list.
In an input help process, the set of possible entries is presented in the dialog box as a list for displaying the hit list. The user selects the required value from this list by double clicking. Since the possible entries are often formal keys, you must be able to display further explanatory information about the possible entries in the list.
If the set of possible entries is very large, the user should be able to define additional conditions for the attributes of the selected entry. Restricting the set of data in this way both increases the clarity of the list and reduces the system load. Additional conditions can be entered in a further dialog window, the dialog box for restricting values.
Specifying the dialog type of a search help defines whether the dialog box for restricting values should be offered and if so under what conditions.
The attributes in the dialog box for displaying the hit list or in the dialog box for restricting values must be defined as internal parameters of the search help. An internal parameter can also be used in only one of the two dialog boxes. It can also belong to the search help interface.
The internal parameter types are also defined with data elements. These data elements define how the parameters are displayed in the two dialog boxes.
Reward if usefull

Assign Search help in report program

Dear All,
I facing problem to assign search help in report program.
I crated one elementary search help in which three fields i include
-carrid
-carrier name
-booking
all three fields having import and export parameter in search help.
while executing this search help in se11 it gives proper output.
but while assigning this search help in report program it only fetch one carried.
my report is also having three parameter
-carrid
-carrier name
-booking
i assign search help like
PARAMETER : p_carrid TYPE scarr-carrid
                           MATCHCODE OBJECT z01_carrid,
with all three field but it fetch only carrid ...

Hi Chintan,
For such types of requirements you can use this Function Module:
F4IF_INT_TABLE_VALUE_REQUEST.
Use this functiom modue under AT SELECTION-SCREEN ON HELP-REQUEST FOR P_CARRID.
With this function module, you can fill your remainng parameters : P_carriername and booking also.
Sample Code:
     DATA : TMP_RETURN_TAB LIKE TABLE OF DDSHRETVAL,                                TMP_RETURN      LIKE DDSHRETVAL,
                TMP_FIELD       TYPE DFIES-FIELDNAME.
CASE AKIND.
   WHEN '1'.
     TMP_FIELD = 'AENNR'.
   WHEN '2'.
     TMP_FIELD = 'VBELN'.
   WHEN '3'.
     TMP_FIELD = 'ZZTEHAI'.
ENDCASE.
CALL FUNCTION 'F4IF_INT_TABLE_VALUE_REQUEST'
   EXPORTING
     RETFIELD               = TMP_FIELD
     WINDOW_TITLE           = ATITEL
     VALUE_ORG              = 'S'
   TABLES
     VALUE_TAB              = ATABLES
     RETURN_TAB             = TMP_RETURN_TAB
   EXCEPTIONS
     PARAMETER_ERROR        = 1
     NO_VALUES_FOUND        = 2
     OTHERS                 = 3.
IF SY-SUBRC = 0.
    READ TABLE TMP_RETURN_TAB INDEX 1 INTO TMP_RETUN.
    AVALUE = TMP_RETURN-FIELDVAL.
ENDIF.
Jus analyze this code, you can get ur requirement done.
Regards
Sandeep Reddy

Search Help Value Not reflecting in WebUI

Hello All, We have a requirement to create a standard F4 value help for PRODUCT_ID field and the selected value should be reflected in the WebUI field. This field is in a table view context node and the component is a stand alone WebUI component. Everything works fine till the Search help is called and the values is selected. But the selected value is not reflected in the Product_ID field. We have checked many forums and links and tried almost all the alternatives suggested. Here's is the code attached for reference.
DATA:l_wa_map       TYPE if_bsp_wd_valuehelp_f4descr=>gtype_param_mapping,
       l_i_inmap     TYPE if_bsp_wd_valuehelp_f4descr=>gtype_param_mapping_tab,
       l_i_outmap    TYPE if_bsp_wd_valuehelp_f4descr=>gtype_param_mapping_tab.
DATA: lv_str_index TYPE string.
* l_wa_map-context_attr = 'product_id'.
* l_wa_map-f4_attr      = 'PRODUCT_ID'.
* APPEND l_wa_map TO:l_i_inmap,l_i_outmap.
lv_str_index = iv_index.
CONCATENATE 'table[' lv_str_index '].PRODUCT_ID' INTO l_wa_map-context_attr.
l_wa_map-f4_attr = 'KEY'. "'PRODUCT_ID'. "'
APPEND l_wa_map TO: l_i_outmap.
lv_str_index = iv_index.
CONCATENATE 'table[' lv_str_index '].PRODUCT_ID' INTO l_wa_map-context_attr.
l_wa_map-f4_attr = 'VALUE'. "'PRODUCT_ID'.   "
APPEND l_wa_map TO: l_i_outmap.
CREATE OBJECT rv_valuehelp_descriptor TYPE cl_bsp_wd_valuehelp_f4descr
     EXPORTING
      iv_help_id        = 'COM_PR_SHTEXT'      "#EC NOTEXT
      iv_help_id_kind   = if_bsp_wd_valuehelp_f4descr=>help_id_kind_name "if_bsp_wd_valuehelp_f4descr=>help_id_kind_comp
      iv_input_mapping = l_i_inmap
      iv_output_mapping = l_i_outmap
      iv_object_ref     = me
      iv_trigger_submit = abap_true.
Is there any further code or event call required to reflect the value in the WebUI? or what exactly is required to be done here?
Thanks in Advance.
Prasad

Hi Kamlesh,
Check that you have checked for import and export in your search help for parameter ATBEZ
Refer my reply in here [F4 Help|HELP NEEDED....F4 VALUE HELP IN WEB UI;
Regards
Jignesh

HOW DO WE CREATRE SEARCH HELP ?

HOW DO WE CREATRE SEARCH HELP ? PLEASE EXPLAIN.
REWARD POINTS GUARENTEED !!

Hi
Input helps (F4 helps) for screen fields can be defined with search helps.
Search helps
1)Standard search help
2)Types of search helps
3)Concept of search help
4)Search Help Interface
5)Dialog behavior of search helps
6)Selection method for search helps
7)Performance of search helps
8)Attaching search helps
9)Hierarchy of search helps
Standard Search Help
The input help (F4 help) is a standard function of the R/3 System. It permits the user to display a list of possible values for a screen field. A value can be directly copied to an input field by list selection.
The fields having an input help are shown in the R/3 System by the input help key to the right of the field. This key appears as soon as the cursor is positioned on the corresponding screen field. The help can be started either by clicking on this screen element or with function key F4.
If the number of possible entries for a field is very large, you can limit the set of displayed values by entering further restrictions.
Further meaningful information about the displayed values is included in the display of possible entries, especially if the field requires that a formal key be entered.
TYPES OF SEARCH HELPS
Elementary search helps Describe a search path. The elementary search help must define where the data of the hit list should be read from (selection method), how the exchange of values between the screen template and selection method is implemented (interface of the search help) and how the online input help should be defined (online behavior of the search help).
Collective search help Combine several elementary search helps. A collective search help thus can offer several alternative search paths.
Context data: You first have to define the context data to be used in the input help process. The context contains the information obtained in previous dialog steps and the entries already made by the user in the current input mask. This information is normally used to restrict the possible values for the current input field.
Dialog behavior: It describes the order of the dialog windows to be displayed during the input help and what they should look like.
Data collection method: It defines where the values offered to the user for selection come from.
Return values: When a value is selected from the list of possible entries, it is stored in the search field. This often results in the contents of further screen fields, such as explanatory text, being updated. You therefore should define which values can be returned to the screen.
In addition to describing an input help, you must define the fields for which it should be used. This is part of the field definition (of the search fields).
In Release 4.0, the search help was introduced in the ABAP Dictionary as a new object type. A search help is an object that describes the input help process. The individual components of such a description can be defined with attributes of the search help.
Search helps are subject to the same rules concerning their maintenance, activation and transport as all other objects of the ABAP Dictionary.
Search helps provide greater flexibility and functionality for defining input helps than the matchcode and help view object types offered up to Release 3.x.
Search Help Interface
Search help interface determines how the exchange of values between the screen template and the selection method is implemented.
The search help interface defines the context data that can be used in the input help and the data that can be returned to the input mask. Analogously to the interface of a function module, the search help interface comprises interface parameters.
When you define an interface parameter of a search help, you must also define whether it should be used to copy data to the input help (IMPORT parameter) or whether it should be used to return data from the input help (EXPORT parameter). A parameter of a search help can also have both attributes at the same time.
The location from which the IMPORT parameters of a search help get their values and the screen fields in which the contents of the EXPORT parameters of the search help are returned are defined in the search help attachment. The search help itself should always be attached to an EXPORT parameter of the search help. If this parameter is also the IMPORT parameter, its contents are only used in the input help if it is a search string (that is, if it contains a ´*´ or a ´+´).
You must define the parameter types of a search help. You can do this by assigning them data elements.
Value Transport for Input Helps
NOTE:In the above example, screen fields A, B and C are linked with parameters of the search help. As a result, values can only be transported between the screen and the search help for these three fields. Existing contents of screen fields A and B can be used for selecting the hit list since they are linked with an import parameter of the search help. The values of parameters A and C can be returned to the screen from the hit list since these parameters are declared as export parameters of the search help.
Description of dialog behavior
A hit list might contain plentiful number of entries. A
dialog provides the user with an option to restrict the
entries displayed on the hit list.
In an input help process, the set of possible entries is presented in the dialog box as a list for displaying the hit list. The user selects the required value from this list by double clicking. Since the possible entries are often formal keys, you must be able to display further explanatory information about the possible entries in the list.
If the set of possible entries is very large, the user should be able to define additional conditions for the attributes of the selected entry. Restricting the set of data in this way both increases the clarity of the list and reduces the system load. Additional conditions can be entered in a further dialog window, the dialog box for restricting values.
Specifying the dialog type of a search help defines whether the dialog box for restricting values should be offered and if so under what conditions.
The attributes in the dialog box for displaying the hit list or in the dialog box for restricting values must be defined as internal parameters of the search help. An internal parameter can also be used in only one of the two dialog boxes. It can also belong to the search help interface.
The internal parameter types are also defined with data elements. These data elements define how the parameters are displayed in the two dialog boxes.
Dialog Types
The dialog type of an elementary search help defines how the hit list is displayed when the input help is called. It defines the dialog steps executed for input help.
The following dialog types are possible:
Immediate value display: The hit list is immediately displayed when the input help is called. This is only meaningful if the hit list usually only contains a few entries.
Complex dialog with value restriction: The dialog window for restricting values is offered immediately. Choose this option if the list of possible entries is usually very large. If the user limits the amount of data to be processed, the hit list will become more comprehensible and the system load during value selection will be reduced.
Dialog depending on number of values: If the hit list contains less than 100 entries, it is displayed immediately. If the hit list contains more than 100 entries, the dialog box for restricting values is displayed.
The following dialog types are possible:
Immediate value display: The hit list is immediately displayed when the input help is called. This is only meaningful if the hit list usually only contains a few entries.
Complex dialog with value restriction: The dialog window for restricting values is offered immediately. Choose this option if the list of possible entries is usually very large. If the user limits the amount of data to be processed, the hit list will become more comprehensible and the system load during value selection will be reduced.
Dialog depending on number of values: If the hit list contains less than 100 entries, it is displayed immediately. If the hit list contains more than 100 entries, the dialog box for restricting values is displayed.
Selection method for Search help
Selection method refers to the database object (database
table or view) from which data is selected and displayed
in the hit list.
The possible entries displayed for a field by the input help are determined at runtime by a selection from the database. When a search help is defined, you must define the database object from which the data should be selected by specifying a table or a view as selection method.
The fields of the selection method are assigned to the parameters of the search help if their names are the same. Restricting the hit list, which is formulated with a parameter of the search help, is also used to formulate a WHERE condition for the field of the selection method having the same name (if one exists). Vice versa, the parameters of the search help appearing in the hit list are assigned the contents of the fields of the selection method having the same name.
If the selection method is a table having a text table, the non-key fields of this text table can also be used in the search help. In this case the corresponding entries of the logon language are automatically taken into consideration in the selection. These columns remain empty for values that do not have text in the logon language.
If the selection method is client-dependent, your client field may not appear as a parameter of the search help. The search help is always selected in the current client.
Performance of an Input help
We must ensure that the hit list is displayed in minimum
time with minimum load on the system.
It is imperative to optimize accessing behavior especially when selection uses a view and thus more than one table.
This can be done by restricting the hit list
By additional restricting conditions from the context.
Restricting conditions entered by the user in a dialog.
Performance of the input help could be greatly improved by creating an index on the fields used to formulate the restrictions.
A large amount of data sometimes has to be searched in the selections for an input help. This means that the user might have to wait a long time for the possible entries to be displayed, and can also result in a significant increase in the load on the system.
When defining a search help, you should therefore check whether you should take measures to optimize the accessing behavior for the selection method. This is especially true if the selection uses a view and thus more than one physical table.
If the number of entries in the selection method is very large, you should restrict the hit list with further conditions. This also increases the clarity of the hit list. The additional conditions can directly result from the context, or can be entered in the dialog box for restricting values by the user. The performance of the input help can frequently be significantly improved by creating an index on the fields used to formulate the restrictions.
If a restriction is defined with the secondary table of a help view, the selection is automatically performed as an inner join. In this case you should replace the help view with a database view.
Attaching a search help to a field
A search help can influence the behavior of a field when the input help is called. The search help must be assigned to the field in order to do this. You have the following options for this assignment:
Attach search help to a data element / table or structure field / screen field / check table.
Conventionally search helps are attached to table fields or data elements. We shall see the same.
Choose the field name, click on search help tab and
provide the name of the search help.
A search help is attached to a field of a table or structure in the maintenance transaction for this table/structure, analogously to attaching to a table. You must assign the interface parameters of the search help to any fields of the table/structure. The search field must be assigned to an EXPORT parameter of the search help at this time.
Attach the search help to the table field
The search help ZSTRAVELAG_NAME is therefore directly attached to the field AGENCYNUM of table ZSTRAVELAG.
Provide the search help name and the parameter name
under the further characteristics tab of the data element.
If the input help of a field is defined by its data element, no further screen fields can be used in the input help.
Also note that the input F4 help would be available wherever the data element is used.
A search help can be directly assigned to a screen field in two ways.
The name of the search help must be entered in the Screen Painter in the Attributes for the field in the field Search help.
The name of the search help can be defined for selection screens in ABAP reports in the PARAMETERS or SELECT-OPTIONS statement directly following the supplement MATCHCODE OBJECT.
However, input help is only available for this particular screen.
Collective search help
A Collective search help provides alternative search
Paths by combining elementary search helps.
Only one search help can be attached to a field, table or data element. Several search paths are therefore attached with a collective search help.
A collective search help also has interface parameters like
an elementary search help.
Like an elementary search help, a collective search help has an interface of IMPORT and EXPORT parameters with which the search help exchanges data. Using this interface, the collective search help can be attached to fields, tables and data elements exactly like an elementary search help.
Parameter assignment needs to be done for each of the
Included search helps.
When you define a collective search help, there are no components for describing the dialog behavior and data selection; instead the included search helps are listed here. You must assign the parameters of the collective search help to the interface parameters of the included search help for each inclusion.
User may choose the tab and thus the elementary
search method.
When we execute the search help SCUSTOM, we are confronted with a dialog which gives us an option of either restricting
By 1)Search for customer according to booking
2)Search for customer according to name.
These are effectively the elementary search helps (SCUSTOM_BOOK and SCUSTOM_NAME) which have been included in the collective search help SCUSTOM.
HOT KEY
The hot key is used to select the elementary search help from the collective search help and to enter the restrictions in the dialog box for restricting values directly from the entry field. If the user often searches for values using the same search help, this procedure can save time.
Reward if usefull

Hi, tell me abt creation of search helps in detail

hi, tell me abt creation of search helps in detail

Hi
Search helps
Standard search help
Types of search helps
Concept of search help
Search Help Interface
Dialog behavior of search helps
Selection method for search helps
Performance of search helps
Attaching search helps
Hierarchy of search helps
Standard Search Help
The input help (F4 help) is a standard function of the R/3 System. It permits the user to display a list of possible values for a screen field. A value can be directly copied to an input field by list selection.
The fields having an input help are shown in the R/3 System by the input help key to the right of the field. This key appears as soon as the cursor is positioned on the corresponding screen field. The help can be started either by clicking on this screen element or with function key F4.
If the number of possible entries for a field is very large, you can limit the set of displayed values by entering further restrictions.
Further meaningful information about the displayed values is included in the display of possible entries, especially if the field requires that a formal key be entered.
TYPES OF SEARCH HELPS
Elementary search helps
Describe a search path. The elementary search help must define where the data of the hit list should be read from (selection method), how the exchange of values between the screen template and selection method is implemented (interface of the search help) and how the online input help should be defined (online behavior of the search help).
Collective search help
Combine several elementary search helps. A collective search help thus can offer several alternative search paths.
Context data: You first have to define the context data to be used in the input help process. The context contains the information obtained in previous dialog steps and the entries already made by the user in the current input mask. This information is normally used to restrict the possible values for the current input field.
Dialog behavior: It describes the order of the dialog windows to be displayed during the input help and what they should look like.
Data collection method: It defines where the values offered to the user for selection come from.
Return values: When a value is selected from the list of possible entries, it is stored in the search field. This often results in the contents of further screen fields, such as explanatory text, being updated. You therefore should define which values can be returned to the screen.
In addition to describing an input help, you must define the fields for which it should be used. This is part of the field definition (of the search fields).
In Release 4.0, the search help was introduced in the ABAP Dictionary as a new object type. A search help is an object that describes the input help process. The individual components of such a description can be defined with attributes of the search help.
Search helps are subject to the same rules concerning their maintenance, activation and transport as all other objects of the ABAP Dictionary.
Search helps provide greater flexibility and functionality for defining input helps than the matchcode and help view object types offered up to Release 3.x.
Search Help Interface
Search help interface determines how the exchange of values between the screen template and the selection method is implemented.
The search help interface defines the context data that can be used in the input help and the data that can be returned to the input mask. Analogously to the interface of a function module, the search help interface comprises interface parameters.
When you define an interface parameter of a search help, you must also define whether it should be used to copy data to the input help (IMPORT parameter) or whether it should be used to return data from the input help (EXPORT parameter). A parameter of a search help can also have both attributes at the same time.
The location from which the IMPORT parameters of a search help get their values and the screen fields in which the contents of the EXPORT parameters of the search help are returned are defined in the search help attachment. The search help itself should always be attached to an EXPORT parameter of the search help. If this parameter is also the IMPORT parameter, its contents are only used in the input help if it is a search string (that is, if it contains a ´*´ or a ´+´).
You must define the parameter types of a search help. You can do this by assigning them data elements.
Value Transport for Input Helps
NOTE:In the above example, screen fields A, B and C are linked with parameters of the search help. As a result, values can only be transported between the screen and the search help for these three fields. Existing contents of screen fields A and B can be used for selecting the hit list since they are linked with an import parameter of the search help. The values of parameters A and C can be returned to the screen from the hit list since these parameters are declared as export parameters of the search help.
creation of Elementary Search Help
Enter the search help name and click on create.
Choose elementary search help radio button option as the search help type.
Enter the search help parameters, the selection method and activate the search help.
Collective Search Help steps
Enter the search help name and click on create.
Choose Collective search help radio button option as the search help type.
Enter the search help parameters.
Note that there is no selection method to be entered for a collective search help.
Instead of the selection method, we enter the included
search helps for the collective search help.
We need to assign parameters for each of the included
search helps.
Complete the parameter assignment by clicking on the push button
Collective search help offers the user to obtain F4 help
using any of the included search helps.
Attaching a search help to a field
A search help can influence the behavior of a field when the input help is called. The search help must be assigned to the field in order to do this. You have the following options for this assignment:
Attach search help to a data element / table or structure field / screen field / check table.
Conventionally search helps are attached to table fields or data elements. We shall see the same.
Attaching a search help to a screen element
A search help can be directly assigned to a screen field in two ways.
The name of the search help must be entered in the Screen Painter in the Attributes for the field in the field Search help.
The name of the search help can be defined for selection screens in ABAP reports in the PARAMETERS or SELECT-OPTIONS statement directly following the supplement MATCHCODE OBJECT.
However, input help is only available for this particular screen.
In this case, the search help is only available for this screen.
OR by useing FM
refer this code
TYPES : BEGIN OF ST_OBJID_SH,
OTYPE TYPE HRP1000-OTYPE,
OBJID TYPE HRP1000-OBJID,
END OF ST_OBJID_SH.
DATA : IT_OBJID_SH TYPE STANDARD TABLE OF ST_OBJID_SH.
DATA : WA_OBJID_SH TYPE ST_OBJID_SH.
***********SELECTION SCREEN DESIGN***********************
SELECTION-SCREEN BEGIN OF BLOCK B1 WITH FRAME TITLE TEXT-001.
*SELECT-OPTIONS : S_OTYPE FOR HRP1001-OTYPE NO INTERVALS .
SELECT-OPTIONS : S_OBJID FOR HRP1001-OBJID NO INTERVALS .
SELECT-OPTIONS : DATE FOR SY-DATUM NO-EXTENSION OBLIGATORY.
SELECTION-SCREEN END OF BLOCK B1.
**********END OF SELECTION SCREEN DESIGN*****************
*********VALIDATION FOR SCREEN FIELDS********************
AT SELECTION-SCREEN ON VALUE-REQUEST FOR S_OBJID-LOW.
IF S_OBJID IS NOT INITIAL.
SELECT OTYPE OBJID FROM HRP1000
INTO TABLE IT_OBJID_SH
WHERE OTYPE = 'D'.
IF SY-SUBRC EQ 0.
SEARCH HELP FOR QUALIFICATION.
CALL FUNCTION 'F4IF_INT_TABLE_VALUE_REQUEST'
EXPORTING
DDIC_STRUCTURE = ' '
RETFIELD = 'OBJID'
PVALKEY = ' '
DYNPPROG = SY-REPID
DYNPNR = SY-DYNNR
DYNPROFIELD = 'S_OBJID'
STEPL = 0
WINDOW_TITLE =
VALUE = ' '
VALUE_ORG = 'S'
MULTIPLE_CHOICE = ' '
DISPLAY = ' '
CALLBACK_PROGRAM = ' '
CALLBACK_FORM = ' '
MARK_TAB =
IMPORTING
USER_RESET =
TABLES
VALUE_TAB = IT_OBJID_SH
FIELD_TAB =
RETURN_TAB = RETURN_TAB
DYNPFLD_MAPPING =
EXCEPTIONS
PARAMETER_ERROR = 1
NO_VALUES_FOUND = 2
OTHERS = 3
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.
Elementary search helps Describe a search path. The elementary search help must define where the data of the hit list should be read from (selection method), how the exchange of values between the screen template and selection method is implemented (interface of the search help) and how the online input help should be defined (online behavior of the search help).
Collective search help Combine several elementary search helps. A collective search help thus can offer several alternative search paths.
steps
Elementary Search Help
1) Goto SE11
Enter the search help name and click on create.
2)Choose elementary search help radio button option as the search help type.
3)Enter the search help parameters, the selection method and activate the search help.
Collective Search Help
1)Enter the search help name and click on create.
2)Choose Collective search help radio button option as the search help type.
3)Enter the search help parameters.
Note that there is no selection method to be entered for a collective search help.
4)Instead of the selection method, we enter the included
search helps for the collective search help.
5)We need to assign parameters for each of the included
search helps.
6)Complete the parameter assignment by clicking on the push button
7)Collective search help offers the user to obtain F4 help
using any of the included search helps.
http://help.sap.com/saphelp_nw04/helpdata/en/cf/21ee2b446011d189700000e8322d00/content.htm
http://help.sap.com/saphelp_nw04/helpdata/en/cf/21ee5f446011d189700000e8322d00/content.htm
http://help.sap.com/saphelp_nw04/helpdata/en/cf/21ee86446011d189700000e8322d00/content.htm

Populate and display internal table results using search help exit...

I have copied F4IF_SHLP_EXIT_EXAMPLE and made changes. I want this search help exit to populate and display contents related to 'FIELD1' when the user enters a specific value for it in the search help screen, meaning when the user restricts the search by that value. For field2, field3, field4, field5, field6, field7, and field8 I am using a custom view.
Following is the code:
TYPES: BEGIN OF t_search,
               field2 TYPE field2,
               field3 TYPE field3,
               field4 TYPE field4,
               field5 TYPE field5,
               field6 TYPE field6,
               field7 TYPE field7,
               field8 TYPE field8,
               field1 TYPE field1,
            END OF t_search.
DATA: it_itab TYPE TABLE OF t_search,
        wa TYPE t_search,
     wa_selopt TYPE ddshselopt,
        wa_fielddescr TYPE dfies.
ranges: r_field1 for std_table1-field1
STEP SELECT    (Select values)
    FREE: r_field1.
**Get the value entered for FIELD1 in search help
    LOOP AT shlp-selopt INTO wa_selopt.
      CASE wa_selopt-shlpfield.
        WHEN 'FIELD1'.
          r_field1-sign = wa_selopt-sign.
          r_field1-option = wa_selopt-option.
          r_field1-low = wa_selopt-low.
          r_field1-high = wa_selopt-high.
          APPEND r_field1.
          CLEAR: r_field1.
      ENDCASE.
    ENDLOOP.
**Select 'ID' and 'FIELD1' from table into lt_itab
    SELECT id field1
          INTO TABLE lt_itab
            FROM std_table1
              WHERE field1 IN r_field1.
    IF sy-subrc = 0.
**Now, based on the particular IDs from lt_itab, I need to select other values
from other tables which also have 'ID' as the key.
       SELECT std_table2~field2
            std_table2~field3
            std_table3~field4
            std_table3~field5
            std_table3~field6
            std_table4~field7
            std_table4~field8
            std_table1~field1
          INTO CORRESPONDING FIELDS OF TABLE it_itab
          FROM std_table2
                     INNER JOIN std_table3 ON
                            std_table3mandt = std_table2mandt AND
                            std_table3id = std_table2id
                     INNER JOIN std_table4 ON
                            std_table4mandt = std_table2mandt AND
                            std_table4id = std_table2id
                     INNER JOIN std_table1 ON
                            std_table1mandt = std_table2mandt AND                                           std_table1id = std_table2id
          WHERE
                std_table1~field1 IN r_field1.
'id' is common in all the std_tables --> std_table1, std_table2, std_table3, std_table4.
STEP DISP     (Display values)
**Then I need to gather all the results in my internal table it_itab and display
in search help results for the value of FIELD1 entered by the user in the search help.
    CALL FUNCTION 'F4UT_PARAMETER_RESULTS_PUT'
      EXPORTING
        parameter   = 'FIELD1'
        fieldname   = 'FIELD1'
      TABLES
        shlp_tab    = shlp_tab
        record_tab = record_tab
        source_tab = it_itab
      CHANGING
        shlp        = shlp
        callcontrol = callcontrol.
I am not getting all the data in my internal table and wanted to know if there is anyting wrong in my select statement.
Any guidance will be appreciated and awarded appropriate points.
Thanks.

the webdynpro fieldname and the search help input parameter name were made same.

Search Help Import Parameter as Listbox

Similar Messages

Maybe you are looking for