Input field in "Advanced Search"

Hello Experts,
I'm setting the "Search Component Set" and "Search Option Set" in our portal, and I've a little question..
In our default "Search Option Set" I disabled the property "Enable Large Search Field" (and it works fine, the input field is not large!) BUT during the search when I go in "Advanced Search" the input field return large... Why??
Is possible to set a not large input field also in "Advanced search" ?
Thanks in advance

Ok,
in SystemAdmin > SystemConfig > ContentManagement > UserInterface > Search
you can find the "Search Component Set" and "Search Option Set".
Configuring "Search Option Set" (the default option set used is "UISearch") you can enable/disable the parameter "Enable Large Search Field", that works on input field width..
If I disable this parameter the input field of my toolArea is short, but if go into "Advanced Search" the input field change and became large...

Similar Messages

Bug after adding fields in advanced search mode of af:query

We are migrating from JDeveloper 11.1.1.6 to 11.1.1.7.
I noticed the following issue:
In a page with search criteria (based on a view object), when the user adds an additional field in advanced search mode and clicks on a full submit button in the page, the following browser popup appears:
"This page is asking you to confirm that you want to leave - data you have entered may not be saved."
This was logged as a bug in Oracle Support but we have not been able to find a workaround yet.
This is the only issue currently blocking us from migrating to 11.1.1.7. Has anyone else faced this issue? Any ideas on how we can bypass this behavior?
Thank you,
Gabriel.

Unfortunately, the latest update from Oracle Support was that they no longer consider this a bug!
SR 3-7706485141: Additional Fields in af:query problem - JDeveloper 11.1.1.7
Bug 17346704 - ADDING FIELD TO AF:QUERY ADVANCED SEARCH CAUSES SPURIOUS WARNING DIALOG POPUP
1. I cannot understand how something that blocks user actions and cannot be bypassed in any way could be considered "acceptable behavior".
2. I also do not understand how a Bug can be lodged and then have its status changed to "Not a Bug".
3. Even if we were to ignore this issue and convince our customers that they should be delayed by meaningless popups while working (which we cannot), their is still another issue that makes this functionality dysfunctional. When the user clicks on "Stay on Page" the popup closes and the page freezes and becomes unresponsive.
Off course this is another issue and a different SR should open, but I think it shows that something is going very wrong with this functionality.
I wonder if anyone else is considering using JDeveloper 11.1.1.7.0 in a production system.

Removing standard operators for a field in Advanced search

Hi,
JDev 11.1.1.3.
In ADF application, we need to remove few standard operators from the list for a field in Advanced search. For this we have followed the below oracle documentation:
http://download.oracle.com/docs/cd/E14571_01/web.1111/b31974/web_search_bc.htm#ADFFD2457
27.3.3 How to Create Custom Operators or Remove Standard Operators
As specified in the doc, we have added the below "CompOper" tag to VO.xml. We have to remove all the operators present in the list except the "Equal to". But the issue is, using below code the "Not between" and "contains" operators are deleted from list, but "Not equl to" is still getting displayed. We have also tried "Doesnotequal". I have tried the oper string with spaces, without spaces, spaces replaced by underscore.
Can some one please provide the exact String to be passed in oper attribute of CompOper for all operators?
<ViewCriteriaItem
Name="CmLookupTypesVOCriteria_vcrow16_Category"
ViewAttribute="Category"
Operator="="
Conjunction="AND"
Required="Optional"
UpperColumns="1">
<CompOper Name="Category" ToDo="-1" Oper="NOTEQUALTO"/>
<CompOper Name="Category" ToDo="-1" Oper="NOTBETWEEN"/>
<CompOper Name="Category" ToDo="-1" Oper="CONTAINS"/>
</ViewCriteriaItem>
Thanks,
Manasa Tadi

I am not able to find the list for the entire set of operators, but you could follow a simple technique to identify the exact operator to be used:
In the View Criteria editor, for any of the attribute, modify the operator to any desired value, this would update the *VO.xml,
use the same operator, if you want to hide it in advanced mode - as you have done earlier.
<ViewCriteriaItem
Name="CmLookupTypesVOCriteria_vcrow16_Category"
ViewAttribute="Category"
Operator="="
Conjunction="AND"
Required="Optional"
UpperColumns="1">
<CompOper Name="Category" ToDo="-1" Oper="NOTEQUALTO"/>
<CompOper Name="Category" ToDo="-1" Oper="NOTBETWEEN"/>
<CompOper Name="Category" ToDo="-1" Oper="CONTAINS"/>
</ViewCriteriaItem>
Thanks,
Navaneeth

Automatic KM search with no input field and no "Search" button

Hello,
I would like to make an automatic KM Search ( a kind of iview that when it loads it doesn´t show the input query field, it just shows the results of a hardcoded query string, with no need of pressing the "Search" button).
I tried to do it passing parameteres to a com.sap.km.cm.basicsearch , for example:
"ConfigFileName=Navigation.xml&StartPage=SearchPage&Validate=false&QueryString=MARADONA&layoutSetMode=exclusive "
but :
1- you have to push the "Search" button to see the results
2- it shows the input field, so user will be able the change the string.
Any suggestions? Thanks in advance.

Removing the input field is slightly more complex.
1) Duplicate the UISearch Options set (from System Admin,System Config,KM, CM, User Interface, Search, Search Options Set)
2) In your duplicated Options Set, Show Advanced Options. Deselect the option to "Enable Further Search After Quick Search". Additionally, you might want to disable some if not all these options.
3) In your search iView, set the Search Options Set parm to the name of the Option Set you created in step 1.
Hope this helps.
Regards,
Frank Nacy

Adding a new Search Field in Advance Search

Hi,
In 1 of the advance search regions, :
We have a search panel in the adv search RN. In the poplist we have say 10 fields. We can add either of these 10 fields and use for searching. Now I want to add another search field ( an attribute from a table).
Question 1 :*
How to find the underlying VO from which the search fields are coming. I saw the page ( about this page) but couldn't find anything.
Question 2:*
Suppose I get the VO (resolution from above question) , if my extra filed is not there I add it in the VO ( VO extn), now how to configure this new field to the existing search panel fields?
Thanks

Hi,
I think search fields are not mapped to any VO. If this is your standard page, check the standard controller. It might be getting values from pageContext.getparameter().
You can create a new item using 'Personalize this Page' option and extend your controller to set where clause for the same.
--Sushant

Restrict fields in advanced search

Hi,
afaik you should be able to restrict the fields exposed to the user in the advanced search with R18.
I am not able to find the place to configure this. Any hints?
Thanks in advance
Michael

Michael, tere is a new privilege called "All fields in Search and Lists" that controls if a user sees all available fields or just the ones on the record detail page.

How to disable a input field in OVS search

Hi friends,
I have crated a OVS search help for matnr.
i have two input field like matnr and mat desc.. user can enter any value and hit SEARCH..
im getting results.
Now i want to hardoced a value of matnr = 001.. and make this field read only..
how can we do it..
i just took a example of matnr and mat desc. to make u understand easily...
kindly help.
Niraja

Hi Niraja,
You can initialize the value for MATNR in the phase 1 of the eventhandler method for OVS. Try refer the code segment below. Am initializing the values for MATNR & MAKTX fields in the lines:
ls_search_input-matnr = 'D*'.
ls_search_input-maktx = '*'.
*     pass the values to the OVS component
      ovs_callback_object->set_input_structure(
          input = ls_search_input ).
Regards,
Uday
Below is the complete code from my eventhandler method:
method ON_OVS .
" declare data structures for the fields to be displayed and for the table columns of the selection list
types:
    begin of lty_stru_input,
"   add fields for the display of your search input here
      matnr type string,
      maktx type string,
    end of lty_stru_input.
types:
    begin of lty_stru_list,
"   add fields for the selection list here
      matnr type string,
      maktx type string,
    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.
field-symbols: <ls_query_params> type lty_stru_input,
                 <ls_selection>    type lty_stru_list.
data: lv_matnr type mara-matnr,
        lv_maktx type makt-maktx.
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 don't want to use the defaults (DDIC-texts)
      ls_text-name = `MATNR`. "must match a field name of search
      ls_text-value = `Material Number`. "wd_assist->get_text( `001` ).
      insert ls_text into table lt_label_texts.
      ls_text-name = `MAKTX`.
      ls_text-value = `Material Description`.
      insert ls_text into table lt_label_texts.
      ls_text-name = `MATNR`. "must match a field in list structure
      ls_text-value = `Col1 -> Material Number`. "wd_assist->get_text( `002` ).
      insert ls_text into table lt_column_texts.
      ls_text-name = `MAKTX`. "must match a field in list structure
      ls_text-value = `Col2 -> Material Description`. "wd_assist->get_text( `002` ).
      insert ls_text into table lt_column_texts.
      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    = 10 ).
    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 ).
" Setting the default values to be displayed in the selection screen
    ls_search_input-matnr = 'D*'.
    ls_search_input-maktx = '*'.
"     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.
      assign ovs_callback_object->query_parameters->*
                              to <ls_query_params>.
      lv_matnr = <ls_query_params>-matnr.
      lv_maktx = <ls_query_params>-maktx.
replace all occurences of: '*' in lv_matnr with '%',
                           '*' in lv_maktx with '%'.
select a~matnr
       b~maktx into corresponding fields of table lt_select_list up to 10 rows
                 from mara as a inner join
                 makt as b on a~matnr = b~matnr where
                 ( a~matnr like lv_matnr and b~maktx like lv_maktx and b~spras = 'EN' ).
"     call business logic for a table of possible values
"     lt_select_list = ???
      ovs_callback_object->set_output_table( output = lt_select_list ).
    when if_wd_ovs=>co_phase_3.
"   apply result
      assign ovs_callback_object->selection->* to <ls_selection>.
      if <ls_selection> is assigned.
        ovs_callback_object->context_element->set_attribute(
                               name = `MATNR`
                               value = <ls_selection>-MATNR ).
        concatenate 'Description from MAKT:'
                    <ls_selection>-MAKTX
                    into <ls_selection>-MAKTX separated by space.
        ovs_callback_object->context_element->set_attribute(
                               name = `MAKTX`
                               value = <ls_selection>-MAKTX ).
      endif.
endcase.
endmethod.

SRM 7 Add a field to Advanced Search

Hi,
we have a requirement, where I need to add a feild on the advanced search screen. Are there any BADis to acheive this.
Any info on this is highly appreciated.
Thanks and Regards,
Krishna

Hi Siva,
Thank you for the response.
Can you please elaoborate this. Like how you renamed the standard field, how to find out which structure needs to be appended. A step by step guidance if you have time on this will really help me ...
Looking forward to here from you again.
Believe me , you will be highly appreciated for the info.
Thanks in advance,
Krishna

Dynamic Search Helps In An Input Field

Hi Experts,
          I need to populate an input field with different search helps based on the user action i.e when user selects "Audit" i hav to show the audit search help for my input field, when he selects "Audit Plan" i would hav to show audit plan search help.
My Questions >
1> i intend to use the method set_attribute_value_help of the interface if_wd_context_info and do the coding as :-
data lo_nd_info type if_wd_context_node_info.
lo_nd_info = lo_nd->get_node_info( ).
CALL METHOD lo_nd_info->set_attribute_value_help
        EXPORTING
          name            = 'identification' (attribute Name)
          value_help_mode = '121'
          value_help      = 'plm_auditplan'.(Help Name)
Is this the correct way to go if not plz suggest a more appropriate method.
2> in the context for that attribute ,what should i specify for the property input field
    Input Help Mode
    i.e should it be deactivated , automatic or should i give the dictionary serach help and specify one of the search helps by giving its name.
Your responses will be greatly appreciated,
Chaitanya.

Hi Ebru,
Yes, it is possible using OVS, freely programmed and dictionary help.
For OVS, refer this blog: /people/shruti.rathour/blog/2008/05/05/ovs-help-in-web-dynpro-abap
For Dictionary Search Help, refer http://help.sap.com/saphelp_nw70/helpdata/EN/47/9f724642314aabe10000000a42189b/frameset.htm
For freely programmed, refer:
http://help.sap.com/saphelp_nw70/helpdata/EN/47/9ef8cc9b5e3c5ce10000000a421937/content.htm
I hope it helps.
Regards
Arjun

Advanced Search Interception

I've got an Advanced Search that I need to intercept and do some pre-processing of the
search criteria before search executes.
I'd first like to add a input field to the Advanced Search UI that is not part of the
view object attached to the Advanced Search model. If the user submits search data in
this "new" field, I'd like to intercept that input data and use it to execute a query
programmatically against a different view object. The results of this query will then
"auto-populate" one of the other fields in the Advance Search model.
In my AppModuleImpl, I notice the following method in my JHS generated application:
public void advancedSearch(String viewObjectUsage, ArrayList arguments)
super.advancedSearch(viewObjectUsage, arguments);
I know I can "intercept" the Advanced Search process at this point, have access to any
search input data from the user via the ArrayList of QueryArguments, and since this is in my
AppModule, I also have programmatic access to my other view object.
I have two things I don't understand how to do:
(1) Add a "new" input field to the searchBean from my UIX Advanced Search page, so that I can
capture my "new" non-model search field.
(2) Create and add a new QueryArgument programmatically and add it to the ArrayList before calling
the super.advancedSearch(..) method. Specifically, the QueryArgument constructor takes some args
that I'm not familiar with (since JHS I think typically does this behind the scenes). Once my
"new" query field is added to the searchBean (from (1) above), I can use this data to execute a
query against another view object programmatically, and the results from that query will feed a
a new QueryArgument that I'd want to programmatically build and add to the ArrayList.
Are there any examples or tutorials of how to do this?
Thanks,
Timothy

Timothy,
The easiest way to do this, is to add a transient attrbute to the VO to get the additional input field in your search area. This attribute should have the queryable checkbox, but does not match a column in the underlying VO table.
When you generate your app, JHeadstart will then add a search field for this transient attribute, and it will create a QueryAttribute for it when you press Find button. Then, by overriding advancedSearch in your app module, you can get this QueryAttribute from the arraylist argument and do your preprocessing.
Steven Davelaar,
JHeadstart Team.

How to restrict columns in Advanced search which are known at runtime

Hi Team,
I need your suggestions for one of my adf search usecase. I had Querypanel with table on UI...where in Viewobject has relations with 2 other tables and this Viewobject is based on Entity...now in advanced search for addfields i was getting all column names by default like 3 tables column names....instead of all columns i need to restrict to particular columns. This particular columns will be decided at runtime like how many columns needs to be shown and alias names for those particular columns. So could you please help me how to approach this requirement.
Thanks in Advance for your help.

whatever you said is at designtime wherein we can uncheck the Queryable checkbox....but as i said at runtime from the application i can come to know whichever fields needs to be there and alias names for columns for add fields in Advanced search...

Advanced Search-Clearing search criteria

Hi,
I am developing apps using JDev 10.1.2. and JHS build 32.
My problem is with using the Advanced Search on page with table layout.
The Advanced Search contains one lookup field (a lamp).
When I enter something in the lamp field and press Find button I get proper result.
Then I run Clear. All field from Advanced Search region are cleared.
Then I run Find and I get question similar to "You are about to leave page without commiting changes...". I choose OK and the lamp field get the old value and the result is incorrect.
What is wrong?
regards,
Cezary

Cezary,
This is indeed a bug in JHeadstart, thanks for pointing this out. The fix will be present in the next release, but for now you and anyone running into it will have to apply a workaround: in the UIX page, locate the "FindXXX" field that has this problem. It will be easy to find because its name is suffixed with "_No_Update". This is incorrect (for the find field, it is OK for the actual form and/or table field!!). Remove the suffix NoUpdate and all should be well again.
Hope this helps,
Peter Ebell
JHeadstart Team

Outlook advanced search & Exchange 2013 - "Sent to...." field doesn't work correctly in online mode?

Hello,<o:p></o:p>
We've come across what seems to be a problem with advanced find in Outlook in online mode, when used with Exchange 2013.
Using the "Messages" tab of "Advanced Find", anything typed into the "Sent to...." field produces no search results. If the field is populated by clicking
"Sent to..." and selecting a name from a contact list or GAL, results are returned.
eg.
Sent items contains messages to "Charlie" who has the email address
[email protected] and sender is
"Dave" who has the email address
[email protected]
Entering "charlie" or
[email protected], (or any previously acceptable partial term such as "charl" or "@contoso.com") into the "Sent to"" field produces no results. If the user exists in a contact
list and is selected from it, the search works fine. The same is true searching the inbox, using the local user's id of "Dave" or
[email protected]
We've confirmed this issue occurs at four client's sites, plus our own internal Exchange 2013 CU3 system. Four of the sites have been transitioned from Exchange 2010, the fifth was a completely new installation. The problem occurs with Outlook
2007, 2010 and 2013.
This works fine in cached mode (not a solution as our clients are predominantly Citrix/RDS). Exchange search doesn't report any issues and the index states are all "healthy",
we've also tried rebuilding the indexes with no improvement.
Any ideas would be appreciated, or even if someone else can confirm they see the same thing.
Thanks.

Hi Winnie,
Thanks for your reply, and I'm sorry I've not responded earlier. While this problem is one that's annoying several of our clients, and while I have been doing further testing and investigation, it's had to take a back seat to other more pressing issues
until now.
OWA search works fine, as does using "From:" in instant search, and the "From" query on the Advanced tab in Advanced Find. The search services have been restarted, indexing state and copy status etc are all healthy, the indexes
have been rebuilt/reseeded, and I've gone through the diagnostics again. Nothing is logged in event viewer, and the only error that comes up when checking failed index docs for a user are for unsupported format handlers (.png etc).
The issue seems purely to be with the "Sent to..." field on the Messages tab, it's as if it gets completely ignored. The search returns instantly with "There are no items to show in this view". Just to make sure I wasn't losing
my marbles, I've compared searches on Exchange 2007 and 2010, and on those I can enter as little as a single letter or email domain and receive the expected results. On 2013 I get nothing whatsoever whatever I enter, unless I pick an address from a contact
list.
At this point, I thought that since Office 365 is Exchange 2013 based it'd be worth testing that, and sure enough I got exactly the same issue. I setup an Office 365/Outlook 2010 profile on a machine that is currently in an existing Exchange 2010
environment where search works correctly, searching Office 365 doesn't work on that either.
EDIT - Ignore this bit, a fresh install of Windows 7 and Office 2010 doesn't work with Office 365 either. I am exploring another avenue. I setup a fresh Windows 7 VM, installed Office 2010 and connected that to Office 365, search worked fine,
so I'm now looking into what the difference with that VM and the servers and workstations out "in the wild" could be. For example, the test VM isn't on a domain, it's not fully patched, it has no additional software installed etc. Outside
of Microsoft applications and operating systems and having similar configurations, I haven't isolated a common link across all of our client sites that are affected, there's no single 3rd party application or anti-virus solution in place at all of them for
example.
I'll update with any findings, but if you or anyone else has any idea in the meantime I'd be grateful for your input.
Regards.

Search help for input fields in a screen

Hi,
Pls help me
how to set search help property for the I/O fields in screen in se80?
1. do we want to add any property for search help in the property window?
2.do we want to create a MODULE PROCESS ON VALUE REQUEST ?
PLS tell me how to set search for the I/O field in se80?pls tell me the process?
i want to set the search help for more I/O fields in se80 but all the fields belongs to the same table?
can i create a single search for all these fields and use that for all the I/O fields ?
elementary search help or collective search help?
thanks & regards in advance,
vsnl.

Hi,
Input Help on the Screen
Within the Screen Painter, you can define two types of input help:
1. The FIELD statement with one of the additions VALUES or SELECT.
2. Linking a search help directly to a screen field.
If you link a search help directly to a screen field, it overrides the additions of the FIELD
statement. However, the input check [Page 581] functions of the FIELD statement remain
unaffected.
Input Help in Flow Logic
The following input help methods are obsolete and should not be used. They are still supported
for compatibility reasons.
In the screen flow logic, you can specify a value list for a screen field <f> as follows:
FIELD <f> VALUES (<val1>, <val2>,...).
The value list contains a series of single values <vali>. The NOT and BETWEEN additions for the
input check [Page 581] are not appropriate for input help.
You can also create a value list by accessing a database table as follows:
FIELD <f> SELECT *
FROM <dbtab>
WHERE <k1> = <f1> AND <k2> = <f2> AND...
In the WHERE condition, the fields of the primary key <ki> of the database table <dbtab> are
checked against the screen fields <fi>. The WHENEVER addition, used with input checks [Page
581], is not necessary for input help.
If you have used a ABAP Dictionary reference for field <f>, the selection and the hit list formatting
may be affected by any check table attached to the field.
Attaching a Search Help
Search helps from the ABAP Dictionary can be attached to a screen field [Ext.]. To do this, enter
the name of the search help in the corresponding field in the attributes of the screen field in the
Screen Painter. This assigns the first parameter of the search help to the screen field. It is only
possible to place a value from the hit list onto the screen.
Input help on a screen.
REPORT DEMO_DYNPRO_F4_HELP_DYNPRO MESSAGE-ID AT.
DATA: CARRIER(3) TYPE C,
CONNECTION(4) TYPE C.
CALL SCREEN 100.
MODULE CANCEL INPUT.
LEAVE PROGRAM.
ENDMODULE.
The next screen (statically defined) for screen 100 is itself. It has the following layout:
602 April 2001
Cancel
Airline
Flight number
Screen field with search help
Input help in the flow logic
The input fields have been adopted from the program fields CARRIER and
CONNECTION. The function code of the pushbutton is CANCEL, with function type
E. The search help DEMO_F4_DE with the search help parameter CARRID is
assigned to the screen field CARRIER. The search help uses the database table
SCARR.
The screen flow logic is as follows:
PROCESS BEFORE OUTPUT.
PROCESS AFTER INPUT.
MODULE CANCEL AT EXIT-COMMAND.
FIELD CARRIER VALUES ('AA', 'LH').
FIELD CONNECTION SELECT *
FROM SPFLI
WHERE CARRID = CARRIER
AND CONNID = CONNECTION.
When the user chooses the input help for the individual fields, the following input
help is displayed:
For the Airline field, the search help displays the names of the airlines and places the airline
code in the input field for the chosen line. If the airline code is not one of those listed in the
VALUES list of the screen flow logic, the input check triggers an error message in the PAI
event. So the search help overrides the VALUES addition for the input help, but not for the
input checks. This is therefore not an appropriate place to use the VALUE addition.
For the Flight number field, the flow logic displays the selected entries from the database
table SPFLI and places the selected line in the input field.
Regards,
Bhaskar

How to implement SEARCH HELP for input field in WDA

Hi All,
I am doing a tool for my team. in this tool there are 4 input fields to show different processes. I implemented the 4 input fields and also bind the respective tables to these fields successfully. Actually I want to filter the data between 2 fields . Means the data in the 2nd input field should be based on the 1st input field. Means when I'll select for example 'CHI' (code for CHINA) in the 1st input field the 2nd field meant for country name should show all country name with value 'CHINA'. But the problem is that all values related to each field are in different table with no foreign key relationship and also some combinations are in single table..
I have tried the import and export parameter method for search help but no luck till now.
Can anyone please suggest me how to implement this scenario..
Thanks in advance...
sekhar

Hi sekhar,
Your Requirement can be implemented by OVS(Object Value selector) This is the custom search help .So that you can define on what basis the value has to be fetched.
Look at the below link
http://wiki.sdn.sap.com/wiki/display/WDABAP/ABAPWDObjectValueSelector(OVS)
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/606288d6-04c6-2c10-b5ae-a240304c88ea?quicklink=index&overridelayout=true
You need to use the component WDR_OVS.
It has 3 phases
In phase 1
     You will fetch the value from input field to F4 help dialog box.
In phase 2
     You will generate the search results , in this phase look for the input value given in field 2 and accordingly generate search result for the field 3.
In phase 3
     The selected value will be returned to the original screen.
Regards
Karthiheyan M

Input field in "Advanced Search"

Similar Messages

Maybe you are looking for