Search Help attached to Data Element Question

Hello! Hopefully this is a simple question to answer. I have looked online but cannot find exactly what I need.
We currently have a search help attached to a data element. The search help is a custom search help. It does work so when you are in the screen it will show you options to pick from for that field. However, the field also allows for free-form text so the user can type in whatever and the screen will take it.
Is there a way through the data element or search help to make it so the user is restricted to only what is in the search help and cannot just enter whatever?
Thanks!!

For restricting values You can use the at selection screen event  on that field.
The search help field values will be there in a table .
So what ever values are there in the table for that particular field , only those values will come in F4 also ..
If it not maintained then issue an appropriate error message.
at-selection screen on p_field.
selct single  field from table into v_value.
if sy-subrc <> 0.
message ""Error message.
Endif.
Regards
Mishra

Similar Messages

  • Search Help for custom data element

    Hi experts,
      I have a small question regarding accessing data on different clients.
      Can I have an abap program where I can make reference to data /tables in different client AAA, assuming the system (AAA) with data is logically connected to the client that has the ABAP Program ?
    thanks,
    Rajesh

    Thanks Ankur and Rich,
       I would like to clarify your responses.
       I have a custom field my material in SAP xRPM system( different client from R/3).  As per your previous replies, I understand it is possible to have search help for material in xRPM and validate the data with material in R/3. Is this correct? Do I need to maintain all the data in the xRPM ?
    thanks again,
    Rajesh

  • Search help attachement

    Hi,
    How i can attach a search help to a parameter or select option field in selection screen?.
    Regards.

    Hi Brinda,
    In my previous program, the second parameter doesn't have a search help.When any value is selected from the search help of first parameter  , the corresponding value of second parameter will be displayed.
    Just check this program for understanding more about search helps.In this program both the fields will have search helps.
    REPORT  ZSHAIL_F4HELP                           .
    DATA: BEGIN OF VALUES,
          MATNR TYPE MARA-MATNR,
          MTART TYPE MARA-MTART,
          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 LIKE TABLE OF VALUES WITH HEADER LINE.
    SELECTION-SCREEN BEGIN OF BLOCK B1 WITH FRAME TITLE TEXT-008.
    PARAMETERS : MATNR_N LIKE MARA-MATNR OBLIGATORY,
                 MTART_N LIKE MARA-MTART.
    SELECTION-SCREEN END OF BLOCK B1.
    AT SELECTION-SCREEN ON VALUE-REQUEST FOR MATNR_N.
    CALL FUNCTION 'F4IF_FIELD_VALUE_REQUEST'
      EXPORTING
        tabname                   = 'MARA'
        fieldname                 = 'MATNR'
      SEARCHHELP                = ' '
      SHLPPARAM                 = ' '
       DYNPPROG                  = PROGNAME
       DYNPNR                    = DYNNUM
       DYNPROFIELD               = 'MATNR_N'
      STEPL                     = 0
      VALUE                     = ' '
      MULTIPLE_CHOICE           = ' '
      DISPLAY                   = ' '
      SUPPRESS_RECORDLIST       = ' '
      CALLBACK_PROGRAM          = ' '
      CALLBACK_FORM             = ' '
      SELECTION_SCREEN          = ' '
    IMPORTING
      USER_RESET                =
    TABLES
      RETURN_TAB                = VALUES_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 = 'MATNR_N'.
      APPEND FIELD_VALUE TO DYNPRO_VALUES.
    AT SELECTION-SCREEN ON VALUE-REQUEST FOR MTART_N.
    CALL FUNCTION 'DYNP_VALUES_READ'
      EXPORTING
        dyname                         = PROGNAME
        dynumb                         = DYNNUM
       TRANSLATE_TO_UPPER             = 'X'
      REQUEST                        = ' '
      PERFORM_CONVERSION_EXITS       = ' '
      PERFORM_INPUT_CONVERSION       = ' '
      DETERMINE_LOOP_INDEX           = ' '
      tables
        dynpfields                     = dynpro_values
    EXCEPTIONS
       INVALID_ABAPWORKAREA           = 1
       INVALID_DYNPROFIELD            = 2
       INVALID_DYNPRONAME             = 3
       INVALID_DYNPRONUMMER           = 4
       INVALID_REQUEST                = 5
       NO_FIELDDESCRIPTION            = 6
       INVALID_PARAMETER              = 7
       UNDEFIND_ERROR                 = 8
       DOUBLE_CONVERSION              = 9
       STEPL_NOT_FOUND                = 10
       OTHERS                         = 11
    IF sy-subrc <> 0.
    MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
            WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
    ENDIF.
    READ TABLE DYNPRO_VALUES INDEX 1 INTO FIELD_VALUE.
    select matnr mtart from mara into table values_tab where matnr = FIELD_VALUE-FIELDVALUE.
    CALL FUNCTION 'F4IF_INT_TABLE_VALUE_REQUEST'
      EXPORTING
      DDIC_STRUCTURE         = ' '
        retfield               = 'MTART'
      PVALKEY                = ' '
       DYNPPROG               = PROGNAME
       DYNPNR                 = DYNNUM
       DYNPROFIELD            = 'MTART_N'
      STEPL                  = 0
      WINDOW_TITLE           =
      VALUE                  = ' '
       VALUE_ORG              = 'S'
      MULTIPLE_CHOICE        = ' '
      DISPLAY                = ' '
      CALLBACK_PROGRAM       = ' '
      CALLBACK_FORM          = ' '
      MARK_TAB               =
    IMPORTING
      USER_RESET             =
      tables
        value_tab              = VALUES_TAB
      FIELD_TAB              =
      RETURN_TAB             =
      DYNPFLD_MAPPING        =
    EXCEPTIONS
       PARAMETER_ERROR        = 1
       NO_VALUES_FOUND        = 2
       OTHERS                 = 3
    IF sy-subrc <> 0.
    MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
            WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
    ENDIF.
    Regards,
    Sylendra.

  • Search Help Attachment

    Hai dear all,
                      Iam Balakumar.
                      Do anyone know how to attach search help in ITS Template,
    pls Provide me with sample coding.Can a be a Table control be simulated in ITS HTML Template,I can pls provide me sample coding

    what do you want to display through search help as the XREF2_HD is 20 char field

  • TEM - Data Element Question

    Pl suggest Table-Field for the following Data Elements in TEM
    Location where Event held
    Schedule of the Event

    PL check this <a href="https://forums.sdn.sap.com/click.jspa?searchID=3972037&messageID=3775117">Thread</a>.
    ~Suresh

  • OBIEE  Apps data element question?

    Please any body explain me, how we can find the right data is coming from the source.
    Through Informatica in the OBIEE Apps
    Thanks in Advance
    Praveen

    You can install the "data lineage" option, but it needs a lot of effort.
    In Informatica, there are system table that gives you information about metadata, so you can find the "link" between a target table/column and source(s) table/column(s).
    Then, in OBIEE, you can do the same for the link between presentation column and physical column.
    Since physical column in OBIEE are your target column in Informatica, you can do the link between everything.
    You have to put that into one big (more more) table, integrate that into OBIEE and create report that, for a presentation table/column, will give you the source table/column. If you work with the catalog manager, you can even do the same with the web catalog.
    But Oracle has already simplified the job by giving you RPD and documentation about that.
    The first thing to do is to search for "data lineage" in BI Apps. Ask your Oracle contact for more information, they're aware about that because it's a frequent need in BI projects.

  • Search Help In ALV Grid

    What is shortest way to attach particular Search Help in ALV grid using OOPS ?

    Thanks Gurpreet,
    Through search helps attached to data element it is possible but is there any other way to attach searchhelp differet from from the search help attached to the data element ? The new search-elp is not customized search help as given in the above threads ?
    Eg. - If I want to attach MAT2 to a field named MATNR in the table instead of the MAT1 which is standard.
    Thanks in advance

  • Search help enhancement - VA01

    Hello,
    I am trying to enhance standard search help on material field(RV45A-MABNR) on VA01 screen with my custom search help. Can someone please suggest which search help is being used by this material field?
    Thanks,

    When you go to display the structure RV45A in se11 and goto field mabnr and double click it , you can find
    "explicit search help attachment to data element" and not as "explicit search help attachment to data field"
    which is the case for  RMXTT_TRIAL_HD-PRODUCT
    and also when you click on the search help for field at the bottom , you can see " no search help for field RV45A-MABNR".

  • 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>

  • A question about search help and input help,PLZ take a look at it.

    hi everyone,
    i want to know the difference between search hlep and inpu help
    can anyone tell me about that?
    thanks

    HI
    BOTH ARE SAME
    you can define F4 help in 2 ways
    in SE11 or in the report program
    IN SE11
    Attaching a search help to a table field
    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.
    Attaching a search help to a data element
    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.
    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 REPORT PROGRAM
    in this way we declare in report program
    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 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.
    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.
    Check this out
    http://www.sap-img.com/abap/value-request-for-parameter.htm
    ******************************8
    sample program
    report zrich_0001 .
    data: begin of ihelp occurs 0,
    field type char10,
    ftext type char50,
    end of ihelp.
    data: a_field(20) type c.
    select-options s_field for a_field.
    initialization.
    ihelp-field = 'A'.
    ihelp-ftext = 'Description A'.
    append ihelp.
    ihelp-field = 'B'.
    ihelp-ftext = 'Description B'.
    append ihelp.
    ihelp-field = 'C'.
    ihelp-ftext = 'Description C'.
    append ihelp.
    at selection-screen on value-request for s_field-low.
    call function 'F4IF_INT_TABLE_VALUE_REQUEST'
    exporting
    retfield = 'FIELD'
    dynprofield = 'S_FIELD'
    dynpprog = sy-cprog
    dynpnr = sy-dynnr
    value_org = 'S'
    tables
    value_tab = ihelp.
    start-of-selection.
    one more program....
    REPORT ZHELP .
    TABLES : MARA.
    SELECTION-SCREEN BEGIN OF BLOCK B1 WITH FRAME TITLE TEXT-001.
    PARAMETERS : P_MATNR(10) TYPE C.
    SELECTION-SCREEN END OF BLOCK B1.
    DATA : BEGIN OF ITAB OCCURS 0,
    MATNR TYPE MATNR,
    END OF ITAB.
    AT SELECTION-SCREEN ON VALUE-REQUEST FOR P_MATNR.
    SELECT MATNR
    FROM MARA
    INTO TABLE ITAB
    UP TO 10 ROWS.
    CALL FUNCTION 'F4IF_INT_TABLE_VALUE_REQUEST'
    EXPORTING
    RETFIELD = 'MATERIAL NUMBER'
    DYNPPROG = SY-REPID
    DYNPNR = SY-DYNNR
    DYNPROFIELD = 'P_MATNR'
    VALUE_ORG = 'S'
    TABLES
    VALUE_TAB = ITAB
    EXCEPTIONS
    PARAMETER_ERROR = 1
    NO_VALUES_FOUND = 2
    OTHERS = 3.
    Create it from SE11.
    enter search help
    and create elementary
    enter description and below Table name
    and the fields
    see the doc
    1) 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).
    2) Collective search helps combine several elementary search helps. A collective search help thus can offer several alternative search paths.
    3)An elementary search help defines the standard flow of an input help.
    4) A collective search help combines several elementary search helps. The user can thus choose one of several alternative search paths with a collective search help.
    5)A collective search help comprises several elementary search helps. It combines all the search paths that are meaningful for a field.
    6)Both elementary search helps and other search helps can be included in a collective search help. If other collective search helps are contained in a collective search help, they are expanded to the level of the elementary search helps when the input help is called.
    http://help.sap.com/saphelp_nw04/helpdata/en/cf/21ee38446011d189700000e8322d00/content.htm
    http://help.sap.com/saphelp_nw04/helpdata/en/cf/21ee45446011d189700000e8322d00/content.htm
    pls go through this for search help creation
    http://help.sap.com/saphelp_nw2004s/helpdata/en/41/f6b237fec48c67e10000009b38f8cf/content.htm

  • Searc help in entry help/Check tab vs Search help in Further Char-Data elem

    Folks,
    I have a screen field which is linked to a structure.When I look at that structure's entry help/check tab in se11 this field is having a collective search help.Now I want this to be replaced by a Z search help.
    If my understanding is right I need access key for this structure so that I can link the z search help in entry help/check tab against this field.
    My query is whic is the right way
    1.Linking the z search help in the entry help/check tab against that field in the structure at SE11 level
        or
        Linking the Z search help in Further Characterisitics tab of the data element used by this field.
    Either way the search help will be reflected at all the places wherever this field is available in the screen.Am I right ?
    or
    2. Linking the search help to a data element is different from linking the seach help to the field in that structure in entry help/check tab ? If they differ how do they differ.Kindly let me know
    Thanks,
    K.Kiran.

    Not true.
    Search help assigned at data element level is independent of that assigned at structure level, and the latter has higher priority. Please read "Input Help Hierarchy in the ABAP Dictionary":
    http://help.sap.com/saphelp_470/helpdata/en/9f/dbaa5435c111d1829f0000e829fbfe/content.htm
    The structure level assignment can (and generally is) linked to more than one field, not only the one that triggers the search help. That depends on the search help importing and exporting parameters. The data element assignment can only affect the field in which it is used.
    Nevertheless, even the search help defined at structure level could be overriden in the program (e.g. PARAMETERS...MATCHCODE OBJECT, AT SELECTION-SCREEN ON VALUE-REQUEST, PROCESS ON VALUE-REQUEST, etc). If that is not your case, it's the structure assignment that you want to change (have into account that it will affect any other dynpros which use that structure).

  • Dropdown box not showing up for field w/attached search help

    Hi.  I've created a search help for a data element and I know that the search help is working on the selection screen. 
    The search help values come up if I hit F4 but when I click into the field on the selection screen no drop-down box appears to the right of it (so the users don't know that a search help is even available).
    Has anyone seen this before?

    Hi Rich,
    I tried closing all sessions and re-logging in.  That did not work.
    I also tried regenerating the program.  That did not work.  Very odd.
    F4 works on the field, just no dropdown box! 
    We're running 640.

  • 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 Field

    Hi,
    I have included a parameter(CHAR 50), say field X in a search help for field Y (Y shud be selected based on X).
    I have attached a search help to X's data element, for providing a drop down.This search help's selection method is a text table for X.
    When I select a value from the dropdown for X in the search help, only the first 19 characters are passed to the search help's screen field.
    Is there any restriction on the length of the value that can be passed to a search help selection?
    Pls let me know.
    Thanks in advance,
    Arthi.

    Hi
    Herewith i am giving some points about Search Help and the Data Element.
    ATTACHING SEARCH HELP TO A DATA ELEMENT ->
    The search help can be used by all screen fields that refer to the  data element. All the fields with the same meaning therefore have an identical input help.
    When the search help is attached to a data element, an export parameter of the search help must be assigned to the data element. If the user selects a line of the hit list in the input help, the contents of this parameter are returned to the corresponding screen field. It is not possible to return several values when the search help is attached to a data element.
    If the parameter assigned to the data element is also an import parameter of the search help, the contents of the search field are used for the value selection if they contain a pattern. Other import parameters of the search field cannot be taken into consideration when the search help is attached to a data element.
    Assign a search help=> You can assign the data element a  search help. This search help is offered on all the screen fields referring to this data element when the input help (F4 help) is called . To assign the search help, you must specify its Name in the data element maintenance screen and an export parameter of the search help in the Parameter field.
    Search Helps =>
    The input help (F4 help) is a standard function of the R/3 System. The user can display the list of all possible input values for a screen field with
    There are two types of search help:
    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 helps combine several elementary search helps. A collective search help thus can offer several alternative search paths.
    Screen Display =>
    I think you r talking about the 255 character that a screen lengh can take,but more than 255 character also we can dispaly in a screen.
    go through this link
    http://www.allsaplinks.com/files/using_table_in_screen.pdf
    I hope this will help you to solve your problem.
    Thanks
    Mrutyunjaya Tripathy

  • Search Help Within Search help

    Hi experts!!
    How can i assign a search help to a field of another elementary search help from SE11???
    I tried to create a new data element but did not work...

    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.
    1)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.
    2)Attach the search help to the table field
    3)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.
    Reward if usefull

Maybe you are looking for

  • Error while executing a JDBC to Idoc scenario : No standard agreement found

    Hello SAP PI Gurus,  I am having a JDBC to idoc Scenario .And the interface is running at 10 min of duration.  <SAP:AdditionalText>No standard agreement found for , BS_EXT_CTBSREPDB, , BS_ERPQAS_QE1_320, http://XYZ.com/FI/FI_FI_01/Charges, FIDCC2</SA

  • Table to see PIR

    Hi, Can anyone tell the table or tables where i can see How  many times PIR in MD61/MD62 has been changed &  the PIRs deleted from the MD61/MD62 where do all these records get stored. I just want to know weather any PIR has been entered last year for

  • An incorrect default value of account assignment group in sales order

    I created a new sales order; however, the default value for account assignment group is not the same value maintained in customer master. Any idea how could this happen?

  • IP address range of Microsoft Location Services API

    Hi, I am developing a LOB windows 8.1 application. The windows 8 tablet device we are using needs to be locked down by IP address to the specific services that the application will use. I have not been able to find the IP address range for the Micros

  • Linking 3rd Party Vendor invoice to customer invoice

    Hi Guys, We have a requirement in 3rd party order processing. Client wants us to link the vendor invoice to the customer invoice. For example, in a 3rd party order, the customers orders 100 qty of MATERIAL A. Then a PR, PO is generated for 100 qty. V