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

Similar Messages

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

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

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

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

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.

U0093BEx transport request u0091ABC3005000u0092 is not available or not suitableu0094

Hi,
In our development, I tried to modify an old report but got the message
BEx transport request ABC3005000 is not available or not suitable
and opened up in BEx but in a read only mode.
My goal was to modify this report.
I therefore spent time to create a new report just like the original report with my modifications. On the next day, I wanted to make some changes in the new report but in opening it, I got the same message as the original one:
BEx transport request ABC3005000 is not available or not suitable
What seems to be going on? What can I do to be able to make modifications in BEx
without this massage?
The switch Change mode is no available to switch.
I assume it implies that the query has been transported already so it wont allow additional changes, but why it the same problem with the new one just created?
Thanks

Hi,
I went through the steps you suggested:
RSA1 -> Transport Connection
Create transport requests for Bex (BEx truck icon); I double-clicked on a package (click on Assign/Delete) and created a new transport request AABB555.
The problem is that, right after that when I open BEx, select Add-Ins, Open Queries, it attempts to open but instead of bringing up the list of queries for selection to attempt to edit, BEx flashes and freezes up.
Then from there BEx freezes up. Any ideas?
I went into se09 and deleted the new transport request AABB555;
Now, BEx can open up the queries instead of the freezing up, but it gives the message:
"BEx transport request 'AABB555' is not suitable or available. Request/task AABB555' does not exist"
When I choose OK, it brings me into the query but still only in read only mode and can't edit.
Any more ideas?

(Request for reporting available) is not coming in Cube

Hi All,
I have Cube & DSO.
I added fields in DSO & Cube.
Cube1 has Aggregrates built on it.i added 5 infoobjects on it, Now when i load data from DSO to Cube(Request for reporting available) is not coming up. i cant do reporting on it. can anyone help.
thanks in advance,
Kiran.

Hi ....
Have you done the Roll up ?
Since aggregates are there on that cube....until and unless you do the roll up that request will not be available for Reporting...
Regards,
Debjani....

"Request for Reporting available " is not displayed after loading the data.

Hi
A DSO feeds the data to a cube and DSO. In dso reporting sysmbol is present. However in the cube "Request for Reporting available " is not present in the manage tab of the cube.
Please advise on this.
Regards
loyee

Hi,
What is the status in Monitor. If it is ok, go to manage of the infocube,
in that screen on the menu, Environment --> Automatic Request processing. Then you will get three check boxes.
Click the first check box, (Set Quality status to OK). If you aggregates, choose second box.
Hope this helps.
Regards,
Rama Murthy.

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

ChaRM Reporting - Transport Request, Tak and Owner columns not filled

I am using ChaRM reporting functionalities (/TMWFLOW/REPORTING transaction). When I select "display header, project, task list and transport", transport request, task and owner columns are not filled with values.
What is the problem?
Thanks
Antonello

Hi,
1. Is it configurd for ChaRM functionality in your systme landscape.
2. If not, please do the ChaRM configuration using by tcode SPRO.
Regards,
Srini Nookala

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>

"battery not available", battery not charging

I just bought a NuPower battery fo my IBook G4. It's been working fine for a month or so. However, now my computer won't charge the battery. Near the battery icon at the top of the screen, it at first says "caluculating..." and then says "battery not available". Further, sometimes even when the power cord is plugged in (and the LED's are lit up), it still runs on the battery power and says the power is not plugged in. And, the lighting on the LED's do not correspond at all with the battery charge(i.e. it is sometimes green even though there is no battery power). Maybe these are 2 different problems?
Any advice would be appreciated-I'm no where near a MAC service provider.

There are two things you could try.
1. "Resetting PowerBook and iBook Power Management Unit" (PMU)
Performing a PMU reset returns the iBook and PowerBook hardware, including NVRAM,
to default settings and forces the computer to shut down. ...
http://support.apple.com/kb/HT1431 - 36k - Cached - Similar pages
2. "Calibrating your computer's battery for best performance"
The battery needs to be recalibrated from time to time to keep the onscreen battery
time and percent display accurate. With all iBooks and PowerBook G4 ...
http://support.apple.com/kb/HT1490 - 27k - Cached - Similar pages
"Mac OS X 10.4 Help: Calibrating an iBook or PowerBook battery"
If you have an iBook or PowerBook portable computer, you should calibrate the
battery to get the longest running life during the first week you have your ...
http://docs.info.apple.com/article.html?path=Mac/10.4/en/mh1959.html -
Also, you may see what the computer's power and battery life look like in
the Profiler's energy/battery logs. Some widgets are good for battery info.
The battery seller may have some kind of support, since that part is not
an original replacement part and may have issues of its own. Sometimes
the recalibration and pmu resets will help new batteries work properly.
Good luck & happy computing!

Existing IMAP notes not available in notes app after mountain lion installation

After today's mountain lion upgrade (from lion) my notes stored on an IMAP server are not available in the new notes app. The folder of the IMAP Account itself is shown but appears empty. On my Iphone all notes of the IMAP Account are shoen correctly as well as on another mac still running lion.
Any Suggestions?
Thanks in advance.

Okay, I assume there are some different reasons for the syncing problem.
I got my notes syncing again by just losing the prefix on my iPhone and renaming the existing notes folder. For those with a similar problem, here's how:
Old situation:
Within OS X Lion I used a Gmail account with notes (IMAP). To avoid a messy layout with the Gmail folders I used [Gmail] as IMAP Path Prefix (found under Accounts, tab Advanced).
Under iOS5, 'Notes' was ticked on under the Gmail account. The result: Apple created a IMAP folder '[Gmail]/Notes' to store all notes.
New situation:
After upgrading to OS X Mountain Lion I ticked 'Notes' under the Gmail account within system prefs, 'Mail, Contacts & Calendars'. The new Notes app remained empty and didn't show my existing notes that were still on my iPhone.
Logging in to www.gmail.com reveiled a new folder created by Mountain Lion: 'Notes'. The existing notes folder was named '[Gmail]/Notes' - because I used the [Gmail] prefix - and contained al the existing notes.
So Mountain Lion syncs with the IMAP folder 'Notes' and the iPhone syncs with the folder '[Gmail]/Notes'
In Lion the Mail settings were used for both Mail and Notes. So the IMAP prefix applied to both.
In Mountain Lion, the IMAP prefix only applies to Mail, not to Notes.
New situation, fixed:
As Mountain Lion can only use a folder called 'Notes' for syncing, I had to change the folder my iPhone was syncing with: '[Gmail]/Notes'. I removed the newly created folder 'Notes' via www.gmail.com under the label settings and renamed label '[Gmail]/Notes' to 'Notes'. After that I removed the IMAP prefix '[Gmail]' from my iPhone Gmail (advanced) account settings, making the iPhone sync notes with the folder 'Notes' instead of '[Gmail]/Notes'. That's it.
Btw, I maintained the use of the prefix within Apple Mail under Mountain Lion as that is totally separated from the Notes section.
Hope this helps.

Why is the iPad 3 not available? Not even the tech specs!

Why isn't the iPad 3 available? Not even the tech specs!

There have been five iPad models: the original iPad, the iPad 2, the third generation iPad, the "iPad with Retina display" and the iPad Mini.
http://store.apple.com/us/browse/home/shop_ipad/compare
The original iPad and the third generation iPad have been discontinued. There is not now, nor has there ever been, an iPad 3 so if you are searching for technical specifications look for iPad (3rd generation).
Identifying iPad Models

Bex Transport request is not available or not suitable

Similar Messages

Maybe you are looking for