FM to find Search help for a table field

Hello Colleagues,
is there any function module which would return the search help associated with a table field ?
I tried with the FM F4IF_DETERMINE_SEARCHHELP but it returns search help that is associated with either to table field DE or search helps associated with the value table fields. I need to find only
the search helps that are associated with a table field but not the value tables or fixed values.
For ex. If i pass table_name = 'SFLIGHT' and field_name='CARRID' then it should return me S_CARRIER_ID. but if i pass field_name='CONNID' then it should return nothing..
Best Regards, JVR

Hi Kishore,
Use the Function Modulein the F4 help associated with a table field ...
CALL FUNCTION ' HELP_VALUE_GET"
EXPORTING
fieldname = 'CARRID' "field name in the table you refer
tabname = 'SFLIGHT' "Table name
IMPORTING
select_value = S_CARRIER_ID. "Selected field
Regards,
Prabhudas

Similar Messages

Assign search help for a screen field in standard program?

Hi All,
Is there any other way to assign search help to a standard SAP screen field? (to be precise i want to assign search help to Recipient field in table control of components tab in transaction IW32/IW31)
I know we can do this by assigning search help through screen painter (by changing standard program, which is my last option).
Any advice/help will be greatly appreciated.

Hi,
I think you will find solution in below <b>threads</b>:
Re: Search Help for standard field
How to assign a search help
Search help for Standard SAP field
<b>Reward if helpful</b>
Rgds,

Search Help for Infotype Custom Field

Hi,
I have created a search help for a custom field in an infotype. What would be the best way of filtering the help selection based on infotype values such as molga, begda, endda?
Thanks in advance.
/Elvez

Hi Nishanth,
thanks for your reply, perhaps I should clarify my question:
1) I have a custom field in an infotype
2) I have a table containing the search help information
3) I assigned a search help to the custom field
4) I have activated a search help exit
The problem is that the information that I get from the custom field is not sufficient for making the selection. Therefore, I would like to somehow get hold of the addition information, such as BEGDA, ENNDA, MOLGA, to do a proper selection in the search help exit. How can I achieve that?
I read something about function module DYNP_VALUES_READ -would it be possible to call this function module from my search help exit and thereby reach my goal?
/Elvez
Message was edited by: Elvez

Change Search Help for Payment Terms Field

Hi,
I would like to change the Search Help for Payment Terms Field, in Customer Master (KNVV-ZTERM). and in Sales Document. I believe it is the same.
Default is From Table T052 / T052U
ZTERM and TEXT1 Fields
I would like to have
From Table TVZBT
ZTERM and VTEXT
PayT Own Explanation Field.
Can we change the Search Help.

Hi,
The search help for the payment terms is not coming from the DDIC search help..
It is coded in the process on value-request event...
The function module FI_F4_ZTERM is called for this..you have to change this function module in case if you want the values from a different table..
OR do implicit enhancement in the subroutine FORM HELP_ZTERM in the include MF02DFH0 to call your search help instead of the function module FI_F4_ZTERM ..And do the same for the sales order also..
Thanks
Naren

SRM Portal - Search help for a custom field

Hi,
I have added a custom field to the SRM Portal (5.0) shopping cart, by adding the field to structures INCL_EEW_PD_ITEM_CSF INCL_EEW_PD_ITEM_CSF_SC.
However, I need to filter the search help for that custom field, based on values & relationships stored in a Z table.
Is this possible? How? Please help.
Thank You.

Currently, my idea would be to create a search help for the custom field & filter the values in a search help exit. However, would I be able to get other field values (standard) from SRM into my search help exit?

F4 help for ALV table field

Hi Experts,
I need to implement F4 help for ALV table field.
I my scenario, I am using two views. If we click on any record in fist view then it displays the popup window (second view) with relevant record details.
Here one of the columns having fieldnames corresponding values (old values), for correcting old values I have created new value editable column, we can enter new value for old value then we can save it. Till this functionality is ok.
Then I have included OVS help for new value field. Here I need to get f4 help for newvalue field relevant to fieldname.
For example: user clicks on f4 in cell (new value) then if corresponding fieldname is u2018WERKSu2019 then it shows the plant values
Here I can get fieldname, domain name and value table using method set_attribute ().
Same concept I have implemented in ALV using F4IF_FIELD_VALUE_REQUEST. It is working fine
Here I have little bit confusion. Please advise me how to implement in OVS.
Regards,
BBC

Hi,
you'll have to create a method for the OVS search help (define it in the "OVS component usage" field in the context).
Sample code (should work for WERKS):
method on_ovs .
declare data structures for the fields to be displayed and
for the table columns of the selection list, if necessary
types:
    begin of lty_stru_input,
add fields for the display of your search input here
      WERKS TYPE WERKS,
    end of lty_stru_input.
types:
    begin of lty_stru_list,
add fields for the selection list here
      WERKS TYPE WERKS_D,
      NAME1 type NAME1,
    end of lty_stru_list.
data: ls_search_input type lty_stru_input,
        lt_select_list   type standard table of lty_stru_list,
        ls_text          type wdr_name_value,
        lt_label_texts   type wdr_name_value_list,
        lt_column_texts type wdr_name_value_list,
        lv_window_title type string,
        lv_group_header type string,
        lv_table_header type string,
        lv_werks type werks_d.
field-symbols: <ls_query_params> type lty_stru_input,
                 <ls_selection>    type lty_stru_list.
case ovs_callback_object->phase_indicator.
    when if_wd_ovs=>co_phase_0. "configuration phase, may be omitted
in this phase you have the possibility to define the texts,
if you do not want to use the defaults (DDIC-texts)
Set label from Medium Description to something more logical...
      ls_text-name = `NAME1`. "must match a field in list structure
      ls_text-value = `Plant description`.
      insert ls_text into table lt_label_texts.
Set col header from Medium Description to something more logical...
      ls_text-name = `NAME1`. "must match a field in list structure
      ls_text-value = `Plant description`.
      insert ls_text into table lt_column_texts.
     lv_window_title = wd_assist->get_text( `003` ).
     lv_group_header = wd_assist->get_text( `004` ).
     lv_table_header = wd_assist->get_text( `005` ).
      ovs_callback_object->set_configuration(
                label_texts = lt_label_texts
                column_texts = lt_column_texts
                group_header = lv_group_header
                window_title = lv_window_title
                table_header = lv_table_header
                col_count    = 2
                row_count    = 20 ).
    when if_wd_ovs=>co_phase_1. "set search structure and defaults
In this phase you can set the structure and default values
of the search structure. If this phase is omitted, the search
fields will not be displayed, but the selection table is
displayed directly.
Read values of the original context (not necessary, but you
may set these as the defaults). A reference to the context
element is available in the callback object.
     ovs_callback_object->context_element->get_static_attributes(
         importing static_attributes = ls_search_input ).
    pass the values to the OVS component
     ovs_callback_object->set_input_structure(
         input = ls_search_input ).
    when if_wd_ovs=>co_phase_2.
If phase 1 is implemented, use the field input for the
selection of the table.
If phase 1 is omitted, use values from your own context.
      if ovs_callback_object->query_parameters is not bound.
      endif.
      assign ovs_callback_object->query_parameters->*
                              to <ls_query_params>.
      if not <ls_query_params> is assigned.
TODO exception handling
      endif.
        call method ovs_callback_object->context_element->get_attribute
          exporting
            name = 'WERKS'
          importing
            value = lv_werks.
        data: lv_subcat_text type rstxtmd.
        select werks
               name1
          into table lt_select_list
          from T001W.
        ovs_callback_object->set_output_table( output = lt_select_list ).
    when if_wd_ovs=>co_phase_3.
apply result
      if ovs_callback_object->selection is not bound.
      endif.
      assign ovs_callback_object->selection->* to <ls_selection>.
      if <ls_selection> is assigned.
        ovs_callback_object->context_element->set_attribute(
                               name = `WERKS`
                               value = <ls_selection>-werks ).
      endif.
endcase.
endmethod.

Search help for selection screen field

Hi ,
steps for creating search help for a key field in selection screen..
tables is a userdefined from which the field is taken..
thxs,
vind

hi,
c this.
REPORT ZXYZ_0002 .
data: dynfields type table of dynpread with header line.
data: return type table of ddshretval with header line.
selection-screen begin of block b1 with frame title text-001 .
selection-screen begin of line.
PARAMETERS: P_BUKRS type T001-BUKRS.
selection-screen comment 30(20) BUTXT for field p_bukrs.
selection-screen end of line.
selection-screen end of block b1.
at selection-screen output.
if butxt is initial.
   select single butxt into butxt
         from t001
        where bukrs = p_bukrs.
endif.
at selection-screen on value-request for p_bukrs.
call function 'F4IF_FIELD_VALUE_REQUEST'
       exporting
            tabname           = 'T001'
            fieldname         = 'BUKRS'
            dynpprog          = sy-cprog
            dynpnr            = sy-dynnr
            dynprofield       = 'P_BUKRS'
       tables
            return_tab        = return
       exceptions
            field_not_found   = 1
            no_help_for_field = 2
            inconsistent_help = 3
            no_values_found   = 4
            others            = 5.
read table return with key fieldname = 'P_BUKRS'.
Add it back to the dynpro.
dynfields-fieldname = return-retfield.
dynfields-fieldvalue = return-fieldval.
append dynfields.
Get the company code from db and add to dynpro
data: xt001 type t001.
clear xt001.
select single * into xt001
         from t001
        where bukrs = return-fieldval.
dynfields-fieldname = 'BUTXT'.
dynfields-fieldvalue = xt001-butxt.
append dynfields.
Update the dynpro values.
call function 'DYNP_VALUES_UPDATE'
       exporting
            dyname     = sy-cprog
            dynumb     = sy-dynnr
       tables
            dynpfields = dynfields
       exceptions
            others     = 8.
start-of-selection.
rgsds
anver
if hlped mark points

Attach search help to standard table field

Hi,
I need to attach search help to standard table field VBKD-EMPST.
I have create a z search help and taken acess key from SAP.
But unable to attach this to standard table field.
Kindly help.
Moderator message: duplicate post locked.
Edited by: Thomas Zloch on Oct 27, 2010 6:11 PM

Hi,
just go throw this link
Re: Attaching Search Help to a field
I hope this will help u
Thanks
Regards
Akhilesh Singh

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

Dynamic value help for a table field to fill two fields, how to?

Hi all gurus,
In SRM 7 I defined a dynamic value help for a single field (ZZ_PROLE_R3) of my header custom table.
That's the code from WDDOMODIFYVIEW in the webdynpro /SAPSRM/WDC_DODC_CT, view V_DODC_CT:
DATA: lo_tabnode        TYPE REF TO IF_WD_CONTEXT_NODE.
      DATA: lo_tabnode_info   TYPE REF TO IF_WD_CONTEXT_NODE_INFO.
      DATA: tab_value         TYPE WDR_CONTEXT_ATTR_VALUE_LIST,
            wa_value          TYPE WDR_CONTEXT_ATTR_VALUE.
      lo_tabnode = wd_context->GET_CHILD_NODE( name = 'THCUS' ). "the custom table node
      lo_tabnode_info = lo_tabnode->get_node_info( ).
      wd_this->GET_VALHELP_ZZ_PROLE_R3( EXPORTING iv_guid = lv_guid
                                        IMPORTING ZZ_PROLE_R3_VALHELP = tab_value ). "this method returns the dyn value table
      lo_tabnode_info->set_attribute_value_set( name = 'ZZ_PROLE_R3'
                                                 value_set = tab_value ).
The method GET_VALHELP_ZZ_PROLE_R3 dynamically builds the value help table tab_value; such table is made up by two fields:
value : contains the value of the field
text   : contains a description of the value
The above solution works; now I'd like to enhance it. The custom table THCUS contains also a field called ZZ_PROLE_R3_DESC, which represents the description of ZZ_PROLE_R3. It is, exactly, the TEXT field in tab_value.
So I'd like to do as follows:
- the user clicks on the search help for ZZ_PROLE_R3 field of the table;
- the above described value help appears;
- after the selection, both ZZ_PROLE_R3 and ZZ_PROLE_R3_DESC are filled with the selected couple value - text chosen from the value help.
Could anyone help me achieving such a behaviour?
Again, a little request... when I open the above value help dialog box, the window itself has a label "Floorplan Manager application for OIF.." that obviously I'd like to redefine (e.g. "Role selection value help"). Is there any way to do that?
Thanks in advance

Chris Paine wrote:
It seems to me - given that your code is in wddomodifyview that you are trying to have different dropdowns per row
- I'm not sure where you are populating lv_guid - but I'd guess it is an attribute of the row selected? If it isn't then I can't see any reason that you would do this code in wddomodifyview and not wddoinit.
Hi Chris and thanks for your help,
lv_guid is the GUID of the document's header; I need to pass it to the method that populates my value help table because the values in it are derived from some fields on the document. (the situation actually is more complex; there's an RFC call on the backend for which the document is intended for to retrieve the data that populate the value help...).
I'm quite unexperienced on webdynpro and terminology; if dropdown menus are fixed selection option that appears on a field, I guess this is not my case. I did a pair of screenshot to provide an idea of what the solution by now is, and what "I would like to have":
[Pre-selection (F4 icon on the field in table)|http://imagebin.ca/view/npIsaqF.html]
[Value Help popup for the field ZZ_PROLE_R3|http://imagebin.ca/view/8fZUh3T.html]
[Result by now |http://imagebin.ca/view/3PaqdvE.html]
[Result I'd like to have.|http://imagebin.ca/view/dExR0J.html]
Chris Paine wrote:
However - by your comment on the "value help dialog box" I am guessing you are using an input field? If this is the case then I would strongly suggest that you change/enhance the structure of the context node THCUS (btw, better coding practise to refer to it as wd_this->wdctx_thcus when using the get child node construct) so that you refer to an actual SAP ddic search help, if you then associate in the structure the value and text fields then populating the text field should happen automatically. Also you'd have the nice side effect that your value help dialog would be named after the associated ddic search help.
Thanks for the code suggestion, I'll apply that. For what concerns the context node THCUS... It is, by standard, a node which I can't explictly find in the context for the view V_DODC_CT. The problem is that ZZ_PROLE_R3 and the corresponding description field ZZ_PROLE_R3_DESC of the table must be filled with data retrieved dynamically @ runtime from the backend. So I guess I can't populate a val help referring to a dictionary table/field; I'd rather do as follows:
- retrieve what's the target backend for the document (to do so, I have to process the document .. that's why the header guid passed to my method);
- RFC call to a custom method that extracts possible values for the specific backend;
- bind the ammissible values to the value help.
Chris Paine wrote:
I realise that this is rather a lot - so if you have any specific question please do respond - hopefully I or someone else will be able to clarify.
Thanks again for your help; additional info as well as code examples would be highly appreciated

Search help for Standard SAP field

Hi,
I need to add a search help to Group key (KONZS) field in XK01 transaction. How can i add our own search help to a field in standard transaction?? This is some what urgent, please give me the solution .
Thanks in Adavance,
Moghani.

You can APPEND your own search help to an SAP field that has search help defined. This is similar to APPENDing fields to an SAP table. But since field KONZS does NOT have any search help assigned, this option is not available to you.
You can also attach the search help to a field on a screen, i.e. limit the scope to that single screen, but this would still require a modification to the system, and hence, an access key. If you want to follow that route, the program name is SAPMF02K, screen 120, element list tab, references tab, search help column.
If you find another way to do this without an access key, please let us know.

Search help to a table field

Hello Folks,
I have an immediate requirement to assign a search help to a specific field in a Table.Requirement is as follows:
requirement:
I want the search help to be populated for the field HRP1000-SHORT when HRP1000-OTYPE='O'.
Values of search help are to be populated from another Custom table field1 where field2 = 'x'.
Please help me out in fixing this.

*---Report with selection screen and to display the list of
possible entries for field 'B' as per the value in field 'A'.
parameters: p_vbeln type vbak-vbeln,
            p_posnr type vbap-posnr.
at selection-screen on value-request for p_posnr.
data: begin of help_item occurs 0,
          posnr type vbap-posnr,
          matnr type vbap-matnr,
          arktx type vbap-arktx,
        end of help_item.
data: dynfields type table of dynpread with header line.
dynfields-fieldname = 'P_VBELN'.
append dynfields.
call function 'DYNP_VALUES_READ'
       exporting
            dyname               = sy-cprog
            dynumb               = sy-dynnr
            translate_to_upper   = 'X'
       tables
            dynpfields           = dynfields
       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.
read table dynfields with key fieldname = 'P_VBELN'.
p_vbeln = dynfields-fieldvalue.
call function 'CONVERSION_EXIT_ALPHA_INPUT'
       exporting
            input = p_vbeln
       importing
            output = p_vbeln.
select posnr matnr arktx into table help_item
                 from vbap
                      where vbeln = p_vbeln.
call function 'F4IF_INT_TABLE_VALUE_REQUEST'
       exporting
            retfield    = 'POSNR'
            dynprofield = 'P_POSNR'
            dynpprog    = sy-cprog
            dynpnr      = sy-dynnr
            value_org   = 'S'
       tables
            value_tab   = help_item.

How to assign search help for an input field by fetchign values from an int

i have an input field ,
i want to assign search help for the same by fetching values from a table.
how to achieve this ?

Using the below ways you can assign search help to a field.
1) [OVS Search Help|http://wiki.sdn.sap.com/wiki/display/Snippets/OVSsearchhelp]
2) [Freely Programmed Search Help|http://wiki.sdn.sap.com/wiki/display/WDABAP/Freelyprogrammedinput+help]
3) Dictonary Help - Use the Data element for that purpose.

How to put search help for shopping cart fields.

Hello Gurus,
I need to put search help for some of the fields in shopping cart. Pls let me know do we have any standard way with out abap work. pls suggest me how to proceed.
Thanks,
kamal

Check out the field and do a mapping od the same in se11, ie field and the table from which you want to search

FM to find Search help for a table field

Similar Messages

Maybe you are looking for