Search Help : brief description of what is it possible

Hello,
I need some helps about search helps with abap webdynpro. I understand with little test that automatic option and search help option have some difficulties ... Integration with DDIC and webdynpro is difficult, I understand, so my questions are...
- I have a easy requirement : a search help that displays a code from table and the description coming from text table. What is the best way to do it ? OVS ? Specific Component ? It is possible with dropdowbykey to display the code and a text whe we select it ?
- Other little question : Anybody knows a good cookbook for OVS implementation ?
I would like to implement these requirements by an easy workaround.
Thanks all for your answer and I hope this question helps other persons with the same requirement...
Best regards

Hi,
If you want to have only codes in search help, then for the context attribute associate the structure field which has check table associated to it. Then the framework will bring the values from check table, automatically. You can check if the check table is associated to attrbite by checking input help mode property of context attribute.
But if you wanto have text table values (text and values), then one option is to create the search help and associte it to the context attribute by using the property Dictionary search help.
Another way is to have OVS if you do not want to create new search help, some documentation for OVS:
<a href="http://help.sap.com/saphelp_nw70/helpdata/en/30/d7fa41c915da6fe10000000a1550b0/frameset.htm">http://help.sap.com/saphelp_nw70/helpdata/en/30/d7fa41c915da6fe10000000a1550b0/frameset.htm</a>
An example for OVS is WDR_TEST_OVS.
Best regards,
Suresh

Similar Messages

Search Help displaying description but returning ID

Hi All,
I have a textbox in web dynpro showing description (from table "Description" ) in a textbox after user selected some value from its search help.
The issue is, instead of description shown (which is correct), I want to process the value selected using its ID (from table "ID").
Both tables have child-parent relation.
Unfortunately, both "ID" and "Description" are not key. The keys for both table are GUID (another field).
Any suggested solution ?
TIA,
Tony

Hi Tony,
    In your search help try using index.
    You can use the index number to select the value.
    I have some sample code, you can use this as per your requirement.
METHOD add_data .
DATA : lt_urls TYPE if_main_view=>elements_drp_text.
DATA : lr_element      TYPE REF TO if_wd_context_node.
DATA :     url             LIKE LINE OF lt_urls.
Supply data for the node at runtime
REFRESH lt_urls[].
DO 5 TIMES.
    url-key = sy-index + 1 .
    CONDENSE url-key.
    CONCATENATE `www.` url-key `.com` INTO url-url.
    INSERT url INTO TABLE lt_urls.
ENDDO.
lr_element = wd_context->get_child_node( 'DRP_TEXT' ).
lr_element->bind_table( lt_urls ).
ENDMETHOD.
Hope this will help you.
Cheers,
Darshna.

Search help description translation for portal view

Hi Experts,
I have created a Z search help which is being called in the portal. The description of the search help text has also been maintained in user local logon language via se63 but still when viewing from portal the description is shown incorrect/different. Is there anywhere else where i need to maintain the search help text description?
thanks.

Hi Maya
Follow these steps:
1.Delete the context node/attribute which is bound to search help from the View.
2.Now Save metadata.
3.Perform Context mapping again .In the Edit Context Mapping window drag the node/attribute FROM RIGHT PANE TO LEFT PANE and select the entry.
4.Delete the Input Field from the view.
5.Save again
6.Close NWDS and reopen it.
7.Create input field again and bind it to the context element.
Hope this solves the problem.
Regards
Ananda

Creating a new Search Help on a standard SAP table field?

Good day, everyone!
As part of a report I am writing, the customer would like to have Search Help added to the AUFEX field in table AUFK. They would like this functionality so that when they are changing an order via t-code ko02, they can get a list of valid values to put in field AUFEX. I would like to tie it to a zTable I've created; in my zTable, I have just 2 fields: a key value (that will go into AUFEX) and a text description of the key value. This zTable is used in my report.
While I've created a Search Help on this table already for table maintenance, I've never added a custom Search Help to an existing standard SAP table field before. I've done some Googling and other searching to see what I need to know, but I've only been able to find information on Collective Search Helps. AUFEX doesn't yet have a Search Help field, so I don't think Collective Search Helps is my answer.
Is this possible? Can I add a custom Search Help to a standard SAP table field that doesn't have any Search Help linked to it yet? Is there an existing thread or guide somewhere that can tell me how to do this?
Thank you!

Hi
Yes u can: u can assign the search help to (A) data element livel or (B) field table livel.
After creating your search help:
A) Run SE11, insert your data element (AUFEX), press edit and insert the search help in "Search Help" area on DEFINATION tab;
B) Run SE11, insert your table (AUFK), press edit, place the cursor on your field (AUFEX) and go to GoTo->Search help->for field
But u should consider it'll mean to change a standard object for both cases: so u need to get the access key from your OSS.
Max

Field values are repeating for search help.

Hello Friends.
I have a problem. When I create a search help for a field the identical field values are repeating. What should I do to trigger only the first time.
for example:
Field-name- field-value
Supplier Nr --- Commodity
5001 -
 casting
5002 -
 casting
5003 -
 casting
So when I create the search help for commodity it is showing 'casting' 3 times in a pop-up window. It should not repeat. Can you please give me the solution what should I do?

Hi
Search helps
Standard search help
Types of search helps
Concept of search help
Search Help Interface
Dialog behavior of search helps
Selection method for search helps
Performance of search helps
Attaching search helps
Hierarchy of search helps
Standard Search Help
The input help (F4 help) is a standard function of the R/3 System. It permits the user to display a list of possible values for a screen field. A value can be directly copied to an input field by list selection.
The fields having an input help are shown in the R/3 System by the input help key to the right of the field. This key appears as soon as the cursor is positioned on the corresponding screen field. The help can be started either by clicking on this screen element or with function key F4.
If the number of possible entries for a field is very large, you can limit the set of displayed values by entering further restrictions.
Further meaningful information about the displayed values is included in the display of possible entries, especially if the field requires that a formal key be entered.
TYPES OF SEARCH HELPS
Elementary search helps
Describe a search path. The elementary search help must define where the data of the hit list should be read from (selection method), how the exchange of values between the screen template and selection method is implemented (interface of the search help) and how the online input help should be defined (online behavior of the search help).
Collective search help
Combine several elementary search helps. A collective search help thus can offer several alternative search paths.
Search Help Interface
Search help interface determines how the exchange of values between the screen template and the selection method is implemented.
The search help interface defines the context data that can be used in the input help and the data that can be returned to the input mask. Analogously to the interface of a function module, the search help interface comprises interface parameters.
When you define an interface parameter of a search help, you must also define whether it should be used to copy data to the input help (IMPORT parameter) or whether it should be used to return data from the input help (EXPORT parameter). A parameter of a search help can also have both attributes at the same time.
The location from which the IMPORT parameters of a search help get their values and the screen fields in which the contents of the EXPORT parameters of the search help are returned are defined in the search help attachment. The search help itself should always be attached to an EXPORT parameter of the search help. If this parameter is also the IMPORT parameter, its contents are only used in the input help if it is a search string (that is, if it contains a ´*´ or a ´+´).
You must define the parameter types of a search help. You can do this by assigning them data elements.
Value Transport for Input Helps
NOTE:In the above example, screen fields A, B and C are linked with parameters of the search help. As a result, values can only be transported between the screen and the search help for these three fields. Existing contents of screen fields A and B can be used for selecting the hit list since they are linked with an import parameter of the search help. The values of parameters A and C can be returned to the screen from the hit list since these parameters are declared as export parameters of the search help.
Description of dialog behavior
A hit list might contain plentiful number of entries. A
dialog provides the user with an option to restrict the
entries displayed on the hit list.
In an input help process, the set of possible entries is presented in the dialog box as a list for displaying the hit list. The user selects the required value from this list by double clicking. Since the possible entries are often formal keys, you must be able to display further explanatory information about the possible entries in the list.
If the set of possible entries is very large, the user should be able to define additional conditions for the attributes of the selected entry. Restricting the set of data in this way both increases the clarity of the list and reduces the system load. Additional conditions can be entered in a further dialog window, the dialog box for restricting values.
Specifying the dialog type of a search help defines whether the dialog box for restricting values should be offered and if so under what conditions.
The attributes in the dialog box for displaying the hit list or in the dialog box for restricting values must be defined as internal parameters of the search help. An internal parameter can also be used in only one of the two dialog boxes. It can also belong to the search help interface.
The internal parameter types are also defined with data elements. These data elements define how the parameters are displayed in the two dialog boxes.
Reward if usefull

HOW DO WE CREATRE SEARCH HELP ?

HOW DO WE CREATRE SEARCH HELP ? PLEASE EXPLAIN.
REWARD POINTS GUARENTEED !!

Hi
Input helps (F4 helps) for screen fields can be defined with search helps.
Search helps
1)Standard search help
2)Types of search helps
3)Concept of search help
4)Search Help Interface
5)Dialog behavior of search helps
6)Selection method for search helps
7)Performance of search helps
8)Attaching search helps
9)Hierarchy of search helps
Standard Search Help
The input help (F4 help) is a standard function of the R/3 System. It permits the user to display a list of possible values for a screen field. A value can be directly copied to an input field by list selection.
The fields having an input help are shown in the R/3 System by the input help key to the right of the field. This key appears as soon as the cursor is positioned on the corresponding screen field. The help can be started either by clicking on this screen element or with function key F4.
If the number of possible entries for a field is very large, you can limit the set of displayed values by entering further restrictions.
Further meaningful information about the displayed values is included in the display of possible entries, especially if the field requires that a formal key be entered.
TYPES OF SEARCH HELPS
Elementary search helps Describe a search path. The elementary search help must define where the data of the hit list should be read from (selection method), how the exchange of values between the screen template and selection method is implemented (interface of the search help) and how the online input help should be defined (online behavior of the search help).
Collective search help Combine several elementary search helps. A collective search help thus can offer several alternative search paths.
Context data: You first have to define the context data to be used in the input help process. The context contains the information obtained in previous dialog steps and the entries already made by the user in the current input mask. This information is normally used to restrict the possible values for the current input field.
Dialog behavior: It describes the order of the dialog windows to be displayed during the input help and what they should look like.
Data collection method: It defines where the values offered to the user for selection come from.
Return values: When a value is selected from the list of possible entries, it is stored in the search field. This often results in the contents of further screen fields, such as explanatory text, being updated. You therefore should define which values can be returned to the screen.
In addition to describing an input help, you must define the fields for which it should be used. This is part of the field definition (of the search fields).
In Release 4.0, the search help was introduced in the ABAP Dictionary as a new object type. A search help is an object that describes the input help process. The individual components of such a description can be defined with attributes of the search help.
Search helps are subject to the same rules concerning their maintenance, activation and transport as all other objects of the ABAP Dictionary.
Search helps provide greater flexibility and functionality for defining input helps than the matchcode and help view object types offered up to Release 3.x.
Search Help Interface
Search help interface determines how the exchange of values between the screen template and the selection method is implemented.
The search help interface defines the context data that can be used in the input help and the data that can be returned to the input mask. Analogously to the interface of a function module, the search help interface comprises interface parameters.
When you define an interface parameter of a search help, you must also define whether it should be used to copy data to the input help (IMPORT parameter) or whether it should be used to return data from the input help (EXPORT parameter). A parameter of a search help can also have both attributes at the same time.
The location from which the IMPORT parameters of a search help get their values and the screen fields in which the contents of the EXPORT parameters of the search help are returned are defined in the search help attachment. The search help itself should always be attached to an EXPORT parameter of the search help. If this parameter is also the IMPORT parameter, its contents are only used in the input help if it is a search string (that is, if it contains a ´*´ or a ´+´).
You must define the parameter types of a search help. You can do this by assigning them data elements.
Value Transport for Input Helps
NOTE:In the above example, screen fields A, B and C are linked with parameters of the search help. As a result, values can only be transported between the screen and the search help for these three fields. Existing contents of screen fields A and B can be used for selecting the hit list since they are linked with an import parameter of the search help. The values of parameters A and C can be returned to the screen from the hit list since these parameters are declared as export parameters of the search help.
Description of dialog behavior
A hit list might contain plentiful number of entries. A
dialog provides the user with an option to restrict the
entries displayed on the hit list.
In an input help process, the set of possible entries is presented in the dialog box as a list for displaying the hit list. The user selects the required value from this list by double clicking. Since the possible entries are often formal keys, you must be able to display further explanatory information about the possible entries in the list.
If the set of possible entries is very large, the user should be able to define additional conditions for the attributes of the selected entry. Restricting the set of data in this way both increases the clarity of the list and reduces the system load. Additional conditions can be entered in a further dialog window, the dialog box for restricting values.
Specifying the dialog type of a search help defines whether the dialog box for restricting values should be offered and if so under what conditions.
The attributes in the dialog box for displaying the hit list or in the dialog box for restricting values must be defined as internal parameters of the search help. An internal parameter can also be used in only one of the two dialog boxes. It can also belong to the search help interface.
The internal parameter types are also defined with data elements. These data elements define how the parameters are displayed in the two dialog boxes.
Dialog Types
The dialog type of an elementary search help defines how the hit list is displayed when the input help is called. It defines the dialog steps executed for input help.
The following dialog types are possible:
Immediate value display: The hit list is immediately displayed when the input help is called. This is only meaningful if the hit list usually only contains a few entries.
Complex dialog with value restriction: The dialog window for restricting values is offered immediately. Choose this option if the list of possible entries is usually very large. If the user limits the amount of data to be processed, the hit list will become more comprehensible and the system load during value selection will be reduced.
Dialog depending on number of values: If the hit list contains less than 100 entries, it is displayed immediately. If the hit list contains more than 100 entries, the dialog box for restricting values is displayed.
The following dialog types are possible:
Immediate value display: The hit list is immediately displayed when the input help is called. This is only meaningful if the hit list usually only contains a few entries.
Complex dialog with value restriction: The dialog window for restricting values is offered immediately. Choose this option if the list of possible entries is usually very large. If the user limits the amount of data to be processed, the hit list will become more comprehensible and the system load during value selection will be reduced.
Dialog depending on number of values: If the hit list contains less than 100 entries, it is displayed immediately. If the hit list contains more than 100 entries, the dialog box for restricting values is displayed.
Selection method for Search help
Selection method refers to the database object (database
table or view) from which data is selected and displayed
in the hit list.
The possible entries displayed for a field by the input help are determined at runtime by a selection from the database. When a search help is defined, you must define the database object from which the data should be selected by specifying a table or a view as selection method.
The fields of the selection method are assigned to the parameters of the search help if their names are the same. Restricting the hit list, which is formulated with a parameter of the search help, is also used to formulate a WHERE condition for the field of the selection method having the same name (if one exists). Vice versa, the parameters of the search help appearing in the hit list are assigned the contents of the fields of the selection method having the same name.
If the selection method is a table having a text table, the non-key fields of this text table can also be used in the search help. In this case the corresponding entries of the logon language are automatically taken into consideration in the selection. These columns remain empty for values that do not have text in the logon language.
If the selection method is client-dependent, your client field may not appear as a parameter of the search help. The search help is always selected in the current client.
Performance of an Input help
We must ensure that the hit list is displayed in minimum
time with minimum load on the system.
It is imperative to optimize accessing behavior especially when selection uses a view and thus more than one table.
This can be done by restricting the hit list
By additional restricting conditions from the context.
Restricting conditions entered by the user in a dialog.
Performance of the input help could be greatly improved by creating an index on the fields used to formulate the restrictions.
A large amount of data sometimes has to be searched in the selections for an input help. This means that the user might have to wait a long time for the possible entries to be displayed, and can also result in a significant increase in the load on the system.
When defining a search help, you should therefore check whether you should take measures to optimize the accessing behavior for the selection method. This is especially true if the selection uses a view and thus more than one physical table.
If the number of entries in the selection method is very large, you should restrict the hit list with further conditions. This also increases the clarity of the hit list. The additional conditions can directly result from the context, or can be entered in the dialog box for restricting values by the user. The performance of the input help can frequently be significantly improved by creating an index on the fields used to formulate the restrictions.
If a restriction is defined with the secondary table of a help view, the selection is automatically performed as an inner join. In this case you should replace the help view with a database view.
Attaching a search help to a field
A search help can influence the behavior of a field when the input help is called. The search help must be assigned to the field in order to do this. You have the following options for this assignment:
Attach search help to a data element / table or structure field / screen field / check table.
Conventionally search helps are attached to table fields or data elements. We shall see the same.
Choose the field name, click on search help tab and
provide the name of the search help.
A search help is attached to a field of a table or structure in the maintenance transaction for this table/structure, analogously to attaching to a table. You must assign the interface parameters of the search help to any fields of the table/structure. The search field must be assigned to an EXPORT parameter of the search help at this time.
Attach the search help to the table field
The search help ZSTRAVELAG_NAME is therefore directly attached to the field AGENCYNUM of table ZSTRAVELAG.
Provide the search help name and the parameter name
under the further characteristics tab of the data element.
If the input help of a field is defined by its data element, no further screen fields can be used in the input help.
Also note that the input F4 help would be available wherever the data element is used.
A search help can be directly assigned to a screen field in two ways.
The name of the search help must be entered in the Screen Painter in the Attributes for the field in the field Search help.
The name of the search help can be defined for selection screens in ABAP reports in the PARAMETERS or SELECT-OPTIONS statement directly following the supplement MATCHCODE OBJECT.
However, input help is only available for this particular screen.
Collective search help
A Collective search help provides alternative search
Paths by combining elementary search helps.
Only one search help can be attached to a field, table or data element. Several search paths are therefore attached with a collective search help.
A collective search help also has interface parameters like
an elementary search help.
Like an elementary search help, a collective search help has an interface of IMPORT and EXPORT parameters with which the search help exchanges data. Using this interface, the collective search help can be attached to fields, tables and data elements exactly like an elementary search help.
Parameter assignment needs to be done for each of the
Included search helps.
When you define a collective search help, there are no components for describing the dialog behavior and data selection; instead the included search helps are listed here. You must assign the parameters of the collective search help to the interface parameters of the included search help for each inclusion.
User may choose the tab and thus the elementary
search method.
When we execute the search help SCUSTOM, we are confronted with a dialog which gives us an option of either restricting
By 1)Search for customer according to booking
2)Search for customer according to name.
These are effectively the elementary search helps (SCUSTOM_BOOK and SCUSTOM_NAME) which have been included in the collective search help SCUSTOM.
HOT KEY
The hot key is used to select the elementary search help from the collective search help and to enter the restrictions in the dialog box for restricting values directly from the entry field. If the user often searches for values using the same search help, this procedure can save time.
Reward if usefull

How to create Search help exit, and then assign it to a collective search

hi gurus,
i have an intersting question for you, well my scenario is like i have to create a search help exit using some function module cause i didt found table for my search help but i can find the value through FM, i know we can create a search help exit and then assign it to collective search help,
my problem is what are the parameters i need to pass to this search help exit FM, and in the function module i want to use the value entered on the f4 selection screen to extract data through FM. i need to give a solution asap.
any reply will be highly appreciated
n rewards points for sure.
thanks mandy

Hi mandy,
Have a look at this code,
FUNCTION SHLP_SHOW_LIST.
""Local interface:
*" IMPORTING
*"     VALUE(PLANT) TYPE WERKS_D OPTIONAL
*"     VALUE(DISPLAY_ONLY) TYPE FLAG OPTIONAL
*" EXPORTING
*"     REFERENCE(ITEM_SELECTED) TYPE CHAR20
*" EXCEPTIONS
*"      POPUP_CANCELED
TYPE-POOLS SHLP .
CONSTANTS:
        co_shlpname            TYPE shlpname   VALUE 'SHLP_CONTAINER',
        co_shlpfield_itemalias TYPE ddshlpsfld VALUE 'CONTAINER'.
DATA: l_shlp         TYPE shlp_descr_t,
        l_subrc        TYPE sysubrc,
        l_return_tab   TYPE STANDARD TABLE OF ddshretval,
        l_return_wa    TYPE ddshretval,
        l_interface_wa TYPE ddshiface.
Get details for search help
CLEAR l_shlp.
l_shlp-shlpname = co_shlpname.
l_shlp-shlptype = 'SH'.
CALL FUNCTION 'DD_SHLP_GET_HELPMETHOD'
       CHANGING
            shlp = l_shlp.
Assign virtual screen field
READ TABLE l_shlp-interface INTO l_interface_wa
WITH KEY shlpfield = co_shlpfield_itemalias.
l_interface_wa-value      = space.
l_interface_wa-valtabname = 'X2'.    "virtuel screen field
l_interface_wa-valfield   = 'Y2'.    "virtuel screen field
MODIFY l_shlp-interface FROM l_interface_wa INDEX sy-tabix.
Call F4 popup
CALL FUNCTION 'F4IF_START_VALUE_REQUEST'
       EXPORTING
            shlp          = l_shlp
            disponly      = display_only
       IMPORTING
            rc            = l_subrc
       TABLES
            return_values = l_return_tab
       EXCEPTIONS
            OTHERS        = 0.
IF sy-subrc = 0 AND l_subrc = 0.
Value selected
    READ TABLE l_return_tab INDEX 1 INTO l_return_wa.
    item_selected = l_return_wa-fieldval.
ELSE.
Popup canceled / no value selected
    RAISE popup_canceled.
ENDIF.
ENDFUNCTION.
make sure to call these FMs and populate accordingly...
Thanks
Madhu

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

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

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

How to validate a filed in a search help which is created in se11

hi
i got a requirement that validate a search help. i created a ztable with 3 fileds for that one i have to create a search help so help me to how to validate fields in a search help.
regards
krishna

Hello Krishna,
What do you mean by validating a field? Usually you use a search help to display possible values for a certain input field based on values in another table. You can restrict the values that are displayed by certain conditions if you need to.
If you want to allow only values based on complex conditions or authorizations of the user, you can always create a search help exit and in there you have complete control over what the user is allowed to see in the search help and what he is allowed to select.
Function Module F4IF_SHLP_EXIT_EXAMPLE gives you an idea what you can do in a search help exit.
Regards,
Michael

F4 search help

Hi,
I have created some custom fields for shopping cart cost assignment. The custom fields have been added to the structure INCL_EEW_PD_ACC_CSF.
Now in the web the fields are displayed under cost assignment with a search help (binocular icon) next to each custom field.
The problem is that when the user clicks on the F4 search help (binocular icon), we would like to fetch the data from R/3 and display the data. Is there any badi which is triggered on click of the F4 search help (binioculars) for custom fields so that we can retrieve the data from R/3 and display possible values?
Is there any other way/approach to achieve this requirement, then please share.
Thanks and Regards,
Jayesh

Thanks Pierre.
What we need is that on click of F4 search help, we want to retrieve the data from R/3.
So in the elementary search help that we have created what should be the value in the selection method? Usually it is the name of a table from which we are going to retrieve the data. But since the table is an R/3 table, and the search help is in SRM, what table should we give in the search help?
Regards,
Jayesh

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

Search Help In ALV Grid

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

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

Populating drop down with search help

I have drop down to populated in WD,but i dont want it to be populated with the field values from ddic,instead iwant the the search help values for this field in the ddic.Say for example i have the Carrid field with values AA,BB and so on in the ddic table and in the search help d description is there like for AA->american airlines and so on .so i dont want to populate my drop down with aa,instead i want american airlines.Please advice.

you can try this ,
1.after creating the attribute which you wanna populate in the context of your node .
2.Go to do inint method of your view and try using the code below with node and attributes which you need.
method wddoinit .
data:     rootnode_info type ref to if_wd_context_node_info,
      rootnode_info1 type ref to if_wd_context_node_info,
      it_value_bet type table of wdr_context_attr_value.
     " node_arrid type ref to if_wd_context_node_info.
rootnode_info = wd_context->get_node_info( ).
" ADD A CHILD NODE TO THE ROOT.
call method rootnode_info->get_child_node
exporting
    name       = 'ARRANGEMENT_ID'
receiving
    child_node = rootnode_info1.
data:    lt_valueset type wdr_context_attr_value_list ,
      l_value type wdr_context_attr_value.
" fill up internal table from table***********************
data : itab_pa_id type standard table of /sappssrm/pa_idt,
       wa_sappssrm_pa_id like line of itab_pa_id.
select * from /sappssrm/pa_idt into table itab_pa_id.
loop at itab_pa_id into wa_sappssrm_pa_id.
   l_value-value      = wa_sappssrm_pa_id-arrangement_id.
   l_value-text    = wa_sappssrm_pa_id-description.
insert l_value into table lt_valueset.
endloop.
I guess this should help .
Regards,
Abhishek

Search help window opening two times

Hi folks,
i found one of wda application is integrated into portal.on portal side if i press on search help symbol then it opened external window two times.How can i make that to one window

External windows are never used by search help becuase they open in a separate user session - making data communication back and forth very difficult. When modal windows are triggered, the parent window is frozen and no longer accepts input.
When you say external window, what are you seeing. Is it actually a separate browser window that can be dragged outside the confines of the parent window. If this is really an external window, then it doesn' seem like this is a search help.
Have you studied the WD Component. Can you see what kind of search help this is. What triggers it? A normal button or the search help button attached to an input field.

Predefine values for search-help of GL-Account

Hello,
we're using SRM on an ERP-backend. Within the shopping-site you can define the GL-Account (SAKTO) which also has a search help. In ERP i predefined the values used in the search-help (KTOPL, PLANT etc) by using a search-help exit. Now i need todo the same in SRM but i cant find the right place todo that.
I dont even find a search-help that might be used for that. Does this work differently in SRM ? Does that all goes over the backend ?
Could someone lease help me by telling how can i set these values for the search-parameters of the search-help and maybe also whats the name of the search-help of GL-Account in SRM ?
Thanks alot...any help will get rewarded.
oliver

Hi Oliver,
Check the Search Help BADIs below:
a. You can use this Business Add-In (BAdI) BBP_F4_READ_ON_ENTRY to influence the display of input and search helps and to control the favorites for display fields. The processing is only available for data elements for which input helps exist on HTML templates. In this way, you can define field values for an input help and define the number of field values too.
b. You can use the Business Add-In (BAdI) BBP_F4_READ_ON_EXIT to restrict (or augment) the list of values and favorites that are output in the input and search helps. You can only process data elements for which input helps exist on HTML templates. The following three BAdIs are also available:
Navigate through SRM Server> Technical Basic Settings> Business Add-Ins (BAdIs)> Interface Configuration> Input Helps and Search Helps...
Cheers.

Search Help : brief description of what is it possible

Similar Messages

Maybe you are looking for