Using ALV as a search Help

Has anyone used ALV as a search help presentation/selection method. I'm thinking, in a simplistic sense, it would be just creating an itab and presenting it on a grid in a container on a new screen called by an exit....
Probably too simple, huh? Pointers to any snippets that implement this would be welcome.
(additionally, might have a need to save user layouts of this info as well)
Thoughts, comments, pitfalls.... ?
Thanks...
...Mike

Hey Michael a working example I just made for some1
thought u might be interested
Q. i_checkbox_fieldname = 'CHECKBOX'
A. If the table output in the popup has checkboxes at the beginning of the rows (e.g. for multiple selection), the internal table must contain a field containing the value of the checkbox.
Assign the name of this field to the parameter I_CHECKBOX_FIELDNAME.
Q. i_tabname = 'TLINE'
A. This is the name of ur input help internal table
Q. it_fieldcat = fieldcat[]
A The table u gonna display has to have a fieldcat.
Q. it_excluding = extab[].
A. In case u wanna exclude some functions.
Below is a working example, paste it in se38 and activate.
!!! Warning SAVE IT AS A LOCAL OBJECT !!!
report ztests1.
type-pools: slis.
data: index type i.
data: l_kunnr like kna1-kunnr.
data: input(10) type c,
 text(4) type c,
 text1(5) type c.
data: begin of itab occurs 10,
 kunnr like kna1-kunnr,
 name1 like kna1-name1,
 end of itab.
data: e_exit.
data: fieldcat TYPE slis_t_fieldcat_alv WITH HEADER LINE.
parameter: p_kunnr(10) type c.
at selection-screen on value-request for p_kunnr.
select kunnr name1 up to 10 rows
 from kna1
 into table itab.
fieldcat-tabname = 'ITAB'.
fieldcat-fieldname = 'KUNNR'.
fieldcat-seltext_m = 'Cust'.
fieldcat-ddictxt = 'M'.
fieldcat-outputlen = 10.
APPEND fieldcat.
CLEAR fieldcat.
fieldcat-tabname = 'ITAB'.
fieldcat-fieldname = 'NAME1'.
fieldcat-seltext_m = 'Cust Name'.
fieldcat-ddictxt = 'M'.
fieldcat-outputlen = 30.
APPEND fieldcat.
CLEAR fieldcat.
 CALL FUNCTION 'REUSE_ALV_POPUP_TO_SELECT'
 EXPORTING
 I_TITLE = 'Customer Selection'
 I_SELECTION = 'X'
 I_ALLOW_NO_SELECTION =
 I_ZEBRA = ' '
 I_SCREEN_START_COLUMN = 0
 I_SCREEN_START_LINE = 0
 I_SCREEN_END_COLUMN = 0
 I_SCREEN_END_LINE = 0
 I_CHECKBOX_FIELDNAME =
 I_LINEMARK_FIELDNAME =
 I_SCROLL_TO_SEL_LINE = 'X'
 i_tabname = 'ITAB'
 I_STRUCTURE_NAME =
 IT_FIELDCAT = fieldcat[]
 IT_EXCLUDING =
 I_CALLBACK_PROGRAM =
 I_CALLBACK_USER_COMMAND =
 IS_PRIVATE =
 IMPORTING
 ES_SELFIELD =
 E_EXIT = e_exit
 tables
 t_outtab = itab
 EXCEPTIONS
 PROGRAM_ERROR = 1
 OTHERS = 2
 IF sy-subrc <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
 WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
 ENDIF.

Similar Messages

Use Of Dictionary Based search help in adobe interactive form

Hi friends,
I wanted to export the search help value into corresponding field of Adobe interactive form.
I am using dictionary type search help in WD context attribute property. I am able to get the search help popup with right data on form. But if select some value it is not exporting data into the field and getting "entry too longer" error.
Can any one help out for this issue.
Note : Wanted to use only dictionary based search help.
Thanks in advance
Naganath Mudale

thanks

Web dynpro ALV requirement with search help

Hello Experts,
I developed a custom transaction in Web dynpro. It has an ALV display in editable mode where the user can enter Material number, plant, quantity and Batch as input fields for Production confirmation.
There is a requirement to add a search-help to BATCH field similar to the one that appears in std. MFBF transaction. Basically what it means is that I will have to capture the material, plant of that line in ALV table and get the stock and batch details from MCHB table and provide them in search help.
I created a dictionary search help with a search-help exit FM that will extract the details from MCHB table. I am having trouble in extracting the line index to get the material number and plant values from the view to export.
Please help me as to how to extract the line index of an ALV table for which the F4 help was clicked.
Also it would be great if I could find a much simpler and better approach to handle the requirement.
Regards
Pratyusha

Hi,
If you have set the help mode as dictionary search help in your context, and if you have defined your search help to have these importing and exporting parameters, then it will work without you doing anything else. Provided you have mentioned the name of the search help in the structure definition itself. You do not have to write explicit event handlers for dictionary search helps.
Or else, you can use an OVS search help. In that case, in the OVS event handler, you will have a parameter ovs_callback_object. Ovs_callback_object->context_element will give you the element on which the F4 was clicked. If you do a get_static_attributes on that, you will get the values of each attribute. Then you can call your function module to get the Batch field. I think OVS will suit your requirement. You can see examples of OVS in the component demo_value_help in the package swdp_demo.
Hope this helps.
Regards,
Nithya

ALV Table - Different Search Help depending on Cell

Hey you experts,
For my current project I'm working on an editable ALV Table. The table has three columns and shall contain:
1) The name
2) The Old value
3) The New Value
of an item.
The name of the item is known (e.g. Product Category, Accounting Type and so on).
The main problem: I have/want to offer search-help to the user in the second and third column depending on the content of the first cell ==> The search help can of course differ in several rows. Example:
NAME OLD-VALUE NEW-VALUE
P.Category Computer Notebook
Acc.Type. A B
The Computer field, shall have a search-help for a differnt data-type (DDIC help) than the A/B types.
Is this possible? There should be a kind of "On-Open-F4-Help" event in which i can adjust the F4 help, which shall be used depending on the currently selected cell.
Thanks for any help,
greetings,
Timo Stark

Hey Sam,
Yes I was able to achieve it. Create a collective search help, which includes all relevant data-elements.
Create a search hel exit.
Use the following code:
IF CALLCONTROL-STEP <> 'SELONE' AND
 CALLCONTROL-STEP <> 'SELECT' AND
 " AND SO ON
 CALLCONTROL-STEP <> 'DISP'.
 EXIT.
ENDIF.
* STEP SELONE (Select one of the elementary searchhelps)
* This step is only called for collective searchhelps. It may be used
* to reduce the amount of elementary searchhelps given in SHLP_TAB.
* The compound searchhelp is given in SHLP.
* If you do not change CALLCONTROL-STEP, the next step is the
* dialog, to select one of the elementary searchhelps.
* If you want to skip this dialog, you have to return the selected
* elementary searchhelp in SHLP and to change CALLCONTROL-STEP to
* either to 'PRESEL' or to 'SELECT'.
DATA: lv_line LIKE LINE OF SHLP_TAB,
 lv_line_tmp LIKE LINE OF SHLP_TAB.
DATA lv_current_context_element TYPE REF TO IF_WD_CONTEXT_ELEMENT.
DATA lv_parent_data TYPE /SIE/SRM_FYC_CHANGE.
DATA:lv_current_node TYPE REF TO IF_WD_CONTEXT_NODE,
 lv_index TYPE i.
IF CALLCONTROL-STEP = 'SELONE'.
 lv_current_context_element = CL_WDR_VALUE_HELP_HANDLER=>M_CONTEXT_ELEMENT.
 lv_current_node = lv_current_context_element->get_node( ).
 lv_index = lv_current_context_element->get_index( ).
 lv_current_node->get_static_attributes( exporting index = lv_index importing static_attributes = lv_parent_data ).
 "switch over parent data..
 CASE lv_parent_data-type.
 WHEN 10.
 "cost center
 lv_line-SHLPNAME = 'BBP_F4_COST_CTR'.
 WHEN 3.
 lv_line-SHLPNAME = 'COM_CAT'.
 WHEN OTHERS.
 lv_line-SHLPNAME = ''.
 callcontrol-step = 'EXIT'.
 EXIT.
 ENDCASE.
 LOOP AT shlp_tab INTO lv_line_tmp.
 IF lv_line_tmp-shlpname <> lv_line-shlpname.
 DELETE TABLE shlp_tab FROM lv_line_tmp.
 CONTINUE.
 ENDIF.
 ENDLOOP.
 callcontrol-step = 'PRESEL'.
 EXIT.
ENDIF.
* STEP PRESEL (Enter selection conditions)
* This step allows you, to influence the selection conditions either
* before they are displayed or in order to skip the dialog completely.
* If you want to skip the dialog, you should change CALLCONTROL-STEP
* to 'SELECT'.
* Normaly only SHLP-SELOPT should be changed in this step.
IF CALLCONTROL-STEP = 'PRESEL'.
* PERFORM PRESEL ..........
 EXIT.
ENDIF.
* STEP SELECT (Select values)
* This step may be used to overtake the data selection completely.
* To skip the standard seletion, you should return 'DISP' as following
* step in CALLCONTROL-STEP.
* Normally RECORD_TAB should be filled after this step.
* Standard function module F4UT_RESULTS_MAP may be very helpfull in this
* step.
IF CALLCONTROL-STEP = 'SELECT'.
* PERFORM STEP_SELECT TABLES RECORD_TAB SHLP_TAB
* CHANGING SHLP CALLCONTROL RC.
* IF RC = 0.
* CALLCONTROL-STEP = 'DISP'.
* ELSE.
* CALLCONTROL-STEP = 'EXIT'.
* ENDIF.
 EXIT. "Don't process STEP DISP additionally in this call.
ENDIF.
* STEP DISP (Display values)
* This step is called, before the selected data is displayed.
* You can e.g. modify or reduce the data in RECORD_TAB
* according to the users authority.
* If you want to get the standard display dialog afterwards, you
* should not change CALLCONTROL-STEP.
* If you want to overtake the dialog on you own, you must return
* the following values in CALLCONTROL-STEP:
* - "RETURN" if one line was selected. The selected line must be
* the only record left in RECORD_TAB. The corresponding fields of
* this line are entered into the screen.
* - "EXIT" if the values request should be aborted
* - "PRESEL" if you want to return to the selection dialog
* Standard function modules F4UT_PARAMETER_VALUE_GET and
* F4UT_PARAMETER_RESULTS_PUT may be very helpfull in this step.
IF CALLCONTROL-STEP = 'DISP'.
* PERFORM AUTHORITY_CHECK TABLES RECORD_TAB SHLP_TAB
* CHANGING SHLP CALLCONTROL.
 EXIT.
ENDIF.
greetings

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.

Search Help in Classical ALV

Hi All,
I have a small problem. Can anybody tell me how can i add a search help to a specific column in my classical ALV?
Regards,
Prakash Pandey

Hi Prakash,
In the Field Catalog there are two fields which are used to get the Search Help of any of the Column in ALV. Those are : REF_FIELDNAME and REF_TABNAME.
For example,
ls_fieldcat-fieldname = 'VBELN'.
ls_fieldcat-fix_column = 'X'.
ls_fieldcat-key = 'X'.
ls_fieldcat-outputlen = '10'.
ls_fieldcat-seltext_m = 'Sales Document'.
ls_fieldcat-edit = 'X'.
ls_fieldcat-ref_fieldname = 'VBELN'.
ls_fieldcat-ref_tabname = 'VBAP'.
append ls_fieldcat to p_fieldcat.
clear ls_fieldcat.
The above code will show the F4 for the column VBELN in the ALV.

How to use the created search helps in the program?

Hi Everyone,
I know how to create Search help elementary / collective search help through SE 11. I have a question, how can I make use of the created search help in the program.
How to use the Search help in the programs, which is created through SE11
Subbu.

Hi,
In case if you want to use in parameters statement, then we can use the suffix MATCHCODE OBJECT syntax.
Eg.
report abc.
parameters : a(10) type c matchcode object ZBELNR.
Hope this helps.
regards,
amit m.

F4-Help without using a table search help

Hi,
We´re using CRM 2007 and I have created several F4-Helps for different fields on the webui.
There it was always necessary to use an existing table search help in the GET_V-method:
CREATE OBJECT rv_valuehelp_descriptor
    TYPE
      cl_bsp_wd_valuehelp_f4descr
    EXPORTING
      iv_help_id                  = lv_help_id   "search help name
      iv_help_id_kind             = if_bsp_wd_valuehelp_f4descr=>help_id_kind_name
      iv_input_mapping            = lt_inmap
      iv_output_mapping           = lt_outmap
      iv_trigger_submit           = abap_true.
But how can I create a f4-help without an existing search help. I have an internal table that I want to be shown like an f4-help (not as dropdown -> a dropdown-field wouldn´t be a problem).
Structure of the internal table: COML_PROD_CAT_REL_F4
Thanx for help.
Greetings,
Sven
Edited by: Sven Keller on Aug 13, 2008 4:26 PM

Hi Sven,
you already pasted the correct call for creating a value help. Now what you have to alter is the variable lv_help_id to reflect a F4-Valuehelp class.
      CREATE OBJECT rv_valuehelp_descriptor TYPE cl_bsp_wd_valuehelp_f4descr
        EXPORTING
          iv_help_id        = '(CL_CRM_UIU_BP_IDTYPE_2_F4)' "#EC NOTEXT
          iv_help_id_kind   = if_bsp_wd_valuehelp_f4descr=>help_id_kind_comp
          iv_input_mapping = lt_inmap
          iv_output_mapping = lt_outmap.
As you can see CL_CRM_UIU_BP_IDTYPE_2_F4 is a normal ABAP class implementing interface IF_BSP_WD_CUSTOM_F4_CALLBACK. Please take a look at it.
It should not be very hard to implement the single method
cheers Carsten

How to include Search Help which has been created using SE11

Hi all,
I have created the custom search help in SE11. What is the way to include it in my code? Thanks in advance.

Hi Mil,
There are different ways of using the search help created by SE11 depending on the kind of application you are using.
1. Search help can be attached to a DATA ELEMENT under the tab FURTHER CHARACTERISTICS.
Now wherever this data element will be used, automatically the search help will be available on the output screen. e.g. in selection screen using parameters statement etc.
PARAMETERS: P_VAL1 TYPE Z_DATAELE.
2. Search help can be also attached to database table fields directly in the tab Entry help/check. Now wherever this database table field is used e.g. in SELECT-OPTIONS statment, the search help will be automatically available on output selection screen.
3. Also, search helps can be directly used in the programs using function modules and event.
PROCESS ON VALUE-REQUEST.
FIELD <f> MODULE <mod>.
Here in the module, you can use following function module for fetching the search help on the screen.
F4IF_FIELD_VALUE_REQUEST
4. Search help can be direclty attached to the selection screen statements like SELECT-OPTIONS using MATCHCODE object extension
SELECT-OPTIONS: LP_STATS FOR TJ30-ESTAT MATCHCODE OBJECT ZH_TJ30 NO-EXTENSION NO INTERVALS.
Hope this sort out your issue.
PS If the answer solves your query, plz close the thread by rewarding each reply.
Regards
Message was edited by:
Sapna Modi

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

Getting values from screen to search help exit

Hi Experts,
I have created a search help in which I am not using selection method but search help exit. Dialog type is 'Dialog with value restriction'. My requirement is to get the values entered in restriction screen into search help exit. Please suggest a parameter which will hold this value in search help exit function module.

Hi M,
As you know there are 5 steps in search help exit. For each step, the values in parameter of your search help exit is different.
For your requirement, you need process in step 'DISP', and get the selection value from 'SHLP-SELOPT'.
Example:
*Build range for customer number
LOOP AT shlp-selopt INTO ls_selopt WHERE shlpfield = 'KUNNR'.
lr_kunnr-sign = ls_selopt-sign.
lr_kunnr-option = ls_selopt-option.
lr_kunnr-low = ls_selopt-low.
lr_kunnr-high = ls_selopt-high.
APPEND lr_kunnr.
CLEAR: lr_kunnr.
ENDLOOP.
Then using the lr_kunnr range in your select statement.
regards,
Archer

Enhancing standard (single select)search help for Multiple value selection

Hi,
Standard search help for Business Partner (in cProjects) allows only single value selection for input fields. I want to make this multiple selection.
Is there a way to do it.
I used an OVS and built a similar search but its difficult to get the standard options like saving to personal value list etc in it.
It would be good if there is a way to modify the standard search help to allow multiple selection. Any ideas??
Appreciate your help,
Thanks,
Sri
Edited by: Sri on Sep 9, 2010 8:50 PM
Edited by: Sri on Sep 9, 2010 8:52 PM

As far as I know you can't make a standard ABAP dictionary search help return multiple entries - where you get this sort of functionality the searches don't use the standard Elementary search help framework (e.g. organisational structure searches)
Given that the WDA search help relies on these dictionary based searches, I'd think very much that you couldn't enhance it to return multiple. how you could even return multiple entries into a single UI element input field is also confusing to me.
I'd suggest creating a freely programmed value help, it would certainly take quite some effort to recreate those personal value lists etc, but it could be done - I don't like OVS, but that just me.

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

Issue in CATS search help Hit List

Hi All,
At the moment we are facing an issue in CATS .
We have added customer fields in the CATS data entry area by implementing CAT0005 and CAT0002 enhancements.
One of customer filed we have created Search Help by using SE11 in that search help we have given default values in one of field and due to that on CAT2 transaction in the customer filed showing search help and that search help giving 2 records as hit list ( due to defaulting value in SE11 ).
Now when user clicking on Record working time service in that when customer click upon custom filed search help its giving 30 records as hit list u2026( here the search help should give 2 records hit list )
Any idea

note that search help of CAT2 and record working time are different!
these are teh steps
please modify the following in the table TCATS_SHLP_ITS as follows:
1. Execute the T-Code SM31
2. Enter the table name TCATS_SHLP_ITS.
or check the class
CL_XSS_CAT_VALUE_HELP_GENERAL
or check
CL_XSS_CAT_VALUE_HELP*
take an example from Sap note 914125

Steps for creation of search help exit for a search help

Hi,
I have created a search help. I need to create a search help exit for this search help.
Please let me know how to create a search help exit as well as how to link it to my search help.

1)Copy the FM F4IF_SHLP_EXIT_EXAMPLE to write your own FM. (check the documentation and coding of FM F4IF_SHLP_EXIT_EXAMPLE).
2)write your code depending upon the functionality you want.
3)attach the FM in search help through SE11 in "search help exit" field.
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.
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.
For more detailed information please refer to the documentation describing the concept of the search help exit.
The module must react with an immediate EXIT to all steps that it does not know or does not want to handle.

Using ALV as a search Help

Similar Messages

Maybe you are looking for