Bex Transport request is not available

Hi guys
I want to change the Bex query from query designer, when i go for change mode it didnu2019t allow me to change and throws error message "Bex transport request " is not available or not suitable" and in second line it gives "choose an existing request.
Can any one tell me how to change the Bex query with a transport request?
Gaurav

Hi,
You get this message if you have captured the query in a transport request and released or transported the request.
You can somply capture the query in a new request again from transport connection and then you will be able to edit the query.
even after capturing the query in the request is not allowing to edit then you need to try the option as explained by our friend above.
Regds,
Shashank

Similar Messages

BEx Transport Requests '' ist not available or not suitable

hi, all,
I want to change a query, that has been transported back from Prod.System into TestSystem. Changes in the query aren't possible - the error message is
" BEx Transport Requests '' ist not available or not suitable ".
Now, there is a Standard BEx Transport Request and, in the RSA1 -> Transport Connection I see the query complete with that Transport Request.
What can the reason be? Any Idea?
Thanks a lot in advance.
neven

Ciao, Paolo,
thank you for the quick responce.
I did exactly as described :
The easiest thing to do is the following:
1) collect your query in transport connection
2) check if it is already assigned to a transport
2a)if assigned to a transport check if this is the standard bex transport. If so go to step 3, If not see if you should just tranport that request (or you can just go to step 3...but i wouldn't advise that)
3) unlock the standard bex request
4) now go back to transport connection and put the collected objects in a new request
5) release and transport your new request
It still doesn't help. I can't change the Query. The error-message is stil the same.
best regards
neven

BEx Transport Request is not available or not sitable

Hi,
When i try to install some queries from Business Content in the BW DEV box, the error was :
<b>BEx Transport Request is not available or not sitable</b>
Please let me know what has to be done in order to get out of this error
Thanks & Regards,
Kishore

Hi Ken,
Thanks for responding to my problem.
You are right. I am installing from business content queries that have never been installed before.
so when i am installing the queries from business content the error was :
BEx transport request is not suitable or not available.
How to proceed now ?
Please give reply ASAP....
Thanks & Regards,
Kishore

Bex Transport request is not available or not suitable

Guys,
I need to make changes to query when I open it...it's saying Transport req is not available. So I have collected the query in a new transport in transport connection, but when I go back to the query its still giving the same error message. How do I resocve this error?
The transport it is showing in the query was deleted, so I cannot use the old transport.
Thanks,
Kris

Hello Kris,
What Mahesh said will solve your issue but once you transport that request you will again get the same error when you open any query in BEX. One way to get around this issue is for the first time create a request using the BEX transport button in transport connection and always keep this request open. If you want to transport a query that is assigned to this request just unlock this request using se03 and then collect your query and the corresponding objects in a new request in transport connection and transport the new request. This way atleast everytime you open a query you will not get the error.
Hope this helps.
Thanks

Opening Query: u0091BEx transport request '' is not available or not suitable"u0092

Hello,
I tried was able to run and modify a query last week. When I try to modify/run it now, it gives the message below and allows me to run it but not modify.
BEx transport request '' is not available or not suitable"
What are the possbile causes and remedies to this problem?
Thanks in advance.

dear Amanda,
here can imply 'copy' since as the result objects(query and elements) in production are exactly same with dev. but the terms 'copy' itself in query normally refer to copy query from one infoprovider to another infoprovider.
(transaction rszc).
i think she mean the query objects included in transport request and will be carried on to qa/production server.
once the new queries 'placed on transport'(in request), we must immediately create a bex request for the same package, otherwise nobody can save their queries (that included in the request).
transport bex
http://help.sap.com/saphelp_nw2004s/helpdata/en/38/5ee7377a98c17fe10000009b38f842/frameset.htm
copy query
http://help.sap.com/saphelp_bw33/helpdata/en/9f/f57539d6d1c93be10000000a114084/frameset.htm
hope this helps.

Standard BEx transporting Request

Hi Dudes,
Can u explain me with a scenario, what is this Standard BEx Transporting Request and what is the purpose of this,
Thankyou.

Hi,
This is what note says:
Symptom
Editing of a query in Query Designer may return the various error messages concerning transport system. Query or query component can not be changed or saved.
The following error messages are possible:
'Query could not be saved due to a problem in transport' message R9 124;
'BEx Transport Request XXX... is not available or not suitable. Choose an existing request';
'Object ELEM XXX... could not be saved to order YYY...';
'A dependent object is being locked by the transport system' message R9 113
'The dependent objects are in different transport orders' message R9 114;
'The upgrade is already running - you are not able to change objects'.
In some particular cases using NW 2004s server with 3.x Query Designer
'Operation failed, no message available from server'.
Other terms
Query, Query Designer, Correction and Transport System, CTS, ELEM, Transport Request, Changeability.
Reason and Prerequisites
The error messages rise as the result of wrong administration of Correction and Transport System (CTS).
Transport System Mode
Two main modes of Transport System can be used for BW system: Standard Transport System and BW Transport System. Both modes require different administration efforts.
Standard Transport System (system default)
Within this mode an assignment of newly created query elements is done during save procedure. System asks for appropriated Package and corresponding Transport Request within this Package. The mode allows separating of changes done in the system different users in different Transport Requests. Users must be authorized to create new Transport Requests or to write into existing Transport Requests.
BW Transport System (recommended for handling of BEx objects)
Within BW Transport System initial assignment of newly create query elements is done automatically to $TMP Package. This is a Package for temporary objects and does not require modifiable Transport Request. Changes of those query elements can be done without further restrictions. Further assignment to a Package and corresponding Transport Request can be performed using Transport Connection of Administrator Workbench (transaction RSA1).
All kinds of changes for query elements which already have been assigned to any Package different from $TMP (for example, queries transported from another system) must be registered in so-called Standard BEx Request. Using Standard BEx Request all changes done to query elements can be also transported to any other system. If the old Standard BEx Request has been released, another one must be created immediately in order to allow further changes for query elements.
The typical reason for error messages listed above is a situation when NO Standard BEx Request is available anymore in the system. The algorithm of query SAVE contains a transport systems check. If the transport system check fails, no changes are possible.
Changeability of query elements
The recommended setting for query element (ELEM) is 'Everything Changeable'. Using of other settings, like 'Original Changeable' or 'Nothing is Changeable', will make editing of objects not possible when the general system changeability will set to 'not changeable' (SCC4).
Setting 'Original Changeable' allows changes only for query elements which have been created in this particular system. Quite often an ordinary query may contain, for example, variables or other reusable components created in the other systems. In this case changing of a query containing those objects will be not possible.
Changeability of Package
Package (Development Class) where the corresponding Transport Request has to be created must be changeable. If a Package has a property 'Package is not extendable' set to true, no requests can be created within this Package. This means no objects can be registered.
Solution
The following messages mainly happen if BW Transport System is activated. The existence of Standard BEx Request and correct settings for object changeability should be checked.
'Query could not be saved due to a problem in transport';
'BEx Transport Request XXX... is not available or not suitable. Choose an existing request';
'Operation failed, no message available from server'.
How to create a new Standard BEx Request?
Start Administrator Workbench (RSA1) --> Transport Connection. Find button BEx. Under the button user is able to create/assign a new Standard BEx Request.
How to check Changeability of object?
Start Administrator Workbench (RSA1) --> Transport Connection. Find button 'Object Changeability'. Set property 'Everything changeable' for query elements (ELEM).
How to check Changeability of Package?
Start transaction SE80 --> select corresponding Package --> find properties dialog. Check whether the property 'Package is not extendable' is set to false. Assignment of query elements (R3TR ELEM) to a corresponding Package is stored in the table TADIR (field DEVCLASS). In order to obtain a list of query elements used in a definition of a particular query having problems use the function RSZ_X_COMPONENT_GET with the I_OBJVERS = 'A', I_COMPID = technical name of a query. Execute the function and copy all elements (ELTUID) from the exporting table C_T_ELTDIR. Use this selection as the input parameter for selection from TADIR table (field OBJ_NAME). Collect all Packages and check the changeability as described above.
The following messages mainly happen if Standard Transport System is activated. The problem happens in case, when one or several objects from definition of a particular query have been already written in another modifiable Transport Request. In BW 3.x each object can be processed only within one Transport Request.
'Object ELEM XXX... could not be saved to order YYY...';
'A dependent object is being locked by the transport system';
'The dependent objects are in different transport orders';
The situation may happen, for example, if a Query A contains a variable which has been already used in another Query B assigned to different Transport Request. In this case, saving of Query A will be not possible while the Transport Request containing the shared variable is not released.
How to find an assignment of object to a Transport Request?
Start transaction SE03 and select 'Search for objects in requests/tasks'. Provide ELTUID of the element which can not be saved. Object type is R3TR ELEM. Search for modifiable Transport Requests containing this element. If corresponding Request is found, it can be released. After that is will become possible to save this query element into another Request.
Changing of query elements during running upgrage is not possible. The system sets a global lock in order to prevent any change which may potentially affect the consistency of objects. In such situation users should stop the upgrade procedures and wait until the process will finish.
Regds,
Shashank

Upgrade requested but not available

I purchased full Acrobat XI Standard, downloaded and installed. Now an upgrade with serial number is requested but not available. How can I resolve?

http://forums.adobe.com/community/download_install_setup/creative_cloud_faq
-has a link about why you are prompted to enter a serial number which may help

Requested resource not available - can not find servlet

I have an application in tomcat that uses jsp and servlets. The JSP works fine, but I keep getting a "requested resource not available" erroe when i try to access a servlet. My jsp is in a directory called ProjectManager, and my servlet classes are in WEB-INF/classes inside ProjectManager and are in a package called pmt.
I can access my jsp using localhost:8080/ProjectManager/index.jsp, but I cannot seem to access the servlets, regardless of the URL I try. I've tried adding a servlet-name and a servlet-mapping in the web.xml file but I'm still stuck.
Does anybody have any ideas?
Thanks in advance.

What jar files should be in the library? I have the following:
commons-lang-2.4(2).jar
mysqlconnector-java-5.1.6.bin.jar
webserviceutils.jar
Here is my web.xml as I too am getting "the request resource....cannot be found:
<?xml version="1.0" encoding="UTF-8"?>
<web-app id="WebApp_ID" version="2.4" xmlns="http://java.sun.com/xml/ns/j2ee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee http://java.sun.com/xml/ns/j2ee/web-app_2_4.xsd">
     <display-name>
     classBlog</display-name>
     <servlet>
          <description>
          </description>
          <display-name>
          DriverServlet</display-name>
          <servlet-name>DriverServlet</servlet-name>
          <servlet-class>
          edu.ec.web.classBlog.DriverServlet</servlet-class>
     </servlet>
     <servlet>
          <description>
          </description>
          <display-name>
          AddEntityServlet</display-name>
          <servlet-name>AddEntityServlet</servlet-name>
          <servlet-class>
          com.ec.blog.web.AddEntityServlet</servlet-class>
     </servlet>
     <servlet>
          <description>
          </description>
          <display-name>
          DeleteEntityServlet</display-name>
          <servlet-name>DeleteEntityServlet</servlet-name>
          <servlet-class>
          com.ec.blog.web.DeleteEntityServlet</servlet-class>
     </servlet>
     <servlet>
          <description>
          </description>
          <display-name>
          EditEntityServlet</display-name>
          <servlet-name>EditEntityServlet</servlet-name>
          <servlet-class>
          com.ec.blog.web.EditEntityServlet</servlet-class>
     </servlet>
     <servlet>
          <description>
          </description>
          <display-name>
          ViewBlogServlet</display-name>
          <servlet-name>ViewBlogServlet</servlet-name>
          <servlet-class>
          com.ec.blog.web.ViewBlogServlet</servlet-class>
     </servlet>
     <servlet>
          <description>
          </description>
          <display-name>
          ViewEntityServlet</display-name>
          <servlet-name>ViewEntityServlet</servlet-name>
          <servlet-class>
          com.ec.blog.web.ViewEntityServlet</servlet-class>
     </servlet>
     <servlet>
          <description>
          </description>
          <display-name>
          AddEntryServlet</display-name>
          <servlet-name>AddEntryServlet</servlet-name>
          <servlet-class>
          com.ec.blog.web.AddEntryServlet</servlet-class>
     </servlet>
     <servlet>
          <description>
          </description>
          <display-name>
          DeleteEntryServlet</display-name>
          <servlet-name>DeleteEntryServlet</servlet-name>
          <servlet-class>
          com.ec.blog.web.DeleteEntryServlet</servlet-class>
     </servlet>
     <servlet>
          <description>
          </description>
          <display-name>
          EditEntryServlet</display-name>
          <servlet-name>EditEntryServlet</servlet-name>
          <servlet-class>
          com.ec.blog.web.EditEntryServlet</servlet-class>
     </servlet>
     <servlet>
          <description>
          </description>
          <display-name>
          ViewEntryServlet</display-name>
          <servlet-name>ViewEntryServlet</servlet-name>
          <servlet-class>
          com.ec.blog.web.ViewEntryServlet</servlet-class>
     </servlet>
     <servlet-mapping>
          <servlet-name>DriverServlet</servlet-name>
          <url-pattern>/DriverServlet</url-pattern>
     </servlet-mapping>
     <servlet-mapping>
          <servlet-name>AddEntityServlet</servlet-name>
          <url-pattern>/AddEntityServlet</url-pattern>
     </servlet-mapping>
     <servlet-mapping>
          <servlet-name>DeleteEntityServlet</servlet-name>
          <url-pattern>/DeleteEntityServlet</url-pattern>
     </servlet-mapping>
     <servlet-mapping>
          <servlet-name>EditEntityServlet</servlet-name>
          <url-pattern>/EditEntityServlet</url-pattern>
     </servlet-mapping>
     <servlet-mapping>
          <servlet-name>ViewBlogServlet</servlet-name>
          <url-pattern>/ViewBlogServlet</url-pattern>
     </servlet-mapping>
     <servlet-mapping>
          <servlet-name>ViewEntityServlet</servlet-name>
          <url-pattern>/ViewEntityServlet</url-pattern>
     </servlet-mapping>
     <servlet-mapping>
          <servlet-name>AddEntryServlet</servlet-name>
          <url-pattern>/AddEntryServlet</url-pattern>
     </servlet-mapping>
     <servlet-mapping>
          <servlet-name>DeleteEntryServlet</servlet-name>
          <url-pattern>/DeleteEntryServlet</url-pattern>
     </servlet-mapping>
     <servlet-mapping>
          <servlet-name>EditEntryServlet</servlet-name>
          <url-pattern>/EditEntryServlet</url-pattern>
     </servlet-mapping>
     <servlet-mapping>
          <servlet-name>ViewEntryServlet</servlet-name>
          <url-pattern>/ViewEntryServlet</url-pattern>
     </servlet-mapping>
     <welcome-file-list>
          <welcome-file>index.html</welcome-file>
          <welcome-file>index.htm</welcome-file>
          <welcome-file>index.jsp</welcome-file>
          <welcome-file>default.html</welcome-file>
          <welcome-file>default.htm</welcome-file>
          <welcome-file>default.jsp</welcome-file>
     </welcome-file-list>
</web-app>

Oracle.jbo.RowNotAvailableException: Requested row not available

Hello all,
i'm new to ADF and at work I'm using ADF/JDEV 10.1.2.
I will try to explain the scenario where I'm getting oracle.jbo.RowNotAvailableException: Requested row not available in the iterator:
I have 2 pages:
A)Search Page - SearchUI.xml - uses View1 - uses DC1
B)Create Page - CreateUI.xml - uses same view as above View1 - uses same datacontrol as above DC1
The search page has a link to create page.
When I test the application the search page functions fine. The create page functions fine when I test it separately.
but when i click the link on the search page to go to create page: I get the following error:oracle.jbo.RowNotAvailableException: Requested row not available in the iterator.
I' have tried fiollowing but no luck so far:
1) Turned off Enable Token state validation -basically in each UIModel above it is set to FALSE
2) If i remove the bindings from create page in the CreateUI.xml and just leave the action - it creates the account and- the Search->create page works fine BUT then Search->create->ThirdPage that uses the same view as the first two pages gives the above error
i'm also using struts1.0.
Each page works fine on its own but its when I go from one page to the other that's when i get this error.
Kindly suggest me if you have noticed this behaviour.
Thank you.

Here is the stack trace:
oracle.jbo.RowNotAvailableException: JBO-25046: Requested row not available in row set iterator FrmlProjectView.
     at oracle.jbo.client.remote.RowSetIteratorImpl.getAllRowsInRange(RowSetIteratorImpl.java:2082)
     at oracle.jbo.client.remote.RowSetImpl.getAllRowsInRange(RowSetImpl.java:743)
     at oracle.jbo.client.remote.ViewUsageImpl.getAllRowsInRange(ViewUsageImpl.java:1123)
     at oracle.jbo.common.ws.WSRowSetIteratorBase.getAllRowsInRange(WSRowSetIteratorBase.java:740)
     at oracle.adf.model.binding.DCIteratorBinding.getAllRowsInRange(DCIteratorBinding.java:1717)
     at oracle.adf.model.binding.DCIteratorBinding.refreshControl(DCIteratorBinding.java:682)
     at oracle.adf.model.binding.DCBindingContainer.refreshControl(DCBindingContainer.java:1596)
     at oracle.adf.controller.lifecycle.PageLifecycle.prepareModel(PageLifecycle.java:205)
     at oracle.adf.controller.struts.actions.StrutsPageLifecycle.prepareModel(StrutsPageLifecycle.java:70)
     at oracle.adf.controller.struts.actions.DataAction.prepareModel(DataAction.java:295)
     at oracle.adf.controller.struts.actions.DataAction.prepareModel(DataAction.java:486)
     at oracle.adf.controller.lifecycle.PageLifecycle.handleLifecycle(PageLifecycle.java:105)
     at oracle.adf.controller.struts.actions.DataAction.handleLifecycle(DataAction.java:223)

Transport Request is not flagged for import into production.

When I try to migrate a CR from the quality system to the acceptance system, through solution manager system, the status flag still remains to be "To be tested" which normally does not happen.
I get 4 warnings as below:
1) Status was reset by system
2) No import into test system has taken place.
3) Transport request is not flagged for import into production
4) The tester role cannot be the same as the developer role.
Usually when a CR is selected for migration to Acceptance, the status flag automatically sets to "productive", which in turn depicts that the CR has been migrated to acceptance and is ready for import into production.
But when I check the Transport log in the acceptance system, it is evident that the CR has been migrated to acceptance with errors.

I guess these errors you mentioned are the reason why ChaRM reports your transprot request as
2) No import into test system has taken place.
1) Status was reset because 2) is not fullfilled.
3) did not get flagged because status was not set due to previous errors.
4) business partner of user with function "tester" (apparently the one who tries to set status) is the same as the business partner assigned to function "developer". If it should be the same person you can switch off the warning in customizing.
Try to correct import errors and repeat status switch.

Transport request is not generating in Development

Hi Friends ,
Transport request is not geting generated in develpment system........so what could be the problem....
RB

Hi Raghavendra,
Can you give me some more details ? Which support package ? What kind of transport (java or abap) ?
Have you configured CTS+ ?
Best regards,
GL
http://newitbizz.blogspot.com/

Bex transport request 'BWDK900073' is not available or not suitable

Hi,
i have transported a cube with "data flow after" option and collected in a package zbexquality.
this request was transported to productin and i can see the queries in production too.
now when i go to change any of the queries on this cube, it gives me the following error:
==========
Diagnosis
There are the following possible causes:
No request has been set up as the standard transport request for BEx objects.
The (set up) request 'BWDK900073' (for the package 'ZBEXQUALITY' ) has already been released.
The (set up) request 'BWDK900073' (for the package 'ZBEXQUALITY' ) is not of the type 'transportable change request'.
System response
The request BWDK900073 can not be used to record changes to BEx objects (queries or Excel workbooks). The changes made to objects you are editing will not be logged.
Procedure
If you want to record changes to BEx objects, set up an open transportable change request as the transport request for BEx objects. (If the package 'ZBEXQUALITY' is not empty, set up a request for this package).
Inform your system administrator of your actions, or enter a new, targeted transport request in the Administrator Workbench in the transport connection by using the 'BEx' pushbutton (Create Transport Requests for BEx).
Procedure for System Administration
====================
when i try to change any other queries( transported using different request and different package earlier), it gives me teh same message.
what is the reason? what is wrong?
thank u in advance

hi S B,
as mentioned in your previous thread,
each time you released request for query to be transported for 1st time, you will need to create
BEx request with same package as soon as the request released, otherwise you won't be able to save changes
to the query in that request.
rsa1->transport connection->icon truck and bex,
assign with package ZBEXQUALITY.
hope this helps.
ZBEXQUALITY is not a good naming. some sample
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/3010ba90-0201-0010-2896-e58547c6757e
Customer Package Description
ZBW BW Package for Custom Objects
ZACTPAY Accounts Payable - Query-only package
ZACTREC Accounts Receivables - Query-only package
ZCONTROLLING Controlling - Query-only package
ZSALES Sales and Distribution Query-only package
ZFIAA Fixed Assets - Query-only package
ZPROJ_SYS Project Systems Query-only package
ZPURCH Purchasing - Query-only package
ZSP_LEDGER Special Ledger - Query-only package

Transport Request Number not Displayed in /TMWFLOW/REP_REPORTING

Hello all,
In Solution Manger 7.0, I am trying to find a way to display Transport Requests associated with a Change Document. I tried using program /TMWFLOW/REP_REPORTING, but when I pulled Transport Request into my layout, the field was blank. I know there should be existing Transport Requests associated with the Change Documents.
We are using the following:
SolMan 7.0, EHP1
SAP_Basis Release 701
ST 400
Best regards,
Cynthia Ferrer

Hello Cynthia,
Did you checked the job SM:TMWFLOW_CMSSYSCOL is planified ? This job gets tracking data from the satellite systems. Some corrections are available for this job depending on your SP level (see note 1377427). There is an activity in SPRO :
SAP Solution Manager --> Basic Settings --> Background Jobs --> Schedule Background Jobs
Kind regards,
Stéphane.

Transport request could not be released

hi guys,
im trying to release a request thru se09
after successfully releasing the task.the request could not be released.
it gives this error message
TEST CALL OF TRANSPORT CONTROL PROGRAM (tp) ENDED WITH RETURN CODE 0212.
<removed_by_moderator>
Read the "Rules of Engagement"
Regards Walata
Edited by: Juan Reyes on Oct 13, 2009 4:40 PM

hi Mark,these are the results of the actions you specifiedWhen i tried to open the tp system log, this is wat i get"Could not open log file
wc40-altsapmnt     ranslog"for the checksconnection test"connection to system DEV OK"transport directoryCheck transport directory      14.10.2009 10:36:27           DEV Development System                Transport directory                 bin
wc40-altsapmnt     rans in               Create test file        Read test file        Delete test file               buffer
wc40-altsapmnt     rans uffer               Create test file        Read test file        Delete test file               cofiles
wc40-altsapmnt     ranscofiles               Create test file        Read test file        Delete test file               data
wc40-altsapmnt     ransdata               Create test file        Read test file        Delete test file               log
wc40-altsapmnt     ranslog               Create test file        Read test file        Delete test file               sapnames
wc40-altsapmnt     ranssapnames               Create test file        Read test file        Delete test file               tmp
wc40-altsapmnt     rans     mp               Create test file        Read test file        Delete test file    there is a ZIG ZAG arrow in front of each.while for the transport toolunder the tp interfacethe test was ok i.e. a green mark sign was there for all the items in the drop down listunder transport filethe check for path was marked okfor profile "tp profile cannot be read"for version "tp profile has an invalid formatunder RFC destinationthe test was ok i.e. a green mark sign was there for all the items in the drop down listunder tp callRFC and tp version successfulfor DBCONNECT "link to database failedoffline call "could not access file as supposedhow do i get the error information in the tp system log when i cant even view it
Regards WAlata

Requested resource not available error

I am using Apache Tomcat 4.1.31 and have JDK 1.4.
The default JSP and servlet examples that come with Tomcat are running,
but the problem is my own applications are not running. I have kept the application in the webapps directory but when I enter the URL for example for an application named 'myapp' saved in the webapps/myapp directory I get an error page displaying the following error message:
HTTP Status 404 - myapp/filename type Status report
message myapp/filename
description The requested resource (myapp/filename) is not available.
Apache Tomcat/4.1.27
the examples folder and myapp folder is in the same directory..
/usr/local/tomcat/webapps/
please help me..thanks in advance for your help..

do you error like this:
HTTP Status 404 - /myapp
type Status report
message /myapp
description The requested resource (/myapp) is not available.
Apache Tomcat/5.5.15

Bex Transport request is not available

Similar Messages

Maybe you are looking for