Transporting Query--

[Former Member]

Hi all,

i have read a couple of posts on this topic....but i am confused with the steps

like they say if you are doing it first time the normal Truck button should be used after collecting the query

and what is this first time means...is it that we have created a new query in the development and sendit to production for the first time am i right

and how to transport the changes to the query which is already in production

please give me the steps how to do it

thanks and regards

Neel

[Former Member · Accepted solution]

hi

It's enough to go to transport connection in RSA1 of your development system and collect again in a new CR all the objects you need to import in your PRD environment!

for ex.. If you change only a restricted KF, you don't need to transport others than the query and its components from RSA1...

After you collected query objects in Transport Connection, are you able to see your changed objects on the right side of the screen

Collect the changed query in new request in transport connection. Check the consistency of the request before releasing in SE01.

go thru this same post..

[Former Member]

Hi Neel

If you are transporting the query first time from Dev then-

First you create a package for BEx- you can create this as per Infocube or for a particualr application(say Sales).

Then collect your query elements in transport connection and click on Truck button and assign this objects to new request you will create.

For changes in queries which are already in prodction -

1.Find out the BEx package for that query.

2.Create a new transport request and assign this to the package when you click on truck button in transport connection screen

3.Do changes to query and all these changes will be saved into this new request.

4.Cross check whether all changes are captured in transport request or not.

Hope this helps you.

Regards

Pradip

(Assign points to useful answers)

[Former Member]

Hi Pradip,

u said Bex package right

right now we are using the package ZBW , when u say bex package, u meant that its going to be a different one for queries.

plz clarify

thanks and regards

neelu

[edwin_harpino]

hi Neel,

i do suggest you create another package for bex,

and even some packages for different area (sd,mm,pp etc) of queries, after queries transported and you create a BEx request (truck with bex) to hold the changes of queries, if you are using only one package and e.g queries from sd and mm are changed at the same time, and guys from sd want to transport the query but mm don't want, if you are using same package.

also please be remind, new created query elements (calculated keyfigure, restricted key figure, formula, selection and variable) WON'T be included in BEx request, you may need to collect again with the query.

hope this helps.

[Former Member]

Hi Neel

Bex package means a package created to transport for Bex related objects(bex queries, structures, workbooks etc).

Yes. Create a new one if you are planning to use ZBW package only for non-bex.

If you have used ZBW for earlier queries that are transported to production then use ZBW for transporting changes in these queries.

Hope this answers your question.

Regards

Pradip

[Former Member]

Hi A.H.P, Murali,Pradip, Shreya (alphabet wise)

Thankyou all for the wonderful help i could do that

A.H.P & Pradip

i was not able to assign points to you guys, their is some error...once thats clear...i will do that

once again i am very thankfull to u guys.

thanks and regards

neel

[former_member188325]

Have a look at this thread:

hope this helps