Transport Request not available or not suitable

[Former Member]

Hi,

We have a set of queries that was developed and transported to Quality. Now we are not able to change those queries in DEV. We are getting 'Transport Request not available or not suitable' error while opening the query and is available only in display mode.

I tried attaching the query to a transport ..but still getting the same error .. any help

Thanks

[former_member188975]

Hi,

You need to assign an open (modifiable) TR to the dev package to which the query elements were assigned. You can do this from RSA1 > Transport Connection > Bex Transport button.

Also, please try to search on SDN when posting a new question...sometimes the same has been answered many times earlier as well.

Hope this helps...

[Former Member]

The reason may be the Underlying Infoproviders/Some objects ( may be query elements ) which are dependent are Imported or are collected in a Released/Unreleased Transport Request.

You can just create a TR and collect them for now ( In transport Connection ) which will let you edit the queries and later move them into the required TR & Dev Class/Package.

[Former Member]

Thanks Roberto..Is there any way to identify the objects thats causing the problem..

[Former Member]

Hi Roberto / Bhanu,

Even after assigning the query to a transport I am getting the same error..

Is there any way to identify the objects that is causing the problem ...

[former_member188975]

Did you log out and log back inot bex after making the assignment?

[Former Member]

Have you assigned it properly - just go check in SE09 if the Query is shown in the Object list for that TR.

[Former Member]

Yes ...

I see them in SE09 ..and I logged in again..

While i did the TR , I just broght in the Query elements .. The necessary objects showed the info cube also.. I didnt want to bring in the cube ...

[Former Member]

Is it still uneditable ??

Try assigning a transportable package ...you can collect them again in the same request....after collecting just do a Refresh there itself to see if all elements have been assigned to the package.

[Former Member]

Yes..I tried it ..All are in the same package..

One more thing ..I had another query(which was transported to Q) on the same info provider which is editable...

[Former Member]

After assigning the Query (USE MANUAL COLLECTION) to a transport the problem got fixed..