Search help supporting only 5000 entries

Hi,
I have created a search help, my data base table consists of
22,676 records. when I am executing my search help,
I am getting a pop up saying 'Only first 5000 wil be displayed'
Can anyone tel me how to show all records.
Regards,
Shilpa

hi,
In the search help (SE11)
give the dialog behaviour as Display values Immediately
(or)
in the help menu
goto setting
in the F4 tab
you can restrict the hits
give  in field your required value  Max. number of hits to be displayed
regards
prasanth

Similar Messages

  • Search help - Display only 500 entries at one time from Internal Table

    Hi,
    I have an internal table with 1000000 entries. And when I use F4IF_INT_TABLE_VALUE_REQUEST function module to display the search help with internal table, it gives me dump. Can somebody help me - how to display limited values when we process search help?
    Thanks,
    Sheel

    Hi Sheel
    u have a variable callcontrol-maxrecords in search help exit to limit the number of records.. check my weblog for more help: https://wiki.sdn.sap.com/wiki/x/du0

  • Table Search Help to Remove Duplicate Entry

    Hi All Tha ABAP GURUS,
    I have created 2 tables say A with fields main description and sub decription and another table B in which there are these 2 fields with other fields. I want to display search help for Table B for fields main description and sub decription separately and I have done the same by creating Elementary Search Help (ZDS and ZDM resp.) . For sub description it is working fine and for main description it is displaying value but duplicate. How to remove these duplicate values.
    For Eg Values are
    Main Desc   Sub Desc
    1                   A
    1                   B
    1                   C
    2                   D
    2                   E
    In my case it is showing
    1
    1
    1
    2
    2
    but I want
    1
    2
    I want to achieve this without creating any ZProg. Can I use search help exit.Kindly guide me in this matter how to use it.
    Thanks & Regards,
    Bharti Jain

    Yes you can delete duplicates in a search help exit, but not without "without creating any ZProg" as you will create a Function Module (and Group)
    Duplicate the sample FM F4IF_SHLP_EXIT_EXAMPLE in a customer function group, and delete duplicate records of RECORD_TAB in the step 'DISP' (executed before display).
    You could also perform the select yourself adding a DISTINCT option to the statement in the 'SELECT' step but this will take more time to develop, as you must read the other parameters to use selections provided by user or program.
    Regards
    Raymond,

  • Search Help - No of entries returned

    Hello ,
    I am working on a search Help exit and noticied that  even we change the Value assigned to Parameter " Maximum no of Hits"  to 9999 system brings backonly 1st 5000 entries. Somehow SAP is controlling that. I tired to change CALLCONTROLL-MAXRECORDS TO 5000 in Debug Mode also but still get's only 5000 entries.
    anyone knows about a OSS note or something written somewhere in R/3 Library about this limitation.
    Thanks
    L

    Hi Lakhbir,
    Check the Note "Note 172687 - Collective note: search help control".
    Restrictions on the length of the hit list
    The number of the entries that the search help control
    displays on its hit list is limited to a sensible number
    of entries for a search help (5000).
    Increasing the length of the hit list causes serious
    performance and stability problems in the control
    used for displaying. If you need a hit list with more
    than 5000 entries switch to the usual search help
    frontend:
    Switching between R/3 dialog and ActiveX support
    It is possible to toggle the support of the search
    help by the search help control according to your needs.
    To do this there are three setting options:
    Search help with ActiveX - support
    Search help without ActiveX - support
    System settings
    The system settings are valid for all clients and
    are defined by the administrator. To do this, the
    administrator profile must contain the
    authorization object 'S_ADMI_FCD' and
    the ID 'S_ADMI_FCD' with the 'F4MX' FIELD.

  • Search help needs more records than 500 or 5000

    I have a requirement to create search help on a non primary key field . So I need to work on search help exit to remove all the repeating and blank values . The problem I am facing rite now is that search help gets only 500 records by default and 5000 if we leave the restriction field blank . I need to get all the records which is approx more than 100000 and get only the unique values .
    Please let me know how I can increase the number of record more than 5000
    Regards,
    Tashi

    Hi Tashi,
    The following approach might work out in y our case by overwriting the data fetch functionality of the standard Search help
    1. Define internal table of desired structure, in the way you get the data from DB table
    2. use your custom function module / class method or select statement to get the desired data into the newly
        defined   internal table
    3. apply required sorting / filtering / formatting as per the requirements
    3. loop through the resultant data in the internal table and append the records to standard internal
        table / parameter  RECORD_TAB of the Search help exit. Please make a note that RECORD_TAB has the
        structure field STRING which needs to be populated with the correct offsetting..for example, if the first field
         is of 10 characters and second field of 5 characters, it should be populated in the following way
    loop at itab into ls_itab.
    wa_record-string+0 = ls_itab-field1.
    wa_record-string+10 = ls_itab-field2.
    wa_record-string+15 = ls_itab-field3.
    append wa_record to record_tab.
    clear wa_record.
    endloop.
    EXIT.
    Please try this approach and let us know.
    hope this helps.
    -Sajan Joseph.

  • 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

  • Search Help for Organization Unit ID..

    Hello Friends,
       Is there any search help which will display all the Organization Unit ID?..
    John.

    Hello Friends,
       When you goto Users_gen->create->copy user and employee... - > create users from existing SU01 users.. you can see the Organization unit id input field.. which has F4 help.. I need to have same F4 help in my custom program.. when i try to find the search help in debug mode i found that 'HRBAS00OBJID' but when i execute this search help in se11.. i dont find the same value which appear in the Users_gen. when i execute in se11 i can see more than 5000 records... appear but when execute users_gen i can see only 20 records.. i want to know is there any other search help will only display the Organiztion unit id only..
    John.

  • Extra fields in search help window in Record working time EHP5

    Hi Experts,
    Can you please let me know how to add additional fields/select options in search help window for Record Working Time ?
    My system is EHP5 NW 7.02
    I have added the custom search help for the respective filed in table " TCATS_SHLP_ITS".
    I can see this table is having entry for only 4 selection options and 6 value fields for search help display.
    But in my custom search help programme is having 8 select options(for advance search) and 10 display fields on the search window. It's working from CAT2 transaction but when I am running through webdynpro timesheet, I can only get 4 select options and 6 value fields.
    Please let me know how to make the other fields available.
    Thanks in advance.
    Sonia

    Hi Siddharth,
    Thanks for your response. In that modify possible entries screen (Details view) I can see the search help is only having 4 select options and 6 display fields.
    So as per my understanding max 6 display fields/4 select options can only be displayed on search window.
    My requirement is to display more fields on search help OVS window.
    Can you please suggest.
    Thanks ,
    Sonia

  • 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

  • Values from Search help not returned to UI

    Hi,
    For a field on Web UI, i have to open a popup which would be configured from a search help created in transaction SE11. The search help uses a Searchhelp Exit. On the UI, I am getting the popup but the value i select is not reflecting on the UI. The moment i select the value, the popup closes. The 'Get_XXX' method of the attribute also does not triggered. Following is the code which i am using to call the search help in the GET_V_XXX method of the attribute.
      DATA:
      ls_map    TYPE if_bsp_wd_valuehelp_f4descr=>gtype_param_mapping,
      lt_inmap  TYPE if_bsp_wd_valuehelp_f4descr=>gtype_param_mapping_tab,
      lt_outmap TYPE if_bsp_wd_valuehelp_f4descr=>gtype_param_mapping_tab.
      ls_map-context_attr = 'STRUCT.ZZSTORAGE_LOC'.
      ls_map-f4_attr      = 'STORAGE_LOC'.
    APPEND ls_map TO: lt_inmap, lt_outmap.
      CREATE OBJECT rv_valuehelp_descriptor
        TYPE
          cl_bsp_wd_valuehelp_f4descr
        EXPORTING
          iv_help_id                  = 'ZOFI_SHLP_STORAGE_LOC2'
          iv_help_id_kind             = if_bsp_wd_valuehelp_f4descr=>help_id_kind_comp
          iv_input_mapping            = lt_inmap
          iv_output_mapping           = lt_outmap.
    I have tried various approaches suggested in the forum, but none could solve the issue. Please guide.
    Thanks and Regards,
    Radhika

    Hi,
    The client wants to use the search help method only. i am using the following code to call the serach help.
    DATA:
      ls_map    TYPE if_bsp_wd_valuehelp_f4descr=>gtype_param_mapping,
      lt_inmap  TYPE if_bsp_wd_valuehelp_f4descr=>gtype_param_mapping_tab,
      lt_outmap TYPE if_bsp_wd_valuehelp_f4descr=>gtype_param_mapping_tab.
      CLEAR ls_map.
      ls_map-context_attr = 'EXT.ZZSTORAGE_LOC'.
      CONDENSE ls_map-context_attr no-GAPS.
      ls_map-f4_attr      = 'STORAGE_LOC'.
      APPEND ls_map TO: lt_inmap, lt_outmap.
      CLEAR ls_map.
      ls_map-context_attr = 'EXT.ZZPLANT'.
      CONDENSE ls_map-context_attr no-GAPS.
      ls_map-f4_attr      = 'PLANT'.
      APPEND ls_map TO: lt_inmap, lt_outmap.
      CREATE OBJECT rv_valuehelp_descriptor
        TYPE
          cl_bsp_wd_valuehelp_f4descr
        EXPORTING
          iv_help_id                  = 'ZOFI_SHLP_STORAGE_LOC2'
          iv_help_id_kind             = if_bsp_wd_valuehelp_f4descr=>help_id_kind_comp
          iv_input_mapping            = lt_inmap
          iv_output_mapping           = lt_outmap.
    this code is written in the GET_V of the field ZZSTORAGE_LOC.The ZZ Storage_Loc field is getting saved but the field ZZPLANT does not. Please provide your inputs.
    Thanks,
    Radhika

  • Search Help to display 2 different fields/values

    Hi Everyone,
    I am going to use a search help for a certain screen transaction using a search help. A certain input field should have an F4 function (using list box). The values to be displayed after F4 input should be the Business Object type and BP number. This input field is can display either of the two fields.
    How can I do this? Do I need to create a new search help for this? Business Object is from table SWOTIP field OBJTYPE and BP Number is form table BUT000 field PARTNER.
    Kindly help me on this.
    Thanks and regards,
    RE

    Hello Ashish,
    The input help should have two possible values. It may be the Org unit number or the Business Partner number.
    As for my experience in search help, the only thing I know about it is to set a reference db table then the field which is to be displayed during F4. For example, an input help requires a Plant number, the search help will have a reference table (selection method) T001W and a parameter of field WERKS.
    What if the input field can contain either an org unit number OR a business partner number, how should I create the search help? What should be the selection method (table name) to be filled? Is it the BUT000 (for bus partner) or HRP1001 (for org unit)?
    Thank you very much for your attention.
    Regards,
    RE

  • Records not displayed in the WGBEZ field in H_T023_MEPO search help.

    Hello Friends,
    I have created the search help exit , in that based on the LREF3 , we have to fetch the materail groups.
    1.I have written the code in the exit , in the search help exit tables parameter record_tab , the data is coming correctly
    but when we run  search help, the description field is not getting displayed.
    I have shift 2-3 places left side as well but the description is not displayed correctly.
    So how can we get the description field filled.
    2. We want that the LREF3 field should come in the selection screen of the dialog box, so that user can enter the values in it.(dialog with value restriction) so i have added LREF3 field in the search help parameters but i want that
    this field should not be displayed in the results of search help . Only materail group and its description gets displayed.
    So can we achieve the same.
    Thanks to provide answers for my above two questions.

    Hi
    Please go through the related pointers ->
    The OSS note 672960 has already indicated you need to use BADI to address it.
    For Search criteria
    You can also use user-defined fields as search criteria. To do this, you have to set fields XINPUT and XDISPLAY to 'X' in table ET_FIELDS for the fields you want to use in BADI BBP_CUF_BADI_2 in method MODIFY_SCREEN. The fields defined this way are displayed if you choose the 'Extended search' link.
    Re: Custom field in Create Bid Invitation..
    Re: Search Help for Purchasing Group..
    Re: urgent help request - How to add custom fields to  header BID.
    Re: New Screen with table control information in Process Bid Invitation
    Do let me know.
    Regards
    - Atul

  • Multiple search helps in ABAP Adobe interactive forms not working....

    Hello,
    I am working on my first interactive form. I have a couple of fields to which I have attached a search help. However, I am able to use the search help for only one field in a session. If I use the search help on one field then I am unable to use it on another field which uses the search help.
    Can some one help? I am new to interactive forms and this is my first form.
    I appreciate your help in advance.
    Thank you,
    Leena

    Hi Leena,
    Are the Data dictionary fields which you are using contains value range. Because i am only getting value help only for the fields for which there is value range defined in the dictionary. The problem is only for the fields for which there is no value range defined. If you have solution to this problem I will definitely award points to you. But in your thread for me its not possible to reward points, so you can answer the following thread:
    [How to get Value help in Adobe forms;
    Will reward points if found your answer helpful.

  • Search help in selection screens for interactive report

    A search help can only be assigned to DB table.
    So my doubt is can it also be used for seletion screens created for an interactive report?
    If yes what is the procedure.. Please give me one example at least...
    waiting for your valuable suggestions.....
    Thanks,
    regards,
    Chinmay

    Hi Chinmay,
    I suppose your requirement is to give search help to selection screen elements.
    Here is the code.
    REPORT  ZSHAIL_F4HELP                           .
    parameters: name(10) type c .
    TYPES: BEGIN OF VALUES,
             CARRID TYPE SPFLI-CARRID,
             CONNID TYPE SPFLI-CONNID,
           END OF VALUES.
    dATA: PROGNAME LIKE SY-REPID,
          DYNNUM   LIKE SY-DYNNR,
          DYNPRO_VALUES TYPE TABLE OF DYNPREAD,
          FIELD_VALUE LIKE LINE OF DYNPRO_VALUES,
          VALUES_TAB TYPE TABLE OF VALUES.
    at selection-screen on value-request for name.
    CALL FUNCTION 'F4IF_FIELD_VALUE_REQUEST'
      EXPORTING
        tabname                   = 'DEMOF4HELP'
        fieldname                 = 'CARRIER1'
      SEARCHHELP                = ' '
      SHLPPARAM                 = ' '
       DYNPPROG                  = PROGNAME
       DYNPNR                    = DYNNUM
       DYNPROFIELD               = 'CARRIER'
      STEPL                     = 0
      VALUE                     = ' '
      MULTIPLE_CHOICE           = ' '
      DISPLAY                   = ' '
      SUPPRESS_RECORDLIST       = ' '
      CALLBACK_PROGRAM          = ' '
      CALLBACK_FORM             = ' '
      SELECTION_SCREEN          = ' '
    IMPORTING
      USER_RESET                =
    TABLES
      RETURN_TAB                =
    EXCEPTIONS
       FIELD_NOT_FOUND           = 1
       NO_HELP_FOR_FIELD         = 2
       INCONSISTENT_HELP         = 3
       NO_VALUES_FOUND           = 4
       OTHERS                    = 5
    IF sy-subrc <> 0.
    MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
            WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
    ENDIF.
    AT SELECTION-SCREEN OUTPUT.
    PROGNAME = SY-REPID.
      DYNNUM   = SY-DYNNR.
      CLEAR: FIELD_VALUE, DYNPRO_VALUES.
      FIELD_VALUE-FIELDNAME = 'CARRIER'.
      APPEND FIELD_VALUE TO DYNPRO_VALUES.
    I hope your query is solved.
    If so,please award points.
    Regards,
    Sylendra.

  • Hi how to attach search help to a field

    hi all,
    how to attach search help to a field.

    hi
    <b>Attaching a search help to a field</b>
    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.
    <b>Attaching a search help to a table field</b>
    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.
    <b>Attaching a search help to a data element</b>
    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.
    <b>Attaching a search help to a screen element</b>
    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.
    <b>IF YOU WANT TO ATTCH A SERACH HELP TO THE SCREEN FILED THIS IS THE CODE</b>
    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.
    <b>REWARD IF USEFULL</b>

Maybe you are looking for