cancel
Showing results for 
Search instead for 
Did you mean: 

BEx Query Transports (NW04s)

Former Member
0 Kudos

I transported a few queries using transport connection collection from DEV to QA.

<b>These were the first transports.</b>

After these transports queries that had not yet been transported are requesting a request when they are being saved in query designer:

<b>error msg:</b> BEx transport request '' is not available or not suitable; Choose an existing request.

To correct this problem I created a standard BEx request in transport connection. But now, when a query is saved entries are entered in the standard request, even though the query was never transported. (??????)

I thought the query would go to standard BEx request the first time it was changed after it was transported.

Also, I want to create multiple requests assigned to different packages:

How do I assign the BEx query elements to the packages for transport?

Accepted Solutions (0)

Answers (2)

Answers (2)

Former Member
0 Kudos

Brendon,

The query that is having the error message has not yet been transported, although it belongs to the same infoprovider as the queries that were transported and refer to the same reusable components (i.e: CKF, RKF).

I thought the query would not need a request until it has been transported at least once. Or does a request become necessary after the first transport of any query?

Thanks

Former Member
0 Kudos

Given that error you will not be able to edit that query at all.

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 to edit and later move them into the required TR & Dev Class/Package.

Former Member
0 Kudos

i don't know if you have to do it OR your basis maintain the same for you. but anyways... here are the steps.

RSA1 --> Transport Connection --> there you will see the truck icon with BEx --> Standard BEx Transport Request (assign new if there is none)

please keep in mind it's going to block other users and so check your client's procedures for having this BEx transport.

regards,

sameer

Former Member
0 Kudos

You get that message when you try to modify a Query that has been previously transported, hence the "transport not suitable" message. Therefore you need to assign a new transport to the query. You can do this in two ways, Sameer mentioned one of the methods.

Sameer's solution is risky, keeping a transport open (assigned) picks up any changes made in the BW environment. That means that if some other BW developer is modifying objects, they will be saved to your "assigned" transport. Therefore you must be careful and coordinate with your BW team if you are to use this method. You must also remember to "delete" the assigned transport to "close" it in Transport Connection.

What I recommend is to go to Transport Connection via RSA1, object types, then query elements. Collect the queries you wish to modify and create a new transport for them. Next, make your query changes. Make sure to exit all BW sessions (if you're on BW3.5) after you're done changing your query. Then recollect the query in transport connection to pick up the new changes you made (assign it to the original transport).