SAP Query transport

Hi,
Wish to have step by step procedure of transporting SAP Query ?
Procedure I followed & got error message
I have used SQ02 & truck symbol it is creating only one TR without any customising task.
Using T.code SCC1 in the target system I got error message
" Program ended with error or warning, return code: 4".
Can someone help?
Regards,
Vengat

Hi
Here I am sending the step by step procedure for the SAP Query. Hope this helps you, if so please issue points.
1. Go to SQ02 .
Select Environment -> Query Areas
Select Standard Area (Client specific) as show below
2. Select Environment -> Transports
Select Import radio button
Check Overwriting allowed (only with import/upload/copy)
Remove Check for Test Run
Select Transport InfoSets and queries radio button
Fill Infoset and Query with corresponding names
Fill Import option with transport request number.
3. Click on Execute button
With this it will be done.
Thanks for your patience

Similar Messages

SAP Query: Transport tool(program: RSAQR3TR)

Does the SAP Query: Transport tool(program: RSAQR3TR) transport addtional fields and code in Extras of an InfoSet from one system to another?
TKS in advance.

Hello,
Yes the ABAP query transports the whole Infoset.
Goto Transaction SQ02
Goto Environment -> Query areas -> Select teh Standard area.
Select Environment -> Transports -> Import radio Button
Check the Overwriting allowedand teh remove the check for Test Run
Select the Transport Infosets and queries radiobutton
Fill in the Infoset and teh Query with the corresponding names and the Import option with Transport Request Number
Execute
Regards

SAP query Transport manual activity in Production

All,
Do we really need to use manual step to import the query to production system using some program ? will not be automatic as we do it normal reports ?
Why this manual step needed ?
Please help me to understand.
Ram.

Hello ,
Please go through this link
How to Transport SAP Query(User Group Infoset and Query) to Quality System
Transporting a SAP Query from DEV to PRD
Transport of Abap Query

SAP query transport error - need help

hello,
The system is throwing the following error when importing the query from development to QA client.
We already have the query imported the first time without errors. This is happening with subsequent transports if there is a change or any modification to the query.
Below is the error log from SAP regarding the failed transport :
R3TRAQQUFI was repaired in this system
Message no. TW104
Diagnosis
Object R3TRAQQUFI is in repair status. Therefore, it cannot be imported.
System Response
The object is not imported.
Procedure
If you still want to import the object, release the relevant repair and repeat the import.
Please help
Thanks in advance.

Hi
Here I am sending the step by step procedure for the SAP Query. Hope this helps you, if so please issue points.
1. Go to SQ02 .
Select Environment -> Query Areas
Select Standard Area (Client specific) as show below
2. Select Environment -> Transports
Select Import radio button
Check Overwriting allowed (only with import/upload/copy)
Remove Check for Test Run
Select Transport InfoSets and queries radio button
Fill Infoset and Query with corresponding names
Fill Import option with transport request number.
3. Click on Execute button
With this it will be done.
Thanks for your patience

Is SAP Query transportable?

Hi,
The info sets, query which has been created in development server(SQ02,SQ03,SQ01) is transportable to Quality,Production servers?
Regards,
Vengat
Edited by: Vengata Raghavan on Jan 29, 2008 4:50 AM

It is transported just like other querries--Workbench request..
Request may be required to unlocked before relaese..

ABAP Query Transport request related

Hi,
I have created a Abap query,
1) User group
2)Infoset
3) Query
But when i transport the request in to Quality, I can see only Infoset, not able to see User group and query which i created in the
Development
Please suggest, is this std behaviour or is anything missed
Rgds,
Jai

Thanks to all,
I just created TR with new package for user group and included ifoset and query in the same TR
and imported, issue is resolved
But my question is,where we can utilize below help material, I have spent much time to understand below given explaination and finally left without any conclusion
Short text
SAP Query: Transport tool
Description
The report RSAQR3TR handles all tasks concerning the transport of queries, InfoSets and user groups.
General information
Queries, InfoSets and user groups are stored in the table AQDB. This table is client-specific. For the transport of queries, InfoSets and user groups, there is a special client-independent transport table called TAQTS. You can carry out transports either
·     from a client (source client) of an SAP system to another client (target client) in the same SAP system or
·     from a client (source client) of an SAP system (source system) to a client (target client) in another SAP system (target system).
In both cases, you have to perform similar actions.
The objects to be transported must first be copied from the source client using an export from the table AQDB into the transport table TAQTS. At the same time, a transport request is created for the transport system that includes all entries created by the export from table TATQS (transport dataset). The name of this transport request conforms to the transport system naming conventions (sysKnnnnnn) and is included in the export log. The transport dataset is stored in the table TAQTS under a key which matches the name of the transport request.
If you are transporting within one SAP system (from one client to another), you can import the transport dataset from the target client. The name of the transport request to use for this purpose is that specified during the export, since it should match the key of the transport dataset in the table TAQTS. With this import, the transport dataset is read from the transport table TAQTS and inserted into the table AQDB, where extensive checks ensure that there are no inconsistent statuses in the table AQDB.
If you are transporting from one SAP system to another, you must first use the transport system to release and export the transport request generated by the export. This transports the transport dataset from the transport table TAQTS into the target system. Then, you can import from the target client of the target system, as described above.
The transport datasets generated by exports in the transport table TAQTS are not deleted after successful import unless this is explicitly requested. Therefore, you can import a transport dataset several times (when copying a functional area to several different clients, for example).
This report handles exports (generation of transport datasets), imports (reading of transport datasets) as well as the management (display and deletion) of transport datasets.
As transport action, you must specify one of the values EXPO (export), IMPO (import), SHOW (display transport dataset) or DELE (delete transport dataset).
Transport action EXPO (exports)
If you select the 'Test only' parameter when exporting (no blank characters), the system determines only those queries, InfoSets and user groups that would be selected according to the selections for transport described below and generates an appropriate log. A transport dataset is not generated in the table TAQTS. This allows you to check whether a selection really includes the queries, InfoSets and user groups to be transported.
With exports, there are four different options for selecting objects (user groups, InfoSets, queries) to be transported. These are 'Transport of user groups', 'Transport of InfoSets', 'Transport of InfoSets and queries' and 'Transport of queries'. You must choose exactly one of these transport types.
In each case, you can also define an import option depending on the transport type. This allows you to determine how the transport dataset is inserted in the table AQDB of the target client during a later import.
The import options, each of which has an abbreviated syntax,
are as follows:
REPLACE or R
MERGE    or M
GROUP=ug or G=ug    (ug = name of a user group)
UNASSIGN or U
If you use the transport type 'Transport of user groups', all user groups are transported according to the select option 'user groups' and the selected import option. The import options REPLACE and MERGE are allowed.
If you use the transport type 'Transport of InfoSets', all InfoSets are transported according to the select option 'InfoSet' and the selected import option. The import options REPLACE, MERGE, GROUP=ug and UNASSIGN are allowed.
If you select the transport type 'Transport of InfoSets and queries', all InfoSets are transported according to the select option 'InfoSets' and the selected import option. The import options REPLACE and MERGE are allowed. Also, all queries are transported for each functional area selected, according to the select option 'queries'. In this case, the user groups of the queries are irrelevant and only the import option REPLACE is allowed.
This transport type allows you to transport a modified InfoSet and all the associated queries.
For the transport type 'Transport of queries', all queries are transported according to the select option 'User groups' and the select option 'Queries' as well as the selected import option. The import options REPLACE and GROUP=ug are allowed.
The export log displays which user groups, which InfoSets and which queries are transported, as well as the import options used.
Transporting a user group
Transporting a user group means transporting all members of the group from the source client. However, the InfoSet assignment to the user group in the source client is NOT transported.
The import option REPLACE first deletes all members of the group in the target client and then enters the members from the source client.
The import option MERGE leaves all members of the group assigned in the target client and adds the members of the group from the source client.
Entering a new member in a user group in the target client is possible only if a user master record exists.
In the target client, the assignment of InfoSets to this user group remains.
Transporting an InfoSet
Transporting an InfoSet means transporting the InfoSet and the InfoSet assignment to user groups in the source client.
Importing an InfoSet is possible only if the same logical database exists in the target client. Extensive checking is also performed to ensure that there are no inconsistencies between the InfoSet and the logical database.
The import option REPLACE first deletes the assignment of the InfoSet to user groups in the target client, provided there are no queries dependent on the InfoSet. The InfoSet is then transported to the target client and the assignment of the InfoSet to user groups is copied from the source client, if user groups also exist in the target client.
The import option GROUP=ug first deletes the assignment of the InfoSet to user groups in the target client, provided there are no queries referring to the InfoSet. The InfoSet is then transported to the target client and assigned to the user group ug of the target client, if such a user group exists.
The import option MERGE leaves the assignment of the InfoSet to user groups in the target client and transports it to the target client. It then copies the assignment of the InfoSet to user groups from the source client if user groups also exist in the target client.
The import option UNASSIGN first deletes the assignment of the InfoSet to user groups in the target client, provided there are no queries referring to the InfoSet. The InfoSet is then transported to the target client. No assignment of the InfoSet to user groups is performed.
Transporting a query
Transporting a query means only the query itself is transported.
Importing a query is possible only if a corresponding user group (see below) and a corresponding InfoSet exist in the target client and if the InfoSet is assigned to the user group. To demonstrate the effect of the import options, suppose that the query has the name QU and belongs to the user group BQ in the source client.
The import option REPLACE overwrites the query QU of the user group BQ in the target client if the user group exists.
The import option GROUP=ug overwrites the query QU of the user group UG in the target client if the user group exists. In this case, the query is explicitly assigned to a user group in the target client. This target user group may be differnet from the user group in the source client.
Transport action IMPO (imports)
If you choose the 'Test only' parameter with imports, only a test import is performed. This means that the system performs checks as for a real import and generates an import log. The import log contains information on the locks that have to be set. With a test import, you can check whether a transport dataset can be imported without any problem and which changes it would make in the table AQDB of the target client. A test import itself never makes changes in the table AQDB of the target client.
All transport datasets are imported according to the select option 'transport request'. In this case, the system outputs a detailed log of all checks carried out and all changes made in the table AQDB.
If you select the parameter 'Delete after successful import', the transport dataset in the table TAQTS is deleted after the import of each transport dataset if no errors occur during the import.
Transport action SHOW (display)
All transport datasets included in the transport table TAQTS are output with name (also the name of the transport request) and contents in the form of an overview.
Transport action DELE (delete)
All transport datasets are deleted according to the select option 'transport request'. To avoid unintentional deletion, the select option 'transport request' must contain values, meaning that the transport action DELE is not performed if this select option is empty.
Transport of ABAP Query
I am involved in this upgrade project to 4.7
The users are not able to find any reports (in QA System) which were there before the upgrade in SQ01. But they can see them in production which is not yet upgraded. They want me to copy all the reports to the QA system now....I dont have any idea how to do that.
I remember a similar problem upgrading to 4.6C from 4.5B ......
Take a look at OOS note 672784.
You can transport queries between systems in SQ02 (hit the lorry button) or run program RSAQR3TR.
You download the infosets, queries etc into a file and load them into whichever system you wish.
Just wanted to share my experience of transporting queries:
I needed to move a user group, 2 infosets and 3 queries from a 4.6 system to a 4.7 system.
When I tried doing this via the SQ* transactions I did not get the import/export option, so instead ran RSAQR3TR.
Step 1. Run RSAQR3TR in 'old' system. Select EXPORT and specify the objects to be transported.
(System includes these in an automatically created transport request)
Step 2. Release this transport and request it be transported to 'new' system.
(This results in the entries being populated in transport table AQTDB in 'new' system).
Step 3. Run RSAQR3TR in 'new' system. Select IMPORT and tick the Overwrite checkbox. Specify the transport number in the field labelled 'dataset with imports'.
(RSAQR3TR gives the message that stuff has been imported OK).
Step 4. In my example I still couldn't find the queries, so ran RSAQR3TR one more time, this time specifying 'Copy Standard Area -> Global Area'.
(Now my queries etc were available in new system).
Perhaps there are better ways, but after 1.5 days of struggling I was glad to get this far.
regards,
Jai

Assigning a SAP Query to Transport Request

Hi Friends
I have a SAP Query, now I want it to transport to the other system, while saving the query it is not prompting for transport request. Is there any possibility to assign that SAP Query to a transport request, if yes, please let me know the process.
Regards
Praveen

Dear All,
This regarding creation of SAP Query .
Situation:
Infosets and User Groups were created in a DEV SERVER CLIENT 200 and saved in a request ie.REQ01
Now i wanted to create a Query QU01 in the Same User Group in DEV SERVER CLIENT 210 so i tried creating a Infoset but i get this error message
Note: I am not able to create & save an Infoset.
Message no. TK414
Diagnosis
You cannot edit request D01K901880 of user X00012, since this request is reserved for changes in client 200. You are logged on to client 210.
Can anyone clear this error? what is the solution?
Thanking You
Andrew

Problem in transporting generated program of SAP Query

<h5> Hi all,
I created a SAP query in development server and generated the program for the same, I transported the infoset and the user group etc. to the next server but couldnot transfer the program, since the program is not a Z Program, so coudlnot save it and capture it in request so that the same can be transported.
What could be the possible solution for the same????
Regards, </h5>

Yep, this gets a bit tricky. Remember that SAP Query is designed as an end-user tool. To this end, the creation of queries could be done in a productive environment. The maintenance of infosets could be restricted to Development systems only. I know that some sites do not allow this.
Through the use of authorisations, you could appoint an administrator to generate the queries in PRD for the users.
The name of the ABAP is a combination of the query name, infoset and the client number (I think - going from memory). You could possibly change the package name of the generated program and then attach it to a transport, but it becomes very messy and I wouldn't recommend it.

How to transport deletion of a SAP Query

Hi
I have a SAP query which I deleted in the development system through SQ01. How do I transport this deletion to production ? Is this possible, or should we be deleting it directly in production system ?
Many thanks,
Sanker

I am interested in this question too.
The deletion is written to the standard BEx transport. Is it possible to collect the deleted queries and transport the deletion to production somehow?

SAP Query(SQ01) need to be transported

Hi All,
I want to transport a tcode which is using SAP query. Now I am able to send the tcode to other system but when I go to SAP query under queries and standard query area I am not able to see the version management details. I also tried going to the SAP query report through double clicking on the report name under SE93, and when I am into the report it also does not show any version details. It says "No version found".
What I am thinking is just get the active request number from the version management and transport it to the other system.
Can anyone of you tell me how to transport a SAP query.
Thanks,
Mahen

Hello everyone,
I am having problem in fixing this up. Let me tell you all what I have done.
I first transported the tcode from souce system to target system.
Because I transported the tcode so in the target system. Tcode has the report/program name as it is existing in the source system.
Now when I transported the everything like user group, infoset and the query, I was able to see them in the target client. I tried to run the tcode.
Tcode does not run, It says there are inconsistensies in the tcode.
I tried to trouble shoot the problem. I found that when I was trying to run the tcode it was not able to find the report/program.
What I did was, I generated the program for SAP query existing in the target client.
When program was generated, I observed that It is different with the one that is currently existing for the tcode in the target client.
This is the main problem report name are different. When I see in the se93 report name is the old one which I transported from the source system for the tcode, but when I see the report name for the SAP query by going into SQ02 it is coming different. I want to know when you create the program name for the SAP query, On what basis is the namespace of the program generated.
SAP query program name existing for the tcode and in the source system and also in the target system(When you see it in se93) is :
AQ01FI==========ZBSAK_LFB1====
SAP query program name when I generated it in the target client is :
AQFKFI==========ZBSAK_LFB1====
Bythe way the query name is ZBSAK_LFB1
Kindly throw some light on this.
Thanks,
Mahen

How to transport SAP Query SQ01??

Hi All,
I am faced with a proble regarding the transportation of SAP query from the development system to the Production system.The following were the steps that I had taken:
Step 1. Run RSAQR3TR in 'old' system. Select EXPORT and specify the
objects to be transported.
(System includes these in an automatically created transport request)
Step 2. Release this transport and request it be transported to 'new'
system.
(This results in the entries being populated in transport table AQTDB
in 'new' system).
Step 3. Run RSAQR3TR in 'new' system. Select IMPORT and tick the
Overwrite checkbox. Specify the transport number in the field labelled
'dataset with imports'.
After I had done all these ,the changes were not reflecting in the test system.
Is there any steps missed ou in the transportation process or is there any other way of transporting the same???
Thanks and regards,
Rupesh

Hi Rupesh
run the program one emore time with
specifying Copy Standard Area -> Global Area.
regards
kishore

SAP Query Use and Transport Strategy

Anyone wish to share their experience in the use of SAP Query? We generally have an understanding that we don't want to be giving out this tool to end-users in Production. We would like to create queries, and when we wish to give them out we'll attach t-codes to them and roll them out.
However in practice, this is becoming difficult. An example is where in our gold client we create queries and then we would typically transport to our unit test client. But whenever we do an export, it generates a transport request. Before we are done testing we may end up with 10's of transports for a single query?
Anyone have some ideas on a transport strategy for SAP Query? How about it's use in Production? Our landscape for changes are typically DEV Gold -> DEV Test -> QAS -> PRD. We would ideally like our transport strategy for queries to match what we do for everything else.

HI,
Query objects are transported in different ways according to the query area in which they were created.
In order to know which transport options are available, you must first understand how query objects are created.
Standard Area
Query objects are stored in the client-specific table AQLDB. They are not connected to the Change and Transport Organizer.
Global Area
Query objects are stored in the cross-client table AQGDB. They are connected to the Change and Transport Organizer.
http://help.sap.com/saphelp_47x200/helpdata/en/d2/cb467f455611d189710000e8322d00/content.htm
Global area objects can be transported into other systems. Standard area query objects can not only be transported to other clients within their own system, but into all clients of other systems as well. In addition, query objects can be transported from the global query area to the standard query area and back within the same system.Transports are normally performed by the system administrator, not by end-users. For this reason, you need the appropriate authorizations
Check the below links for detailed explanation
Transporting Global Area Objects
http://help.sap.com/saphelp_47x200/helpdata/en/ec/052786a30411d1950a0000e82de14a/content.htm
Transporting Standard Area Objects
http://help.sap.com/saphelp_47x200/helpdata/en/ec/052789a30411d1950a0000e82de14a/content.htm
General Transport Description
http://help.sap.com/saphelp_47x200/helpdata/en/d2/cb4699455611d189710000e8322d00/content.htm
Generating Transporting Datasets
http://help.sap.com/saphelp_47x200/helpdata/en/d2/cb46a6455611d189710000e8322d00/content.htm
Reading Transport Datasets
http://help.sap.com/saphelp_47x200/helpdata/en/d2/cb46e7455611d189710000e8322d00/content.htm
Managing Transport Datasets
http://help.sap.com/saphelp_47x200/helpdata/en/d2/cb46f4455611d189710000e8322d00/content.htm
Transporting Objects between Query Areas
http://help.sap.com/saphelp_47x200/helpdata/en/ec/05278ca30411d1950a0000e82de14a/content.htm
I hope this solves your purpose.
Regards,
Vara
Message was edited by:
varaprasad bhagavatula

Transport standard variant of SAP Query

Hey,
I made a SAP Query with SQO1. Within the attributes of the query, I defined a standard variant.
How can I transport this variant.
When I go to maintain variant, I can click to program RSTRANSP.
When I try to execute, I get the following message "Function not possible for local/private objects". In the help it says that I have to create a transport for my program.
But my query is in a transport. I already transported the query to QAS and it works fine.
Do I have to put the program also in a transport? The program is SAP generated code with the following name "AQZZZISU========CP_METERS=====". I haven't transported the program but it is available in QAS. So I think I don't need to transport it.
Does anyone how I can transport my variant?
Thanks
Steven

I have attached the sap Query based on your idea. But I geting small probelm. Please help me on this.
The varient is created as Protected by default. I can't able to create the varient unprotected. Can you tell me how to create unprotected varient for SAP Query? becuase other user can't able to change the varient it is giving the error message with my user name as " No authorization to change the varient <varient name> Protected by <my user name>".
Please could you help me how to fix it. this issue?

Issue of transporting SAP Query

Dear All,
Pls let me know if we can transport SAP Query from 1 client to another. If yes, the way too as we need to transport it to the Production client.
Points would be awarded.
Thanks
Deepali

Hi,
one client
SQ02>Select infoset>click on transport button.
select export option
select infoset radio button and enter infoset name
deselect at the end delete after transport.
same process for query also.
This process generates transport request.
go to another client
sq02--->select infoset -->click on transport button
select import option
select infoset radio button and enter infoset name
deselect at the end delete after transport.
enter transport request at the end above delete after transport option
same process for query also
please let me know any issues
Thanks
Usha

Transport sap query from one client to another client

Hi,
how to transport the sap query from one client to another client.
Moderator Message: Basic Question
Edited by: kishan P on Sep 15, 2010 3:39 PM

use report "RSAQR3TR"
Moderator Message: Do not answer such basic questions
Edited by: kishan P on Sep 15, 2010 3:44 PM

SAP Query transport

Similar Messages

Maybe you are looking for