Designing LOV Query Problem

Hello APEX people,
I posted my problem here:
Designing LOV Query Problem
What I have is a sequence like this:
CREATE SEQUENCE
DR_SEQ_FIRST_SCHEDULE_GROUP
MINVALUE 1 MAXVALUE 7 INCREMENT BY 1 START WITH 1
CACHE 6 ORDER CYCLE ;
What I need would be a SQL query returning all possible values oft my sequence like:
1
2
3
4
5
6
7
I want to use it as a source for a LOV...
The reason why I use the cycling sequence is: My app uses it to cycle scheduling priorities every month to groups identified by this number (1-7).
In the Admin Form, I want to restrict the assignment in a user friendly way - a LOV.
Thanks
Johann

Here ist the solution (posted by michales in the PL/SQL forum):
SQL> CREATE SEQUENCE
dr_seq_first_schedule_group
MINVALUE 1 MAXVALUE 7 INCREMENT BY 1 START WITH 1
CACHE 6 ORDER CYCLE
Sequence created.
SQL> SELECT LEVEL sn
FROM DUAL
CONNECT BY LEVEL <= (SELECT max_value
FROM user_sequences
WHERE sequence_name = 'DR_SEQ_FIRST_SCHEDULE_GROUP')
SN
1
2
3
4
5
6
7
7 rows selected.

Similar Messages

LOV Query problem

I have a very huge and a lenghty LOV Query . I am using 6i builder and when i save the module and try to reopen it , Only 3/4th of the LOV query is available and the remaining disappears . I can compile this in 6i by copying the query again but it creates a problem in 10g . ie. The Fmx file is not generating in 10g.
Firstly ,
I haven no idea as to why the code disappears for no reason ? IS it because its too lenghty. I am sure there are no errors because it wouldn't have compiled if there were any .
Anybody who has come across such problems , kindly advice!
Thank you .

hii,
Create a VIEW of your query in database level and then create LOV based on that VIEW.
Regards
PS

Select List (based on LOV) query problem

Hello experts! I have a small problem here, which I can't seem to overcome.
I have a page item (select list based on LOV), which is based on a query. The query returns all potential employees of a department that are responsible for a certain duty. So far so good!
The problem is that there are two departments, which should not only see there own employees but also the name of the employee that has carried out a certain task. However, due to my query, the name of that person is not displayed - only the pk is returned.
Do you have a recommendation how I display all employees of a specific department and have additional values translated as well?
My query is as follows: select str_bearbeiter, cnt_bearbeiter from vt_tbl_bearbeiter where cnt_bearbeiter in (SELECT
CNT_REGIERUNGSBEZIRK FROM TBL_REGIERUNGSBEZIRK) union select str_bearbeiter, cnt_bearbeiter from vt_tbl_bearbeiter where int_behoerde in (SELECT
CNT_REGIERUNGSBEZIRK FROM TBL_REGIERUNGSBEZIRK where STR_REGIERUNGSBEZIRK = lower (:app_user)) whereas :app_user holds the information of the department.
Any hint is appreciated!
Many thanks,
Seb

Okay, I just had the right idea and it's working well! Sorry for posting!
I return the name of the employee that has edited a dataset and simply add all others of the logged on department! Really easy! Should have thought of that before posting! ;-(
The correct code is select str_bearbeiter, cnt_bearbeiter from vt_tbl_bearbeiter a, vt_tbl_punktdaten b where a.cnt_bearbeiter = b.int_bearbeiter and
inv_pt_id_sub = :P4_PTIDS
union select str_bearbeiter, cnt_bearbeiter from vt_tbl_bearbeiter where int_behoerde in (SELECT
CNT_REGIERUNGSBEZIRK FROM TBL_REGIERUNGSBEZIRK where STR_REGIERUNGSBEZIRK = lower (:app_user))Bye,
Seb

LOV query problem (1.6)

Hi,
I have been pulling my hair out over this one!
Background: I have an LOV that needs to return 4 different lists depending which of 4 radio buttons (P40_OPPORTUNITY_TOGGLE) has been selected, and who is logged in (FLOW_USER).
the LOV of based off two views:
* OPP_GEO_V (opportunity, sales consultant and geography for opp)
SC_EMAIL_ADDRESS
OPP_NUMBER
OPPORTUNITY
CUSTOMER
DIVISION
REGION
COUNTRY
* SC_GEO_V (sales consultant and geography for SC)
EMAIL_ADDRESS
DIVISION
REGION
COUNTRY
SALES_ACCESS
The four lists should be:
* All opportunities in the same country as the user
* All opportunities in the same region as the user (depending on SALES_ACCESS)
* All opportunities in the same division as the user (depending on SALES_ACCESS)
* Every opportunity where the user is listed against it (SC_EMAIL_ADDRESS)
The query:
select distinct o.opp_number||' - '||o.customer||' - '||o.opportunity d, o.opp_number||' - '||o.customer||' - '||o.opportunity r
from opp_geo_v o, sc_geo_v s
where
(nvl(:P40_OPPORTUNITY_TOGGLE,'C') = 'C'
AND upper(s.email_address) = upper(:FLOW_USER)
and o.country = s.country)
OR
(:P40_OPPORTUNITY_TOGGLE = 'R'
AND upper(s.email_address) = upper(:FLOW_USER)
AND s.sales_access is not null
and o.region = s.region)
OR
(:P40_OPPORTUNITY_TOGGLE = 'D'
AND upper(s.email_address) = upper(:FLOW_USER)
AND s.sales_access = 'D'
AND o.division = s.division)
OR
(:P40_OPPORTUNITY_TOGGLE = 'S'
AND upper(o.sc_email_address) = upper(:FLOW_USER))
Problem: HTML DB will time out when trying to submit this query. The strange thing is, it was functioning well until last night when I added the final OR block (opp_toggle = 'S'). If i remove the first 3 OR blocks, it will submit fine. If I remove the bottom OR block it will also submit fine. But for some reason it won't allow me to have all 4. Actually it won't allow any combination of the bottom OR block and any of the top 3...
This could be something blatantly obvious or it might just be one of those oddities, but I'd appreciate any ideas.
Thanks,
Mark

Ok I changed FLOW_USER to APP_USER, i think in this case it will be the same value (email address), and the functionality of the LOV is still the same, but if you insist =)
Now this is odd and may give an idea of what is going on.....
I have a table ALL_CLIENTS, which is one of the tables that makes up the view OPP_GEO_V (geographic_areas being the other). The fields that come from ALL_CLIENTS are:
* SC_EMAIL_ADDRESS
* OPP_NUMBER
* OPPORTUNITY
* CUSTOMER
now, if i alter the query so I pull the data from ALL_CLIENTS, and use OPP_GEO_V for looking up the geographic information for the opportunity (with a join between ALL_CLIENTS and OPP_GEO_V --- o.opp_number = c.opp_number) in each of the OR clauses, it WORKS! It sounds ridiculous that I'm joining a view with one of the tables it's based off, but i'm getting desparate here... This is probably a confusing description, so here's the query:
select distinct c.opp_number||' - '||c.customer||' - '||c.opportunity d, c.opp_number||' - '||c.customer||' - '||c.opportunity r
from opp_geo_v o, sc_geo_v s, all_clients c
where
(nvl(:P40_OPPORTUNITY_TOGGLE,'C') = 'C'
AND upper(s.email_address) = upper(:APP_USER)
and o.opp_number = c.opp_number
and o.country = s.country)
OR
(:P40_OPPORTUNITY_TOGGLE = 'R'
AND upper(s.email_address) = upper(:APP_USER)
AND s.sales_access is not null
and o.opp_number = c.opp_number
and o.region = s.region)
OR
(:P40_OPPORTUNITY_TOGGLE = 'D'
AND upper(s.email_address) = upper(:APP_USER)
AND s.sales_access = 'D'
and o.opp_number = c.opp_number
AND o.division = s.division)
OR
(:P40_OPPORTUNITY_TOGGLE = 'S'
AND upper(c.sc_email_address) = upper(:APP_USER)
and o.opp_number = c.opp_number)
As you can see, I no longer have to look up OPP_GEO_V to compare the email address in the bottom OR clause.. but why on earth would HTML DB object to me doing that? I feel like I'm looking in the wrong spot here...
The only problem with this is it's unacceptably slow. There are currently 836 sales consultant records and 95718 opportunity records, which will be growing significantly once this goes into production, so I kinda need it to be speedy!
I hope this post hasn't caused confusion ....
Mark

Oaf :lov query problem

Hi friends
In my search PG i hav 3 field in that one of the field i hav set it as lOV field
In the LOV field i click the icon one pop up screen open (ie) search and select screen .... from that list of field i hav selected one field .... it return back to my searchPG the selected item is in lov field of my searchPG ...when i click "query "button the whole whole table is seen in the result table instread of that selected item
i want oly the selected item to b displayed in the result table ... i dont want the the whole table to b displayed in the result table....
what i hav to do please help me
thanks
Thiliban

hi friend
How to bind the VO query .... //for that QueryLovVO i hav not written any coding
Capture the button in pfr // i hav capture the button press in the PRF
and bind the vo query with the lov field value //how ?
I hav changed Phoneno field as LOV field
These r my coding in the PFR of the main search PG
===================================
public void processFormRequest(OAPageContext pageContext, OAWebBean webBean)
super.processFormRequest(pageContext, webBean);
String actionInMainPersonScreen = pageContext.getParameter(EVENT_PARAM);
String personId= pageContext.getParameter("PersonId");
OAApplicationModule am = pageContext.getApplicationModule(webBean);
if (pageContext.getParameter("Query") != null)
System.out.println("Submit button pressed");
OAQueryUtils.checkSelectiveSearchCriteria(pageContext, webBean);
String firstName = pageContext.getParameter("FirstName");
String phoneNO = pageContext.getParameter("PhoneNO");
Serializable[] parameters = { personId, firstName, phoneNO};
System.out.println("AM Method is called");
am.invokeMethod("initQuery", parameters);
=====================================================
In my AM
public void initQuery(String personId,String firstName,String phoneNo)
System.out.println("In Am initQuery");
MyQueryVOImpl vo = (MyQueryVOImpl)getMyQueryVO1();
System.out.println("MyQueryVO initQuery method called");
vo.initQuery(personId, firstName, phoneNo);
====================================================
Here i hav two VO .... these is my query VO
public class MyQueryVOImpl extends OAViewObjectImpl
* This is the default constructor (do not remove)
public MyQueryVOImpl()
public void initQuery(String personId,String firstName,String phoneNo)
StringBuffer whereClause = new StringBuffer(100);
Vector parameters = new Vector(3);
int clauseCount=0;
int bindCount=0;
setWhereClauseParams(null);
setWhereClause(null);
if ((personId != null)&&(!("".equals(personId.trim()))))
whereClause.append(" PERSON_ID like :");
whereClause.append(++bindCount);
parameters.addElement(personId );
clauseCount++;
if ((firstName != null)&&(!("".equals(firstName.trim()))))
if (clauseCount > 0)
whereClause.append(" AND ");
whereClause.append(" FIRST_NAME LIKE :");
whereClause.append(++bindCount);
parameters.addElement(firstName );
clauseCount++;
if ((phoneNo != null)&&(!("".equals(phoneNo.trim()))))
if (clauseCount > 0)
whereClause.append(" AND ");
whereClause.append(" PHONE_NO like :");
whereClause.append(++bindCount);
parameters.addElement(phoneNo );
clauseCount++;
setWhereClause(whereClause.toString());
if (bindCount > 0)
Object[] params = new Object[bindCount];
parameters.copyInto(params);
setWhereClauseParams(params);
executeQuery();
===========================================
i hav created queryLovVO in LOV.Server package and i hav written no coding in that LovVO
public class QueryLovVOImpl extends OAViewObjectImpl
* This is the default constructor (do not remove)
public QueryLovVOImpl()
======================================
please help and guide me
thanks
thiliban

Problem in Dynamic LOV query

Hi,
I have a LOV in my page its query should be based on item condition.
So I tried using Apex provided Dynamic LOV Query with IF.. ELSE.. END IF condition.. But when I use this and run the page it is giving error "URL NOT FOUND".
My query is
   IF :MY_ITEM is not null THEN
   RETURN 'select ename ,eno
                from emp
                where eno = '''||:MY_ITEM||''' ';
   ELSE
    RETURN 'select ename ,eno
                from emp
                where ename = ''ALAKA'' ';
   END IF;But it is not working for me.
Please anyone help me to solve this.
Thanks
Alaka

Hi All,
It worked for me. Just I modified my code a bit. Thanks to all for help.
Just I did ,
   DECLARE
   BEGIN
         IF :MY_ITEM IS NOT NULL THEN
            RETURN 'SELECT ENAME,ENO
                        FROM EMP
                        WHERE ENAME = '''||:MY_ITEM||''' ';
       ELSE
           RETURN 'SELECT ENAME,ENO
                        FROM EMP
                        WHERE ENAME = ''ALAKA'' ';
      END IF;
      EXCEPTION
        WHEN OTHERS THEN
            HTP.PRN('ERROR'||SQLERRM);
   END;
Thanks
Alaka

How to accessing current row report column value in Lov Query?

Hi,
which access methods (eg. bind variables, substitutions, ...) for getting the current row report column value can be used in the "Lov Query" property of a report column?
As what I know of and what I have read on the forum there are no bind variables for the report columns. For the "Link Text" property it seems that the column values exist as substitution strings (#COLUMN_NAME#). But they don't work in the Lov Query. => And would be good because of a hard parse each time the Lov query is executed.
The following post (Re: Simulating a correlated sub query in lov
is showing a solution to use package variables for temporary storage of the referenced value, but the only problem with that solution is that if a new record is added with the "Add rows to tabular form" process the package variable still contains the value from the last queried row! Is there a way (variable, APEX package, ...) to determine if the lov query is executed for a new record so that the package can return null?
I know that I could write the package in a way that the value is immediately cleared when lov_pkg.keyval is called (one time read), but then I would have to create several variables if I'm accessing the value multiple times in the query or in another query => I think an one time read solution would be very obscurely.
Thanks for your help
Patrick
http://inside-apex.blogspot.com

Hi Patrick,
I agree that it's a waste to continually use Ajax to go back to the server to get the contents of a dynamic select list.
There are no bind variables for any row item - but what you do have, as per my previous post, is the value of the data entered by the user in the first row. You can pass this into your application process (using get.add("VARIABLENAME", value)), which can use it to retrieve the correct LOV in your Ajax code - this will give you a "bind variable" that your process can use.
What you could do, however, is generate hidden select lists on your page - one for each possible LOV list and replace the contents of the new row's select list with the contents of the appropriate hidden select list. This is easy to do with javascript (using innerHTML functions). Obviously, though, the usefulness of this depends on the number and size of the select lists.
Even if you don't generate them to start with, you can keep a copy of any select lists returned by Ajax in the DOM for use on new rows. So, if you have retrieved a select list, you will have a copy of it in DOM which you can then copy into the new row. If you don't have the list in DOM, use Ajax to get it, store a copy of it and copy it into the new row.
Which method you use will depend on the number/size of select lists needed. If they are few in number and/or size, I would suggest generating hidden lists. If they are large, use Ajax to get them once, store them and then retrieve them from the DOM when needed.
There is another thread here where Arie recommends going to the server every time to make sure you get the most up-to-date data for the lists. If you want to follow this advice, for this reason, use get.add("VARIABLENAME", value) to pass the value to your process. If this is not an issue, you can use one of the other methods I outlined above.
Regards
Andy

1.6 LOV query invalid, was working in 1.5

The following LOV query was valid in 1.5:
select rd.name, rd.refdata_id from refdata rd, refdata_meta meta where meta.name = 'Title' and rd.refdata_meta_id = meta.refdata_meta_id and (:20_PATIENT_ID IS NOT NULL OR visible = 'Y') order by rank
This query is being flagged as invalid in 1.6. The problem appears to be the parenthetical OR clause, since taking it out passes validation. The error message is:
"LOV query is invalid, a display and a return value are needed, the column names need to be different. If your query contains an in-line query, the first FROM clause in the SQL statement must not belong to the in-line query."
Seems to me that the validator is equating the existence of a left parenthesis with an inline query, which of course is incorrect as the above perfectly valid SQL demonstrates.
The query with the OR clause operates to populate the LOVs just fine in my existing app migrated from 1.5, so this is a maintenance and new app creation issue.
I can of course work around it by views as needed to support a simplified LOV query, but I would much rather just get the former level of functionality back. Any prospect of fixing what appears to me to be a bug in the LOV query validator for the 1.6 platform?
thanks,
susan weber

Susan,
In 1.6, we introduced LOV query validations, to help head off problems before runtime. Looks like in this case, the check has a bug. It's trying to parse your SQL as if it were a query in a region and it fails because of the item name you are using that begins with a numeric digit and is followed by non-numeric characters. Such a query fails to parse with DBMS_SQL.PARSE. But the query does work, as you know, in an LOV, where EXECUTE IMMEDIATE with a USING clause handles it okay.
So we have three bugs, the LOV query validation algorithm, the misleading validation failure message, and the bug that allows users to create and use items with names that are not valid Oracle identifiers. Thanks for pointing this out.
Your workaround is to use v('20_PATIENT_ID') instead of using bind variable notation.
Scott

Select list and subquery: "LOV query is invalid"

Hi all,
I want to create a select list with the following format:
"name1 (count of another table)"
"name2 (count of another table)"
I've boiled it down to a simple query with a non-correlated subquery that works fine in SQL*Plus but not as an LOV:
select table1.field1 || (select count(*) from table2) d,
table1.field2 r
from table1
I get this (Apex 3.2.1):
1 error has occurred
* LOV query is invalid, a display and a return value are needed, the column names need to be different. If your query contains an in-line query, the first FROM clause in the SQL statement must not belong to the in-line query.
Even this doesn't work:
select table1.field1 || (select 'a' from dual) d,
table1.field2 r
from table1
I've tried it with an inline view, joining table1 to a select from table2 that returns the count, but I get the same result. Any ideas?
Edited by: MalcA on Jan 22, 2010 12:14 PM

I don't know, but the difference is that the count(*) code goes from the select clause to the from clause.
Other times I had the same problem and always did it and it was the solution.

Binding a variable to an LOV query, not working... Urgent!

Hi,
Based on a column value(which gets populated at runtime), in a table, the LOV query for another column in the same table, should be restricted with this value.
1. My LOV is based on a VO.
Lov query is
SELECT ped.full_name as employee_name,
ped.employee_number as employee_number
FROM p_employee_details ped
WHERE ped.value = 'Y' and ped.work in (:1, 'Both')
2. For binding the variable, I have a method in VOImpl of the LOV.
public void initQuery(String p_param)
setWhereClauseParams(null);
setWhereClauseParam(0,p_param);
3. This method is called in the LOVAMImpl
public void initializeVO(String p_param)
LovVOImpl lovVO = (LovVOImpl)getLovVO1();
lovVO.initQuery(p_param);
4. In the CO for the LOV RN, the LOVAMimpl Method defined in step 3 is called.
public void processRequest(OAPageContext pageContext, OAWebBean webBean)
super.processRequest(pageContext, webBean);
OAApplicationModule lov_am = (OAApplicationModule) pageContext.getApplicationModule(webBean);
Dictionary lov_dict = pageContext.getLovCriteriaItems();
String lov_criteria = (String) lov_dict.get("work");
Serializable lov_params[] = {lov_criteria};
lov_am.invokeMethod("initializeVO",lov_params);
Here "work" is the column in the table whose value is needed for binding the lov query
But i am still getting an error saying not all variables bound.:
Developer Mode Exception : Lov Input should by default be the queryable criteria and Result.
I don't know what else to do.
Thanks in advance

HI,
Here the code giving on starting of the thread will work,only problem is lov mapping over here which was same as mine , u have to create one more lov mapping which will have criterial item same as the field on which lov is based.
Thanks

LOV Query Invalid

Hello.
I am uisng Apex 4.1 on Oracle 10.2.0.5 and Oracle App Server.
Would someone please tell me why the following LOV query is causing the dreaded error:
LOV query is invalid, a display and a return value are needed, the column names need to be different. If your query contains an in-line query, the first FROM clause in the SQL statement must not belong to the in-line query.
select d, r
from
select
'(select)' as d,
'javascript:void(0)' as r
from dual
union
select
initcap(INFO_NAME) as d,
'javascript:popUp2(''' || INFO_LINK || ''', 1000, 800);' as r
from INFO_LINKS
order by 1Running this query in the SQL Commands section returns the result set without problem.
Related to this, I've noticed that I am getting this same error for many similar LOV "complex" queries that involve things like UNIONs or sub-queries. In fact, when I bring up an already working LOV query in the LOV editor and then simply click the "OK" button without modifying the query, I get this same error. WHY?
Thanks in advance for any help on this.
Elie

Hello Everyone.
I just realized what my mistake is.
Many of the individual lines in my LOV query are ending with a carriage-return character. And so, the following code line is literally concantonated with the previous line.
Once I added one or more space characters to the end of each code line, Apex accepted the query without problem.
Whew! That was tricky, indeed.
And this is why many of my other already working queries suddenly caused the error when I clcik the OK button in the LOV editor. For some reason, bringing up these already existing, working queries stripped awawy any space characters from the very end of the code codes.
I hope this helps others facing the same issue.
Elie

LOV query is invalid, a display and a return value are needed, the column n

Hello,
I used to have no trouble at all creating dynamic LOV but from today I' am alway getting the error mentioned above.
This is the LOV query
select nm,zon_id from scr_zones_mv@d29ut
I tried to created a view of the referenced table, I'm able to select from this view in query builder but it gives the same error.
What is going wrong?
Erwin

Sorry guys,
I already found the problem.
thanks
Erwin

"FROM" in a string in a LOV query

An LOV query such as this:
select c001 || ' from ' d, seq_id r
from apex_collections
where collection_name = 'ABC'
order by 1produces this error when trying to save the LOV: "LOV query is invalid, a display and a return value are needed, the column names need to be different. If your query contains an in-line query, the first FROM clause in the SQL statement must not belong to the in-line query."
Splitting the string into two pieces (e.g., ' fr' || 'om ') avoids the problem. Looks like the parser isn't tokenizing strings before looking for keywords.
Rodney

Rodney,
Looks like it just doesn't like the space at the beginning.
That said, this worked for me:
SELECT c001||chr(32)||'from ' d, seq_id r
FROM apex_collections
WHERE
(collection_name = 'ABC'
ORDER BY 1
Chad

LOV creation problem

I'm having a problem with creating some dynamic LOV's. It appears that I can only create an LOV against a table that has only two columns. When I try to create one against a table with three or more columns, even though I'm only selecting two columns, I get the "LOV query is invalid, a display and a return value are needed, the column names need to be different." error message.
As a quick test, using the scott.emp table, I was unable to create a LOV against it. I then made a view called emptest consisting of the ename and empno fields, and then I was able to create an LOV.
This suffices as a last resort workaround, but any idea on when this functionality might be fixed, so people can aviod the extra step?
One of the queries I've tried to create an LOV against a table with three columns is:
select affil d, afn_code r
from lu_affiliation
order by 1
This just gives me the error message listed above. However, if I create a view first with just those two columns, and then create the LOV against the view, then it works.
Thanks

Yes, I've double-checked, and I am am using the D and R alias'. Perhaps it may have been caused by installing HTML DB after installing the database control and following the instructions (alerts) about revoking execution fom PUBLIC on utl_file and a few others {?}. I noticed later that it caused some problems with other packages becoming invalid, so I re-granted execution to those and re-complied the invalid packages. But, I did do all this before playing around with HTML DB.
Yesterday I played around all day experimenting, and the only way I could create a LOV was against an object (table or view) with only two columns.
Thanks for any assistance or clarification, though I've found a cludgy workaround.

2 Query Problems....

Hi there,
i've got two Major Problems. I'm a relativly newbie to SAP BW and the Query Designer.
First Problem:
My Query looks Like this
Year-----Sales--Change
2003---1000 u20AC-0%
2004---2000 u20AC-100%
2005---3000 u20AC-50%
Now i wanna have a third Column in witch the Change of the Sales is displayed in correlation to the year before.
l will try to eyplain it a litte bit. When my Sales were 1000 u20AC in year 2003 then i wanna calculate the increase in percent in correlation to the year before. Is this posiible???
An now the second problem ):
I got another Query in wich i just wanna to show the overall result in a Diagramm. When i calculate the Overall Result, every result is shown and actually is also shown in the diagram.
I try to explain this a bit more:
Year--Header1---Header2
2003--data--
data
2004--data--
data
2006--data--
data
O.Result---result1--result 2
So i Just want to show result1 and result2 in a diagram. How do i do this?
Thanks in advance for some answers .

Hi,
For you first problem, In column, in your structure, create a selection with the current year for example and another selection with previous year and in the third column create a formula to calculate the progression.
For your second problem, hide year from your query an you will have only global result.
Regards
Romain.

Designing LOV Query Problem

Similar Messages

Maybe you are looking for