Transportation of queries

Hello all,
how do I transport a querie from 1 client to another. I have created a query in the development environment and I'd like to transport it to the quality environment. But I don't seem to find a functionality for this.
Could anyone help me with this?
Will reward points for usefull answers,
Mark

Hi Mark,
Pl. refer the following link.
http://help.sap.com/saphelp_nw04/helpdata/en/d2/cb4699455611d189710000e8322d00/content.htm
Regards,
Senthilkumar SD

Similar Messages

How to create a transport for queries from production system

We have a situation where the production client has been open during cutover and a user has modified queries which were previously transported into production from our development system. We now wish to 'synchronise' our systems so production can be closed (although we will use the changeability options to allow maintenance of local queries).
Does anyone have experience of this problem? What is the best way of exporting the queries in such a way that we can import them into our development and quality systems?
As ever, any suggestions will be gratefully received.

Hi,
In similar situation, we opted for manual modifications in the Dev. We made the changes in the queries as they were in Prod and then transported them from Dev to Q and then to Prod.
This is how generally it is done.
Regards,
Yogesh

How to transport Jump Queries (RRI) from DPW to QPW

Hi,
I need to transport the Jump Queries from D to Q.
I have one sender Query and 2 Receiver Queries. I would like to transport them to Q. In the transport connect I can able to select the sender Query and The receiver Queries are not found.
Please let me, If I transport my sender Query will the receiver Queries will be automatically transported.
Regards,
Reddy

How have u been transporting all ur queries?
Its the sameway how u generally transport queries but make sure u find all ur 3 queries with whats underlying beneath in the flow.
In RSBBS open the assignment n on top ull see a Truck Icon - Collect & Transport.

Transport of Queries: Query Designer vs. Transport Connection in RSA1

Hello,
actually we are having a very strange behavior towards query transports.
Whenever we collect queries using Query Designer ("save"), all query elements are written on a transport request.
Collecting queries using rsa1 transport connection collects additional repair elements. For some reason these repair elements cause problems: although query elements + repair elements are transported in transport protocol, the query itself does not exist on the quality system.
Any idea why?
Thank You!
Goliad001

Hi,
If you are getting error in transport log due to repair elements, then you can move your transport in Overwrite mode. And when you are moving your query through transport organizer make sure that you have marked your query as well for transport along with dependent objects.
Once you collect all the objects and write them to TR just have a refresh to make sure that all the objects are written to TR. You can check that just beside the object name in Transport organizer.
Regards,
Durgesh.

Activation of BW Production Objects and Transport of Queries and Work books

Hi,
I have successfully transported 0FIGL_1 InfoCube (only in Data Flow Before) from BW DEV to BW Production...
But In BW Production This Cube and InfoSources and Update rules and InfoObects are all in inactive...
What to do?..
Please tell me step by step procedure.....
and also suggest me on how to transport Queries and work books related to My 0FIGL_1 Cube...
Please tell me all step by step procedure...
Help will be greatly appreciated..
This is very urgent
Thanks in advance...

Hi,
May be you are telling is correct but i am unable to follow..
Please correct if my understanding is wrong....
1. I have Created one BEx Truck Request...it is not Released so far..So, it is there in SE09 of BW DEV
2. Selected Queried and work books --- Grouping --- Only necessary objects -- Collection mode -- automatic...(Default all queries and workbooks selected as check box)
3. Click Transport truck (Which is beside of Grouping Option)..
4. Created one request and then released... But not imported into BW Production..
5. Now I have modified all the queried (Change text)
6. RSA1 -- Transport connection -- Selected modified queried...
7. Grouping only necessary objects and collected mode --automatic...
8. Selected modified queries and dragged into right side...
My question here is they are not checked check box under transport?...shall i check it?
Shall i release Old BEx Request? and then before transporting these new modified queries Create another BEx Request?
or else..
Create new request for modified Queries? and then transport?
Now the situation is i have already created transport request for modified queries..What to do? shall i release them also?...
Pls suggest me....

Transport of queries from production to developement

Hello BI Community,
We allow ad-hoc query development in our production system. Yet certain queries are critical and must be "certified" so that they cannot be overwritten in an ad-hoc manner.
The method for certifying a query is to transport it from the development system, and once done the only way to change this query is to move another transport.
As more and more sophisticated queries need to be certified, it is becoming difficult to re-create those queries in the development system for the certification process.
Does anybody have experience or recommendations around moving a query that was originally created in the production system BACKWARDS to the development system ? Then it would be easy to move forward again via transport for certification.
Thank you !
Kiran

Hi Kiran,
1. Open production system
2. Create transport (1) in Prod, add queries, process chains, etc.
3. Create new transport (2) in Prod (in SE01) of type "Transport of Copies"
4. Enter your target system on this screen (choose your Dev system here!)
5. Include objects from transport 1 into transport 2
6. Release transport 2 to go to Dev
7. Delete transport 1 from Prod. This release locks on the objects.
8. Close Prod
8. Import transport 2 into Dev system
OR
The reverse transport is usually not setup , what you could do is :
1. As BASIS to set up the connection
2. Copy the transport object into file and then import it manually into Development
Check this thread.............also.....
Re: Reg : Transport req
Regards,
Vijay.

Transport of queries

Hi
Can anyone tell me what happens when i transport the Bex Request (Which contains the changes made to the queries tat are already in production) to prd with the option
1. Overwrite originals
2. Overwirte originals in repair mode.
What the difference if i use and doesnt use the option in STMS?
Regards
Annie

Hi,
If u use Over Write originals...It will just over write all the Previous objects in Production before transport and completely replaced by new ones..
Suppose if u r changing 0customer infoobject length to 35 from 45....Then after transports the entire Info Object will be trnasported once again and replaces the older version with newer version..
Overwirte originals in repair mode....Here only the changed things wiil be reflected in Production...
Suppoese if u r chabging Info cube design by changing the Info Objects....Then after Transports only these Changed things will get transported...and not the entire cube....
TO make simple and short...These options are all about what objects are transported...
In Over Write originals..all the things are transported..
In Overwirte originals in repair mode...only changed ones get transported..
Hope this helps u..
Best Rgards,
VVenkat..

Transporting InfoSet Queries

Greetings Experts,
I am seeking some guidance in transporting an InfoSet Query that was created in the DEV system. Here are the steps I followed to create the query in the Standard Area:
1. SQ03 - Create user group.
2. SQ02 - Create InfoSet.
3. SQ03 - Assign InfoSet and user IDs to user group.
4. PAAH - Create an InfoSet query with the specified InfoSet
Now I have the user group, InfoSet, and query sitting in the DEV system but am unsure how to transport to PREPRD. I did some research and someone pointed to using SQ02.
In SQ02, I try transporting the User Group only (Import option = REPLACE) and it provides a transport number. The issue is that when I check the transport in SE10, I find something like this:
SIDK904259 Transport for ABAP Query
    Object List of Request
        Table Contents
            AQTDB
                AQSIDK904259 *
This was not what I had expected and I am unsure what this means (and not very comfortable transporting this across). If someone can shed some light into the meaning of this and how I can possibly transport my InfoSet query across systems, that would be much appreciated.
Apologies go out in advance if this is the incorrect section but I chose the one which seemed to fit closest to this issue.
Thanks!

Hi,
The following link will help you to solve your problem
http://help.sap.com/saphelp_sm32/helpdata/en/d2/cb46b3455611d189710000e8322d00/content.htm
Thanks & Regards,
Vidyadhar K

Transport routes queries

Hi ,
I have some doubt in transport route configuration for below structure,
I develop a change in Dev 100 , once release the changes needs to move to Dev 200 and QAS 100 , once test completed in QAS 200 move to QAS 300( UAT client), tehn PRd 100
Dev 100 -
> QAS 100 ---> QAS 300 (UAT client) ---> PRD100
\ --> DEV 200
How to put transport route from Dev 100 -> QAS 100 & DEV 200 ?
Plz help it.
Rg,
Karthik

Transport Target Groups mentioned under this blog by Dolores:
Change Request Management scenario: Usual questions and known errors
Items 1, 2, 3 should explain your query

How to find list of Queries built on Multiprovider &steps to transport quer

Dear Experts,
I got a task to Check if any queries are built on a multiprovider and to change the filter condition on 0INFOPROV to restrict some more Infoproviders in all the queries built on multiprovider .
Request you to help me out how can i find list of queries created based on Multiprovider wise and steps to be followed to restrict 0INFOPROV.
And one more doubt is, what are steps to be followed to transport the queries.
Thanks in advance for favorable assistance.
Thanks & Regards,
Ramesh - Kumar.

Hi..
Follow the steps below:
1) Goto RSA1 -> Metadata Repository -> Select Multiprovider -> Find (Cntrl+F) give your object name -> Double click on search result object, this will give you detailed view of used that particular Objects.
2) To restrict infoprovider within that Multiprovider for Query reullts, Double click on Multiprovider -> choose Change mode -> You'll be able to select/deslect the check boxes under the Infoprovider Tabs (Infocube, DSO, Info Objct, Infosets, Aggr levels) there you can check the infoproviders as per your requirements then selelct the display options with Display All Infoproviders (1st option) at down then continue and save the settings.
Hope this helps you.
Thanks,
Ramanan.

Transport Queries with RSAQR3TR doesn't work

Hi,
I'm tryinf to transport changes made to query from dev to prod. In SQ02 I tried using the transport-button, but it gives me no options for Exporting or downloading only to copy from standard to global area and vice versa.
I tried calling the report RSAQR3TR directly, here I have all options, but when I'm choosing the option "Export" and specify the desired query, I get the message that nothing matching my selection has been found.
Any idea, why I can't transport queries? Does this depend on the standard/global area? If so: where can I change this?
Thanks and regards,
Jan Hempel

Jan,
Here is what <a href="https://websmp202.sap-ag.de/~form/sapnet?_FRAME=CONTAINER&_OBJECT=011000358700007342672001">Note 127182</a> says about transporting global queries vs. standard queries:
All query objects (queries, functional areas, user groups) are created client-independent in the global work area of the query.These objects are therefore displayed in all clients of a system and can be used by all clients. In addition, the objects of this work area have a connection to the workbench organizer, so that changing and transporting of such objects is organized according to common procedures for workbench objects.
In contrast to this, query objects are client-specific in the standard area and have no connection to the workbench organizer. The transport of these type of objects must be organized using a special utilities function (Environment -> Transports function in Transaction SQ02).
Further information on this topic can be found in <a href="https://websmp202.sap-ag.de/~form/sapnet?_FRAME=CONTAINER&_OBJECT=011000358700007427742001">Note 412054</a>. Mainly this note describes transporting query variants but in the section on "Transporting Queries" it mentions, "A detailed description of the procedure for transporting queries, including variants, is provided in the section 'Transport query objects' of the query guide."
It looks like transporting a global query should be through the normal Workbench Organizer tools. See the following links for more info:<a href="http://help.sap.com/saphelp_erp2005/helpdata/en/83/ca5d6688d511d194ec0000e82de14a/content.htm">Query Transport</a>.
<a href="http://help.sap.com/saphelp_erp2005/helpdata/en/d2/cb467f455611d189710000e8322d00/content.htm">General Query Transport Help</a>.
<a href="http://help.sap.com/saphelp_erp2005/helpdata/en/ec/052786a30411d1950a0000e82de14a/content.htm">Transporting Query Global Area Objects</a>
Sorry to give you such a flood of information, but I think the links should give you what you need.
Best Regards,
James G.

Do you transport queries or create them in prod?

We are looking at transporting all queries all the time except special ad-hoc reports. I was wondering how many people out there follow this model as opposed to just creating queries directly in prod. Are there pros and cons to either way? What is the recommended best practice?

I was wondering how many people out there follow this model as opposed to just creating queries directly in prod.
For standard reports, you're going to find that most companies use the create/maintain in development and promote via transport to landscape more than allowing unlimited create/maintain in production.
Are there pros and cons to either way?
There are pro and cons for both sides of the coin. For instance, if you use the transport means for production reports no one will be allowed to change the report whenever they feel like it (big pro in my view), but it limits/eliminates the ability of the end users to create customized, personal versions of those reports (con). With a wide open production environment, the end users will have the ability to create customized reports that suit their individual needs (pro), but it also gives the end users the ability to maintain standard reports to suit their needs, but may not and probably will not suit the needs of others that use that same report in which case you'll have hundreds of versions of each report in your system (huge con from a maintenance and break/fix analysis perspective).
What is the recommended best practice?
The recommended approach is the transport to production methodology. It allows for standard reports to remain standard and mitigates risks that might be introduced because and end user does not understand the underlying data or just does not care.
In the future, with the SAP Business Objects tools, you'll be able to create standard reports in Crystal Reports, Web Intelligence (rich and thin client - Web Intelligence rich client used to be called Desk Intelligence), Xcelsius, et. al. and still give the ability to the end users to save versions of their own reports, in their own personal folder or team folder, so that you have basically the best of both worlds.

Bex Queries not transported into prod

Hi,
I have transported few queries to prod thru transport conn, created bex transportable req and assigned to package and transported to prod
but i could not able to find those queries in prod
can anyone give some suggestions wht could be the problem or am i missin something
thanks

Hi,
I have already tried with Query Designer --> open Queries .... there were no queries and even i am unable to find infoarea's (but i can see the infoarea's in RSA1) and searched with Metadata Repository.. there were no queries
i have transported successfully
i have not transported roles along with Queries
thanks

Transport objects and queries

Hi ,
I know that this topic has been discussed a lot, but can some one help me .
I have made some modifications to Infocube and query in Development system and now I would like to move them to QA and Production system in BI. Can some one tell me a step by step procedure to do this and how I should collect the path for the Infocube and the query to be passed on to the Basis people.
Thanks in advance
tanu

Hi,
Do the following.
1. Goto RSA1 -> Transport connection -> Under all object types -> Infocube -> select objects. There type in your Infocube name and select it and transfer to the right pane. Before transferring select the grouping option Data Flow before.
2. Create the above transport request and transport it to Production.
3. Create another Transport request for transporting the queries from RSA1 -> Transport connection -> Under all object types -> query elements -> query and select all the required queries.
Please note that while transporting make sure that all the objects are saved in Pacakage.
Hope this helps.
Best of luck.
Regards,
Sreenivas.

Question in HR module in SAP Queries ( transport changes)

Question in HR module in SAP Queries.
One infoset is attached to multiple queries.
If there are some changes in infoset, these changes are done in Development box and saved to the transport request. (queries related to infoset are not attached to the transport request).
These changes have to be moved to the Quality box and further to the Production.
1. When I move the infoset to Quality and production, do the related queries get affected? Will they work?
Or do we need to attach all the queries related to the infoset in development. ?
2. What would be the status of the queries that are not attached ?
3. When the changes to infoset is moved to different boxes, is the original infoset OVERWRITTEN or CHANGES APPENDED.
friends plz clarify and send them ASAP.

Hi,
form read_infotype .
call function 'HR_READ_INFOTYPE'
exporting
TCLAS = 'A'
pernr = pernr-pernr
infty = '0002'
begda = pn-begda
endda = pn-endda
BYPASS_BUFFER = ' '
IMPORTING
SUBRC =
tables
infty_tab = i0002
EXCEPTIONS
INFTY_NOT_FOUND = 1
OTHERS = 2
if sy-subrc 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
regs,
Hema.

Transportation of queries

Similar Messages

Maybe you are looking for