Exit Search Help Standard /DSD/RPSH_EX_DRIVER

Hi guys,
I need know what is the best way to implement a exit search help standard.... I found that the help search /DSD/RPF1_SH has a exit search help called /DSD/RPSH_EX_DRIVER (Function Module), i need modify this exit search help standard.... the question is: is better unlock the object standard /DSD/RPSH_EX_DRIVER or create a copy of this Function Module into Function Module Z, then modify it and next link this Function Module to the search help?
Any suggestion?
Thanks.

/DSD/RPSH_EX_DRIVER has some unneccesary code in it... but it would be better to create another FM with the same signature and the code, and attach it to the search help.

Similar Messages

  • Search Help - Standard Screen Field: ME21n / ME22n

    Helow, experts.
    I have to create a search help in the standard screen field "Our Reference" (UNSEZ) in the tab  Communication to ME21n / ME22n, anyone could say me how can I code it?
    To populate this search help, I have to use 3 different tables.
    Thanks

    hi shatish
    code here in screen flow logic it will fire on F4 pressing.
    PROCESS ON VALUE-REQUEST
    module value_help.
    in program
    module value_help.
    populate the itab.
    CALL FUNCTION 'POPUP_WITH_TABLE'
                    EXPORTING
                      ENDPOS_COL         = <colvaluea>
                      ENDPOS_ROW         = <colvaluea>
                      STARTPOS_COL       = <colvaluea>
                      STARTPOS_ROW       = <colvaluea>
                      TITLETEXT          = 'VALUE HELP'
                  IMPORTING
                    CHOICE             =
                    TABLES
                      VALUETAB           = itab
                  EXCEPTIONS
                    BREAK_OFF          = 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.
    endmodole.
    regards
    shiba dutta

  • How to create user exit search help

    Hi,
    I have created a search help from se11 with a field (PT9653-ZDOCENTE) of table control.
    Now I want to fill another field (PT9653-ZMATERIA) of table control  when the user select a value in the search help.
    How do I do it?
    I read that I must use a user exit, is it correct?
    could you give me some examples?

    I have created a exit that should upgrade the second field with the function 
        dynpvaluetab2-fieldname = 'PT9653-ZDOC_TXT'.
        WRITE wa_nome TO dynpvaluetab2-fieldvalue.
        dynpvaluetab2-stepl = sy-stepl.
        APPEND dynpvaluetab2.
        CLEAR   dynpvaluetab2.
    CALL FUNCTION 'DYNP_VALUES_UPDATE'
          EXPORTING
            dyname     = 'MP965300'
            dynumb     = '2000'
          TABLES
            dynpfields = dynpvaluetab2.
    but it is not work.
    Instead, if the first use F4IF_INT_TABLE_VALUE_REQUEST to see the search help and then the DYNP_VALUES_UPDATE to update the other fields work.
      SELECT objid stext FROM hrp1000
        INTO CORRESPONDING FIELDS OF TABLE tab_materie
      WHERE plvar EQ '01'
       AND otype EQ 'ZM'.
      CALL FUNCTION 'F4IF_INT_TABLE_VALUE_REQUEST'
        EXPORTING
          retfield        = 'OBJID'
          dynpprog        = sy-repid
          dynpnr          = '2000'
          dynprofield     = 'PT9653-ZMATERIA'
          value_org       = 'S'
        TABLES
          value_tab       = tab_materie
          return_tab      = tb_ret_conc
        EXCEPTIONS
          parameter_error = 1
          no_values_found = 2
          OTHERS          = 3.
      IF sy-subrc <> 0.
        MESSAGE s000(zh) WITH 'Non trovati record per questa selezione'.
      ENDIF.
      GET CURSOR FIELD pt9653-zmateria LINE riga_corrente.
      READ TABLE tb_ret_conc INDEX riga_corrente.
      REFRESH dynpvaluetab.
      dynpvaluetab-fieldname = 'PT9653-ZMATERIA'.
      WRITE tb_ret_conc-fieldval  TO dynpvaluetab-fieldvalue.
      dynpvaluetab-stepl = riga_corrente.
      APPEND dynpvaluetab.
      CLEAR   dynpvaluetab.
      READ TABLE tab_materie WITH KEY objid = tb_ret_conc-fieldval.
      dynpvaluetab-fieldname = 'PT9653-ZMAT_TXT'.
      WRITE tab_materie-stext TO dynpvaluetab-fieldvalue.
      dynpvaluetab-stepl = riga_corrente.
      APPEND dynpvaluetab.
      CLEAR   dynpvaluetab.
      CALL FUNCTION 'DYNP_VALUES_UPDATE'
        EXPORTING
          dyname     = sy-repid
          dynumb     = sy-dynnr
        TABLES
          dynpfields = dynpvaluetab.
    bold The problem is that for this field, I need a collective search help , and therefore I can not use the F4IF_INT_TABLE_VALUE_REQUEST. bold

  • Search help + standard field

    Hi,
    is it possible to create a search help for a standard field (in a standard screen for FB60 transaction).
    how to make that? and how to attach this serch help to this field?
    best regards

    Hi,
    Please check this [Re: Adding a field in standard search help |Re: Adding a field in standard search help ] thread.
    Thanks,
    Abhijit

  • Search Help for ROUTE field in VA01

    Hi All,
       I need help in assigning search help to ROUTE(VBAP-ROUTE) field in VA01 Transaction.Instead of standard F4 list I need a list of Routes from the Custom table which will be maintaned.This new F4 list has to be displayed based on order types...Means only for order type ZXXX it should show the new F4 List, for the rest of the ordertypes it should show the standard F4 List.
    P.S : Search help H_TVRO is assigned to the Route.This Search help doesn't have Search help Exit or Append Search help options.
    Your help is highly appreciated.
    Thanks.
    Satyan.

    Hi,
       You can do that using search help exits you would find several threads already posted to the forum for this like below:
    Link[Search Help Exits|Search Help Exit;
    Regards,
    Himanshu

  • Search Help for Route - VA01

    Hi All,
    I need help in assigning search help to ROUTE(VBAP-ROUTE) field in VA01 Transaction.Instead of standard F4 list I need a list of Routes from the Custom table which will be maintaned.This new F4 list has to be displayed based on order types...Means only for order type ZXXX it should show the new F4 List, for the rest of the ordertypes it should show the standard F4 List.
    P.S : Search help H_TVRO is assigned to the Route.This Search help doesn't have Search help Exit or Append Search help options.
    Your help is highly appreciated.
    Thanks.
    Satyan.

    Hi Satyan
            for the search help H_TVRO you can create your own search help exit. search help exit is just a fm which will be executed when SH is hit..
    with out access key you can add the search help exit in the search help..
    https://wiki.sdn.sap.com/wiki/x/du0 this is my code for saerch help exit in CRM

  • Search help for material code in VA01

    Dear Experts,
    In VA01 tcode in item level if user press f4 in the material code then we will get all the f4 helps for few fields.Now i need to add one more field  mtart from mara table  in the existing  search help of material code.
    plz suggest me how can i proceed.
    If u have any documets regarding adding one more fied to existing search help plz send me.
    Thanks & Regards,
    farook.
    Edited by: farook shaik on Aug 18, 2009 8:58 AM

    Hi,
       You can do that using search help exits you would find several threads already posted to the forum for this like below:
    Link[Search Help Exits|Search Help Exit;
    Regards,
    Himanshu

  • Custom Search Help for the field Equipment number

    Hi,
    I have enchanced sales order transaction and included a field Equipment number(EQUI-EQUNR).
    Here after pressing F4(Search help) standard search help is display.
    I have a requirement wherein, the standard search help should not appear and a customised search where a specific Equipment category type values should appear in the search help.
    Ex. Field equipment  category (EQTYP).EQUNR(Equipment Number).
    Please let me know how to work for the customised search help.

    Hi,
    You need to create a customized search help.
    [Elementary Search Help - Structure|http://help.sap.com/saphelp_nw04/helpdata/EN/cf/21ee38446011d189700000e8322d00/content.htm]
    [Creating Elementary Search Helps|http://help.sap.com/saphelp_nw04/helpdata/EN/cf/21ee5f446011d189700000e8322d00/content.htm]
    Then you need to attach the search help to the screen field..
    [Assigning Search Helps to Screen Fields|http://help.sap.com/saphelp_nw04/helpdata/EN/cf/21ee93446011d189700000e8322d00/content.htm]
    [Hierarchy of Search Help Call|http://help.sap.com/saphelp_nw04/helpdata/EN/0b/32e9b798da11d295b800a0c929b3c3/content.htm]
    regards
    Nitesh

  • 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:
    <u>Field-name</u>-                        <u>field-value</u>
    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

  • Custom search help

    Hi expert,
    I want to create a search help that read data from a table and show this data, but only a selection of this data and not all.
    So, I created a custom search help, with an exit search help ( refernce at F4IF_SHLP_EXIT_EXAMPLE ).
    Inside this help I put the selection, with code like reference F4IF_SHLP_EXIT_EXAMPLE .
    My problem is: the match code show all data of table and not the selection !!!
    Any idea ???
    Tks a lot,
    bye.

    Hi,
      In the selection step after receiving the required entries from table you have to pass the details to the following FM 'F4UT_RESULTS_MAP'
    where SOURCE_STRUCTURE is the selection method name(Table structure name)
              APPLY_RESTRICTIONS = 'X'
             SOURCE_TAB is the table with u to pass the selected new entries
             other parameters are general..
         Finally set the CALLCONTROL-STEP = 'DISP'.
    Thanks&Regards,
    Karthik.

  • 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

  • Getting the value of a dynpro field in an exit for a standard search help.

    Hallo Experts!
    I need to modify the selected data displayed in standard sap search help: H_T357
    What I've done is create an exit for the search help.
    Then, when CALLCONTROL-STEP = 'DISP' I use the function module F4UT_PARAMETER_VALUE_GET and I get the value of the parameter 'WERKS' correctly. I think that this function module can only obtain values from the parameters of the search help. Well, here is the problem, I would like to get the values of dynpro fields
    'ILOA-STORT' and 'VIQMEL-QMART' (warning type) in transaction IW21.
    I prefer not to add these fields as parameters to the standard search help: H_T357.
    Any ideas for getting the value of these fields? I've seen functions modules: F4UT_GET_ENVIRONMENT and F4UT_SH_SIC_GET_FIELDS. But I don't know if I can use them  for my porpuses.
    Thanks a lot in advance.

    Hello again,
    I have already solved the problem using function module 'DYNP_VALUES_READ'.
    Thanks, David.

  • Skip standard select method in search help exit

    Hi experts,
    how to skip standard select method in search help exit? Currently I'm selecting my custom data with select statement in 'DISP' section, but still text: 'more than 500 results were found' is shown. I just want to skip/disable standard selection. Thank you.
    BR
    Paul

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

  • 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

Maybe you are looking for

  • Goods Receipt PO (Service Type) for generate accruals

    Hi, Just wonder that Service type of Goods Receipt PO possible write to the G/L or not? for item type of Goods Receipt PO, it can generated accruals. I want to generate accruals by Goods Receipt PO., else how am i going to generate accruals? Thanks.

  • Pages 5 exporting issues

    I go to export files to Word in .doc or .docx. After doing this I will try to open the document in microsoft word on a different computer. When I do this, the fle opens with no problem but inside the file or the text of the file is very messed up. Pa

  • DVD ROM query for embedding Powerpoint

    Hi, I am receiving conflicting advice on a job I have to output on Tuesday for a client. I have a 20 min NTSC video thats complete. The client has stated that they now need to have 2 powerpoint presentations, some pdfs and some jpgs added to the DVD.

  • Oracle 9i/10G DB authentication using Active Directory (with out OID)

    Hello All, We want to use a Single-Password authentication scheme using the Active Directory as the primary source for userId/Password. We don't want to use the Active Directory and OID bridge. As we have many databases and would like to configure al

  • Javascript stopped functioning when reader 9.2  installed

    I have a fillable PDF form that was designed using Live Cycle Designer - It uses a javascript to load XML data and fill the PDF form fields. This had been working previously in a previous version of Reader but has suddenly stopeed working now that Re