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

Similar Messages

Query transport tool

guys,
we have a few queries, infosets and user groups created in our development system. I can see them all in the Global area. Now i want to export them to my qa system but when I open the query transport tool, I do not see options like export, import, download etc. However, I see these options when i execute report RSAQR3TR from SE38. But when i execute this report using export option, I get the message no object found !! I can see these queries, infosets from sq01, sq02 just fine.
If I go back to the transport tool from sq01, I see that there are two options: copy standard area ---> global area, executing which gives me no object found message again. But if i execute the option copy global area -
> standard area (in test mode), i get results. But why would I do that if my queries are already there in the global area and I want to transport them to another system???
please advise.

Hi Mahajan,
The reason why the radio buttons do not appear is because the queries are in the global area and hence they are cross client.
To transport them I would suggest assigning them to packages and hence it would either create a transport request right then or you can then use the option of the transport icon.
To change the package of the query .
Goto SQ02 and choose the infoset .
Then goto menu Infoset->More functions-> Change Package.
This will assign your queries to a Development class(package) and then using transport requests move them to the client that you require.

Converting SAP Query to Report Program

Hello Experts,
I'm stuck up with an issue.
I want to convert SAP query into a report program as the things which I need to implement is not possible with SAP Query anymore.
So I need to convert SAP query to Report program.
I'm very much aware about the SQ01--> Query --> More functions --> Display Report Program
But this Report Program generates is AQ..................... but if you see the code there will be buch of dynamic calls not as clear as ABAP code and not much flexibility to modify...
Please Provide a solution to this.
Regards,
Titiksha

Hi Bhange,
Glen Anthony has said very well and I support him. Even I suggest you to ignor the report generated with Query and develop a new report with the required business logic.
Regards,
Vijay

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

Declarations in SAP QUERY generated ABAP Programs

hi,
i had created a ABAP Program through ABAP Query (SQ01,SQ02,SQ03) but i have a issue that when i transport it to the PRD server i got the run time error. The Z program which i had created is the copy of the SQ01 generated program and i had done all the includes declarations in this program. but there is a problem that it is consist of the declarations of the structures,quries .
I want to know is it necessary to always transport the Infoset and user group and the structure which is present in the program generated .
Please provide me guidelines for this problem .
Edited by: ricx .s on Jul 6, 2009 5:31 AM
Edited by: ricx .s on Jul 6, 2009 8:07 AM

hi,
i had copied the program bcoz i want to chekc that it is really necessary to transport the user group and infoset so that it can achieve functionality similar to the SAP QUERY.
is there any other way without whichi can ahieve the functionality of SAP QUERY generated program and take it into the ABAP Porgram?

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

How to call SAP query in a program

Hi experts
I have created a query in SQVI its gives a result. Now i want this query to be used in my program. Is there any FM which gets the quary name and populates the result in iternal table. So that i can use that result.
I know without query you can write using the tables you can fetch the records but i just want to explore a new way to do things. If any body done such type let me know and also give some sample code or process how to achieve it.
Regards
Vijay

Hi Siva
My final option is that only. That you can do any how. But my intension is to learn something new way. How to do copy the query and where to inject the code is there any example in wiki or artical for that. I want to something new. Old way of creating a report program is possible i want to do this way. If some body could help me out.
@ karthik
I have generated the SAP query and i got the program but when i view the code i dont find any select statment or where storing my input data. How to identity that i did in debug mode but am not sure where it pulls the data and where it put in internal table. Can you throw some light with example code or an article.
Regards
Vijay

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

Issue with SAP query

Hi experts,
I not able to download the user group , infoset and query through standard program RSAQR3TR, even though the user group, infoset and query exists.
i. e with download option in RSAQR3TR prgram.
so, can u please guide what exactly might be the problem .
or is there any other way to download the user group, infoset and query.

Did you create transaction for query or did you create transaction for the program generated by the query?
For queries the programs are dynamically generated in every system/client when they are transported. So the program name would be different in each system even though the query infosets etc are same.
What you have to do is create a parameter transaction (for query).
In the screen of SE93 give the following informations
Transaction will be - START_REPORT
Down at the bottom define the following parameters as per your Query/infoset
D_SREPOVARI-REPORTTYPE     AQ (for abap query)
D_SREPOVARI-REPORT     Z_abap_qryname
D_SREPOVARI-VARIANT     a_any_variable_for_report
Hope this helps.
<removed_by_moderator>
FY
Edited by: Julius Bussche on Aug 26, 2008 11:41 AM

Adhoc Query Vs SAP query

Hi friends,
Is there any difference between Adhoc query and SAP query.

ADHOC QUERY:-
Web item that enables you to create and change ad hoc queries in a Web application. You can use the Web item Ad-hoc Query Designer in the Web Application Designer to design Web applications in which you can create or change queries.
SAP QUERY:-
A tool that allows users who have no knowledge of the ABAP programming language to define and execute their own reports.
To determine the structure of reports in SAP Query, you just have to enter texts, and select fields and options. If necessary, you can edit lists using Drag&Drop and the functions in the available toolbars.
bye
Naveen

Re: Info set and query transport under same request number

Hi,
I would like to know the details about info set and query transport from development to quality using SAP Query: Trnasport tool.my quesion is,
Can i create all info sets and related queries under same request number or will it be created in diffrent request numbers?Please respond any body to my question.
Regards,
Suresh Kumar.

No it is possible as per SAP.
Please read follwoing help-
http://help.sap.com/saphelp_nw70/helpdata/en/e3/e60138fede083de10000009b38f8cf/frameset.htm
It is talking abou the Special Features of InfoCubes in InfoSets.
For queries based on an InfoSet with an InfoCube, the system decides at runtime whether aggregates can be used for the InfoCube. This is the case if all the required InfoObjects of the InfoCube exist in an aggregate. The following InfoObjects are required:
The key figures of the InfoCube selected in the query
The characteristics of the InfoCube selected in the query
The characteristics required for a join with other InfoProviders in the InfoSet.
Furthermore, as a prerequisite for using aggregates, all the data required by an InfoCube must be readable using logical access. For an InfoCube within an InfoSet with InfoCubes, it is no longer possible to read part of the data from one aggregate and part of the data from another aggregate or the InfoCube itself.

How to find which Query is using program AQ10MM==========Z6============

Hi,
I wanted to know how to find out which SAP query uses this program. AQ10MM==========Z6============
I tried with SQ01/02 but was unable to get it. Can you please help.
Regards,
Mukund S

In my installation , it is usually AQZZ"usergroup"========QUERYNAME======
You could see if you have a user group 'MM' or '10MM' in SQ03 and set the user group if available.. then in SQ01, see if you have a query called Z6
Also try out this function module RSAQ_DECODE_REPORT_NAME to see if it would give you the user group and query name...

ABAP Query transports not handled by CHARM

Hi,
How should ABAP query transports be handled in CHARM??
The ABAP query transport tool doesn't allow picking a transport that is already created (Own transport), it creates a new transports which is outside of CHARM. I had to assign the objects in the transport manually to the appropriate CHARM transport.
Any ideas???
ABAP query don't seem to be using the standard transport tool.
Thanks
Stephane

Hi
Instead of assigning the objects you can directly assign the trasnports to the charm task list of the project
check q22 (registerting transport created outside of charm)
Change Request Management scenario: Usual questions and known errors
hope it clarifies
regards
prakhar

SAP Query: Transport tool(program: RSAQR3TR)

Similar Messages

Maybe you are looking for