Manual Search help(F4)

hi
I have a selection screen on which there are two criterias one for the lot number the second is for the result.when the user press the F4 button for the lot number the search help apears and he selects the required lot number from the list.
then he goes to the second criteria to select the results when he press the F4 button to select the results for the selected lot number(which is selected in the first criteria).
my requirement is that when user press F4 button on the result criteria the selected lot number should be filled automatically in the result F4 search help.
is it possible if yes then plz let me know how can i do this.
Regards

Hi,
Do the below:
1) Fetch the data from the table(where you have lot nos) using SELECT statement
2) Process the data above and fill in the internal table above based on conditions if any
3) Call the function modules in the sequence :   'F4IF_INT_TABLE_VALUE_REQUEST'', 'DYNP_VALUES_UPDATE'.
Below is some sample code that helps you
*&      Form  F4_TRANSFER
   F4 help for the field TRANSFER ID
FORM f4_transfer .
Local data declarations
  DATA : lt_transfer TYPE ty_t_transfer.
  CONSTANTS: lc_retfield1 TYPE dfies-fieldname VALUE 'TRANSFERID',
             lc_helpfield TYPE help_info-dynprofld VALUE 'ZGLT_BAL_TRF-TRANSFERID'.
Fetch the transfer id
  SELECT transferid
  FROM zglt_bal_trf
  INTO TABLE lt_transfer.
  IF sy-subrc EQ 0.
  Call the FM to display the F4 help values
    PERFORM f4_helpval_desc TABLES lt_transfer USING lc_retfield1 lc_helpfield.
  ENDIF.
ENDFORM.                    " F4_TRANSFER
*&      Form  F4_HELPVAL_DESC
   F4 help for the field TRANSFER ID
FORM f4_helpval_desc  TABLES   values_tab     TYPE table
                       USING   sp_retfield    TYPE dfies-fieldname
                               sp_dynprofield TYPE help_info-dynprofld.
Local data declarations
  CONSTANTS : lc_s  TYPE ddbool_d VALUE 'S'.
  DATA :      lt_return_tab    TYPE TABLE OF ddshretval, " Return value
              lt_dynpro_values TYPE TABLE OF dynpread,   " Screen details
              ls_field_value   TYPE dynpread,
              ls_return        TYPE ddshretval.
FM for F4 help display values
  CALL FUNCTION 'F4IF_INT_TABLE_VALUE_REQUEST'
    EXPORTING
      retfield        = sp_retfield
      dynpprog        = sy-cprog
      dynpnr          = sy-dynnr
      dynprofield     = sp_dynprofield
      value_org       = lc_s
    TABLES
      value_tab       = values_tab
      return_tab      = lt_return_tab
    EXCEPTIONS
      parameter_error = 1
      no_values_found = 2
      OTHERS          = 3.
  IF sy-subrc EQ 0.
Append the data to dynpro table.
FM to Update the Fields
  CALL FUNCTION 'DYNP_VALUES_UPDATE'
    EXPORTING
      dyname     = sy-cprog
      dynumb     = sy-dynnr
    TABLES
      dynpfields = lt_dynpro_values.
ENDIF,
ENDFORM.                    " F4_HELPVAL_DESC
Regards
Shiva

Similar Messages

  • Help regarding search help

    hi,
    i want to know the functionality with example on "search help".
    how r they useful?....how r they created??...and how to use them in dialog program??
    thanks

    Hi Kunal,
    There are 3 ways:
    1)In the PAI of the screen, add a module Process on value request. For example:
    PROCESS AFTER INPUT.
    MODULE USER_COMMAND_100.
    PROCESS ON VALUE-REQUEST.
    FIELD field_name MODULE value_request_for_field_name.
    *field_name is the field for which you require search help.
    In the Module value_request_for_field_name call this function 'F4IF_INT_TABLE_VALUE_REQUEST'.
    2)The above procedure can be used if the field you have defined doesnt have an existing search help.If it already has search help and the field in the screen is taken from the dictionary,then in the attributes,u can check from from dictionary under the dictionary tab.
    3)A manual search help can also be created in the se11 transaction by clicking on the search help radio button and giving the table and field name for which search help is required.
    Creating Elementary Search Helps
    Procedure
    In the initial screen of the ABAP Dictionary, select object class Search help, enter the name of the search help and choose Create.
    A dialog box appears in which you must select the type of search help.
    Select Elementary search help and choose .
    The maintenance screen for elementary search helps appears.
    Enter an explanatory text in the field Short text.
    You can for example find the search help at a later time using this short text.
    In the Definition tab page enter the selection method of the search help.
    You can enter the name of a table or a view (database view, projection view or help view) here. If you enter a table that has a text table, the name of the text table is automatically entered in the corresponding field.
    Using the input help (F4 help), select fields of the selection method as parameter in the Search help parameter area. Select the fields that should be used in the dialog box for value selection or in the hit list.
    If the selection method is a table that has a text table, both the fields of the table and the fields of the text table are offered in the input help.
    The data element of the parameter is automatically copied from the selection method. The data element defines the output attributes and the F1 help of the parameter in the hit list and in the dialog box for value selection.
    You can assign the parameter another data element. To do so, select the Mod flag. The Data element field is now ready for input. Then select a data element with the input help (F4 help). Only data elements whose data type, length and number of decimal places is the same as those of the previous data element can be assigned.
    This removes the link between the data element of the search help parameter and the data element of the selection method field having the same name. If you cancel the Mod flag, the data element of the assigned table field is used again.
    Define the attributes of the search help parameters.
    Select the IMP flag if it is an import parameter. Select the EXP flag if it is an export parameter.
    You can define the dialog for the input help with the fields LPos, SPos and SDis. Enter the parameter position in the hit list in LPos. If you enter nothing or the value 0 here, the parameter is not displayed in the hit list.
    Enter the parameter position in the dialog box for value selection in SPos. If you enter nothing or the value 0 here, the parameter is not displayed in the dialog box for value selection.
    Set the SDis flag if the parameter should be a pure display field in the dialog box for value selection. The user is thus informed that the contents of the parameter restrict the value, but he cannot change this restriction. This makes sense for example when the parameter is an import parameter or if it has a default value.
    You can assign the parameter a default value in the Default value field.
    Select the dialog type of the search help.
    The dialog type defines how the hit list is displayed in the input help.
    Save your entries.
    A dialog box appears in which you have to assign the search help a development class.
    Choose .
    Do not forget to link the search help to a screen field. The search help attachment is not part of the search help definition; it is part of the object definition to which the search help is attached.
    Result
    The search help is activated. You can find information about the activation flow in the activation log, which you can display with Utilities ® Activation log. If errors occurred during activation, the activation log is automatically displayed.
    Please check this link on how to create search help.
    http://www.sapdevelopment.co.uk/dictionary/shelp/shelp_basic.htm
    1) after creation of search help, you can assign this to database field in change mode of table and double clicking of the field name.
    2) in screen field, double click to see the attributes and give your search help there.
    Refer this link
    http://help.sap.com/saphelp_erp2005/helpdata/en/cf/21ee93446011d189700000e8322d00/frameset.htm
    Hope this resolves your query.
    Reward all the helpful answers.
    Regards

  • Attachig a search help to screen filed

    hi
    I want to attach sarch help to screen field .
    i am not able to make out where i have to attach . do i need to go in attributes of the field .
    plz provide ur inputs .
    Thanks ,
    abhishek .

    Hello Abhishek,
    1)In the PAI of the screen, add a module Process on value request.For example:
    PROCESS AFTER INPUT.
    MODULE USER_COMMAND_100.
    PROCESS ON VALUE-REQUEST.
    FIELD field_name MODULE value_request_for_field_name.
    *field_name is the field for which you require search help.
    In the Module value_request_for_field_name call this function 'F4IF_INT_TABLE_VALUE_REQUEST'.
    2)The above procedure can be used if the field you have defined doesnt have an existing search help.If it already has search help and the field in the screen is taken from the dictionary,then in the attributes,u can check from from dictionary under the dictionary tab.
    3)A manual search help can also be created in the se11 transaction by clicking on the search help radio button and giving the table and field name for which search help is required.
    Regards,
    Beejal
    **Reward if answer is helpful

  • The Previous Search help value

    PARAMETERS:LOTNUM TYPE QPLOS OBLIGATORY,
               STARTDAT TYPE QALS-PASTRTERM OBLIGATORY.
    SELECT-OPTIONS: FTEST FOR QAMV-VERWMERKM Matchcode Object ZLOT_HELP.
    Please answer accroding and using the above parameters and select-options.
      My Requirement is that the when user selects the LOTNUM value by pressing F4.
    then he wants to select the value of FTEST when he press the F4 button on FTEST then
    the manual search help ZLOT_HELP will popups I need the Previous Selected LOTNUM value
    to be displayed or selected in the manul Search Help F4 of FTEST.
    Please If possible send me the CODE using the abov parameters and select option.
    and guide me except the option AT SELECTION-SCREEN ON VALUE-REQUEST FOR FTEST.
    cos this option gives me error due to I m using manual search help and this option can be used only wiht
    standard helps.
    Regards.

    try FM DYNP_VALUES_READ to get entered values of LOTNUM-->check its documentation for its usage.
    F4IF_START_VALUE_REQUEST-->u can use this FM to get values frm ur custom search help .
    regards
    Prabhu

  • Attach search help to standard screen

    Hi Gurus,
    I have to populate order quantity KWMENG in screen subscreen 4900 of VA01 ( Create Sales Order) from a ztable based on customer and date.
    I have tried customer-exits ..<b>There exists none</b> satisfying this req. Could anyone pls tell how I can go about this now?
    I believe , one way is to create a search help attaching to the screen-field . Can anyone help what is the process ? Has anyone done this earlier -<b>attaching search help to standard screen</b>
    Rewards for helpful answers are sure!!
    Regards,
    Shweta

    Hi Shweta,
    Check this matter.
    There are 3 ways:
    1)In the PAI of the screen, add a module Process on value request.For example:
    PROCESS AFTER INPUT.
    MODULE USER_COMMAND_100.
    PROCESS ON VALUE-REQUEST.
    FIELD field_name MODULE value_request_for_field_name.
    *field_name is the field for which you require search help.
    In the Module value_request_for_field_name call this function 'F4IF_INT_TABLE_VALUE_REQUEST'.
    2)The above procedure can be used if the field you have defined doesnt have an existing search help.If it already has search help and the field in the screen is taken from the dictionary,then in the attributes,u can check from from dictionary under the dictionary tab.
    3)A manual search help can also be created in the se11 transaction by clicking on the search help radio button and giving the table and field name for which search help is required.
    Hope this resolves your query.
    Reward all the helpful answers.
    Regards

  • Creation of search help manually fro select-options

    hi friends i got a requirement for creating the search helps manually for select-options.
    but i am facing a progbalem.
    i am attaching a sample code for what i have written for select-opions low of which when i am pressing f4 button i am getting list of data but when i am selecting that particular it is not withstading on the screen...kindly help in this regard very urguent..plz...all answers are rewarded..
    tableS: kna1.
    datA: BEGIN OF ITAB OCCURS 1,
        KUNNR TYPE KNA1-KUNNR,
        END OF ITAB.
    data: kunnr type kunnr.
    select-options: cust for kunnr .
    at selection-screen on value-request for cust-low.
    select kunnr from kna1 into table itab .
    CALL FUNCTION 'F4IF_INT_TABLE_VALUE_REQUEST'
      EXPORTING
    *   DDIC_STRUCTURE      = ''
        RETFIELD               = 'CUST-LOW'
    *   PVALKEY                = ' '
    *   DYNPPROG               = ' '
    *   DYNPNR                 = ' '
    *   DYNPROFIELD            = ''
    *   STEPL                  = 0
    *   WINDOW_TITLE           =
       VALUE                  = 'CUST-LOW'
       VALUE_ORG              = 'S'
    *   MULTIPLE_CHOICE        = ' '
    *   DISPLAY                = 'X'
       CALLBACK_PROGRAM       = SY-CPROG
    *   CALLBACK_FORM          = ' '
    *   MARK_TAB               =
    * IMPORTING
    *   USER_RESET             =
      TABLES
        VALUE_TAB              = ITAB
    *   FIELD_TAB              =
    *   RETURN_TAB             =
    *   DYNPFLD_MAPPING        =
    * EXCEPTIONS
    *   PARAMETER_ERROR        = 1
    *   NO_VALUES_FOUND        = 2
    *   OTHERS                 = 3
    IF SY-SUBRC <> 0.
    * MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
    *         WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
    ENDIF.

    Hai  Saslove,
    I think Problem Lies In this Area When U r Creating   Search Helps.
    Import and Export Parameters
    When an input help is called, the entries that the user already made in the input template are taken into consideration. For example, if a user calls the input help for the flight number and already specified the carrier, of course only the numbers of flights of this carrier should be offered.
    On the other hand, if the user selects one row of the hit list, more than one field of the input template might have to be filled with data from the selected row of the hit list. For example, if the flight number is obtained from the hit list, the city of departure and the destination should also be returned in the screen template.
    The interface of a search help defines the context data that can be used in the input help and the data that can be returned in the input template.
    A parameter of a search help can be classified as:
    Import parameters: Parameters with which context information from the processed input template (screen) may be copied to the help process.
    Export parameters: Parameters with which values from the hit list may be returned to the input template.
    A parameter can simultaneously be an input and an export parameter. A search help can also contain parameters that are neither import nor export parameters. Such parameters could be required for the internal input help process, for example.
    When you attach a search help, you must define where the import parameters of the search help get their values from and the fields in which the contents of the export parameters are returned. See also Value Transport for Input Helps.
    Regards.
    Eshwar.

  • WAD Manual Planning search help

    Dear all,
    i have a manual planning scenario, i am entering functional location and quantity.
    When i open up search help for funct.loc, i only want to see the key and text for the funct.loc.
    Is it possible to modify that search help? or make it shows only key and text
    Thanks
    jmq

    thats correct,
    however i have created my infoobject reference to 0funct_loc, therefore it does not give me option to modify my custom object.
    it shows attributes of infoobject in search help.
    Thanks
    jmq

  • Adding a new field to the search help exit

    Hi friends,
    adding a new field to the search help exit. How does it work ?
    Thanks in advace
    Ilhan

    The search help exit allows you to modify functionality of search help. If you add a new field to the
    parameter list that is not contained on the selection method you can manually populate it within the search
    help exit.
    This  would be performed within the u2018STEP DISPu2019 section. Once within this section all search help
    data has been retrieved and is stored in table RECORD_TAB (record_tab-string) as one long string value.
    Therefore you need to read table SHLP in-order to locate position of value within string.
    Example:
    To find position of personnel number (PERNR) within elemenory search
    help M_PREMN you would use the following code:
    Loop at record_tab.
         read table shlp-fielddescr into wa_shlp
                                       with key tabname   = 'M_PREMN'
                                                fieldname = 'PERNR'.
    You could then use this information in the following way, for
    example, to find a persons organisation unit:
          select  orgeh endda
            up to 1 rows
            from pa0001
            into (ld_orgeh,ld_endda)
           where pernr eq record_tab-string+wa_shlp-offset(8)
                                                      u201Cpernr length is 8
           order by endda descending.
          endselect.
          select single orgtx
            from t527x
            into ld_orgtxt
           where orgeh eq ld_orgeh and
                 sprsl eq sy-langu and
               ( endda ge sy-datum and
                 begda le sy-datum ).
    If you have added a new field to the end of the parameters list
    the next step is to populate it by adding this data to the end of
    the record_tab string:
      concatenate record_tab-string ld_orgtxt into record_tab-string.
      modify record_tab.
    endloop.

  • Search Help Error while Publishing Query in Explorer

    Hi All,
    We have upgraded BW from version 3.1 to BI 7.0. SP level is 15. When we publish query in Explorer, selection screen appears, we get error in selecting variable(Fiscal Year/Period) entries from search help. After selecting a value from a list of possible entries, the format is changed on the screen.
    For example:
    If we select 002.2002 for variable FiscalYear/Period, we get
    002 02 i.e. it is truncating 20 from 2002.
    Now, we have to manually enter the values.
    While executing query in BEx analyser, no such error occurs.
    What will be the solution?
    Regards,

    887188 wrote:
    Hi,
    I have added the below query in the EBS dataset to retrieve only unique applications as APPLICATION_NAME column has some duplicate data. I imported data to DB.
    select distinct(APPLICATION_NAME) as NAME from APPLICATIONIs there any table in OIM schema which you have named APPLICATION? AFAIK, applications from EBS are imported into Lookups in OIM and you will have to query lookup to get the Application name in OIM.
    But, when I try to filter on application I get below error
    Internal Exception: java.sql.SQLSyntaxErrorException: ORA-00936: missing expression
    Error Code: 936
    Call: select distinct(APPLICATION_NAME) as NAME from APPLICATION WHERE UPPER ( DISTINCT(APPLICATION_NAME) ) like UPPER('%%') The UPPER ( DISTINCT(APPLICATION_NAME) ) like UPPER('%%') clause here is wrong. What are you trying to achieve through this query?
    >
    >
    -Bikash

  • Using Search Help with ALV and Dynamic context node

    The topic subject already describes my situation.
    I have to create, populate and remove context nodes at runtime, and bind them to an ALV, to let user display the data or modify the data. The nodes I create are always typed with a table name, but the table name is of course, dynamic.
    This is all working: what's not working is help for entries inside the ALV; since the table has foreign keys and domains with check tables or fixed values, I expected that search helps were detected and managed by the framework.
    Instead, no help search is displayed except the input help based on data-type of the one "Date" input fields.
    I think I have to work on the dynamic node creation, and not on the ALV itself, since the latter only takes the node/attributes information, but i could be wrong. I tried with both the two following codings:
      CALL METHOD lo_nd_info_root->add_new_child_node
        EXPORTING
          static_element_type          = vs_tabname
          name                         = 'SAMPLE_NODE_NAME'
    *    is_mandatory                 = abap_false
    *    is_mandatory_selection       = abap_false
         is_multiple                  = abap_true
         is_multiple_selection        = abap_false
    *    is_singleton                 = abap_false
          is_initialize_lead_selection = abap_false
          is_static                    = abap_false
        RECEIVING
          child_node_info              = lo_nd_info_data .
    cl_wd_dynamic_tool=>create_nodeinfo_from_struct(
          parent_info = lo_nd_info_root
          node_name = 'SAMPLE_NODE_NAME'
          structure_name = vs_tabname
          is_multiple = abap_true ).
    The result is the same...is there any way to let the ALV know what search helps it has to use, and doesn't force me to manually build a VALUE_SET to be bound on the single attributes? There are many tables, with many fields, and maintaining this solution would be very costly.

    I have checked with method GET_ATTRIBUTE_VALUEHELP_TYPE of interface IF_WD_CONTEXT_NODE_INFO, on an attribute which i know to have a search help (Foreign key of a check table).
    The method returns 'N', that is the constant IF_WD_VALUE_HELP_HANDLER~CO_VH_TYPE_NO_HELP. So, the framework was not able to find a suitable search help.
    Using method GET_ATTRIBUTE_VALUE_HELP of the same interface, on the same attribute, returns me '111', which is constant C_VALUE_HELP_MODE-AUTOMATIC.
    Therefore, the WD framework knows it has to automatically detect a value help, but fails to find one.
    Also, this means in my opinion that the ALV and the dynamic external mapping are not the culprits: since node creation, no help is detected for any attribute but the date. Honestly, I don't have a clue on what's happening.

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

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

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

  • Custom search help for a custom field in SRM 7

    EDIT: I'm gonna clarify on this thread since my first post wasn't explicative enough... thanks for the patience
    Hi all gurus,
    the question is about a search help in SRM7 but since the task is about abap development, I guess this is the right section to ask for.
    Shortly; every purchase doc in our SRM7 has a custom header table which contains data which are retrieved from the connected backends. In this custom table, the user has the opportunity to add manually a line, and for a specific input field in table, we have to define a search help which should retrieve the appropriate possible values w.r.t. the "target" backend for the document.
    A bit of technical data: say the field is called ZZ_R3_ROLE; it's included in a custom structure ZR7_HEADER_CST_GEN which is itself an append for BBP_PDHCF.
    I defined a Search Help for that field and the corresponding exit FM to manage our task.
    Unfortunately, to retrieve the possible values for the specific backend I need some informations like:
    - the backend on which the document will be distributed;
    - the process type of the document.
    This means that my search help should take into account additional informations that comes from the document I'm processing; I don't know what's the "clean" solution to do this.
    I've seen on an old system (a SAP SRM 3.0) a workaround based on IMPORT/EXPORT ... TO MEMORY ID has been used. Actually, I'd like to find a more elegant solution, if any.
    So... as you can see, I'm absolutely a newbie on the argument, but since I can trigger the search help only from a purchase document (PO, contract) process, I should need at least the GUID of the document to retrieve, for example, what's the target backend for that document in order to provide proper values.
    Any hint/suggestion and in particular, a sketch of code as example is welcome.
    Edited by: Matteo Montalto on Oct 22, 2010 3:01 PM

    Hi,
    into your modify view,
    extract data you need in your search help in an itab (do it into a class do not perform select directly into modify view) and then bind it as value help to your WD element.
    Regards,
    Ivan

  • Help required in Search help

    Hi Friends,
       My requirement is that when user Clicks on pushbutton in module pool screen,popup window with 4 radio buttons to be displayed.Once user selects the push button and said ok...Then Search help has to be displayed with Selection Criteria for 4 fields..the selected radiobutton in the popup has to be passed on to the one of the search help input fields as a default value and the remaining input values will be entered by user manually as per the requirement. Finally result has to come for the user input.
    Could any one suggest me how can i do this?
    Thanks & Regards
    Ravindra

    Hi,
    Try this.
    In the user command of the first screen( in which the push button is placed and its func code is PB) in the function code 'PB', do the following
    1. Call a new screen with x and y coordinates so that it appears as a pop up window
       ex:  call screen 9000 starting at <x> <y> ending at <x> <y>
    2. In the 2nd screen 9000, place 4 radiobuttons and create a gui status with ok and cancel buttons.
    3. In the usercommand of the 2nd screen 9000, check for the ok code of 'OK' button and pass the value to the input fields in the 1st screen.
    4. Then use the passed value and filter the search help value based on it and call the function module F4IF_INT_TABLE_VALUE_REQUEST for the search help of the required fields.
    Hope this may be helpful.
    Regards,
    Sharin

  • Applying filters to F4 Search help - how so with many entries?

    Hello all,
    I have a problem that I have to filter a search help for employees. We use a DB view that unions infotypes 1, 2 and 105. Now I need to restrict potential employees to a given company code BUKRS.
    I now invoke search help in REQUEST ON-VALUE REQUEST within a DynPro screen and call function module F4IF_INT_TABLE_VALUE_REQUEST which I am passing the restricted internal table.
    Fine, that works - however, in the DynPro (which is actually used as an EWT within our portal), the entire internal table is sent to the frontent instead of, say, 250 or so.
    The search help dialog offers the possibility to manually restrict for first and last name - is it perhaps possible, that this search only applies on the server (ITAB) and just returns the results according to the user input?
    Otherwise, sending all potential employees to the frontend is consuming too much resources (time and traffic).
    In function group SDHI there is an "example" module F4IF_SHLP_EXIT_EXAMPLE which tries to explain how to use callbacks but from my point of view I understand very few (it misses the big picture).
    Do you know an alternative, e.g. using the other module F4IF_FIELD_VALUE_REQUEST and to apply a filter to BUKRS using a callback mechanism? There are module parameters indicating that possibility (passing some report?). Perhaps one of you has some sample code, because I am much more trained in BAPI and web stuff only...
    Any hints? Thank you in Advance!
    Regards,
    Timo

    Hi,
    if I can understand you, you tell me that you search information in the view and all found records (let´s say 300) are saved in the internal table, which in time you pass to function F4IF_INT_TABLE_VALUE_REQUEST for display. Now, you think it is too much to display 300 records because of time and traffic.
    Try this:
    REPORT ztest NO STANDARD PAGE HEADING.
    TABLES mara.
    DATA: mytable TYPE TABLE OF ddshretval WITH HEADER LINE.
    DATA l_repid TYPE syrepid.
    PARAMETERS p_mtart LIKE mara-mtart.
    AT SELECTION-SCREEN ON VALUE-REQUEST
                 FOR p_mtart.
      l_repid = sy-repid.
      CALL FUNCTION 'F4IF_FIELD_VALUE_REQUEST'
        EXPORTING
          tabname           = 'MARA'
          fieldname         = 'MTART'
          dynpprog          = l_repid
          callback_program  = l_repid
          callback_form     = 'F4CALLBACK'
        TABLES
          return_tab        = mytable
        EXCEPTIONS
          field_not_found   = 1
          no_help_for_field = 2
          inconsistent_help = 3
          no_values_found   = 4
          OTHERS            = 5.
    START-OF-SELECTION.
    *&      Form  F4_form
          Exclude all material types that start with F & H
    FORM f4callback
         TABLES   record_tab STRUCTURE seahlpres
         CHANGING shlp TYPE shlp_descr
                  callcontrol LIKE ddshf4ctrl.
      DATA: aux_struc TYPE ddshselopt.
      MOVE: 'H_T134' to aux_struc-shlpname,
            'MTART'  TO aux_struc-shlpfield,
            'E'      TO aux_struc-sign,
            'CP'     TO aux_struc-option,
            'F*'     TO aux_struc-low.
      append aux_struc to SHLP-SELOPT.
      MOVE: 'H_T134' to aux_struc-shlpname,
            'MTART'  TO aux_struc-shlpfield,
            'E'      TO aux_struc-sign,
            'CP'     TO aux_struc-option,
            'H*'     TO aux_struc-low.
      append aux_struc to SHLP-SELOPT.
    ENDFORM.                                                    "F4_form

  • Search Help Exit for ECC 6.0

    Greetings,
    I'm working in ECC 6.0. I'm trying to create a Help screen exit using F4IF_SHLP_EXIT_EXAMPLE as a model. The problem is that it will not compile due to the fact that a 'LIKE'  parameter type is used in the function definition tables tab. This is not allowed in 6.0.
    I've tried several work arounds without success. I have search for a 6.0 version of this function without success.
    Does anyone have a solution?
    rv

    Hi Richard,
    We too are running ECC 6.0 (release 701) and the LIKE definition doesn't cause a problem in our system. Maybe it has to do with a particular support pack level. Anyway, since you have presumably copied F4IF_SHLP_EXIT_EXAMPLE to a custom function module, you can manually change the typing of the Changing parameter. I tried this below and the search help exit executes as expected.
    If this doesn't resolve the issue for you, you may want to repost your question to the ABAP Development community.
    Cheers,
    Amy

Maybe you are looking for