Transport of Abap Query

Hi,
Can anybody tel me how to transport Abap Query.

Hi,
ABAP/4 Query is a powerful tool to generate simple reports without any coding. ABAP/4 Query can generate the following 3 simple reports: Basic List: It is the simple reports. Statistics: Reports with statistical functions like Average, Percentages. Ranked Lists: For analytical reports. - For creating a ABAP/4 Query, programmer has to create user group and a functional group. Functional group can be created using with or without logical database table. Finally, assign user group to functional group. Finally, create a query on the functional group generated.
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.
regards,
vineela.

Similar Messages

Transporting an ABAP QUERY

Hi guys/gals,
I've created an abap query in testing client.
May I know how to transport the ABAP query into quality and production server??
Regards
Jiku

Hi Jiku,
Transaction SQ02 menu "Envrionment/transport" (=Ctrl+F3).
For transport, select "export" and the objects you want to transport.
This will generate a request which you'll be able to process normally.
An other solution is to download your object from the source system and then to upload it from your target system, if this one is open (and if you have the requested rights).
Reward if useful.
Regards,
Aneesh.

Transport of ABAP query to production server

Hi!
I have developed a report with ABAP query in development server with transaction codes SQ01, SQ02 AND SQ03 respectively.
I also got the program name from SQ01.
Now , how to attach a transaction code with the program that is generated from ABAP query and transport it to production server
successfully.
If the program is attached directly to the tr code through SE93 and transported----- program is not found in the pr. server.
pls help me out , requirement is very urgent.
points to be rewarded .
regards
Amit

hi amit,
if i understood correctly.is ur query and infoset transported or imported to production.
Regards,
sudheer

Transport request : ABAP QUERY

Friends,
Please help me to generate the Transport request for ABAP query.
I have modified an existing custom ABAP QUERY.
I have followed the following process, but unable to get the transport number.
Goto SQ02. Select the proper query area. Press the transport button in the application bar.
Now u have two options...
1. Download and upload
2. Export and import.
The first option downloads the user/infoset & query on ur local server and then using upload u can bring it into other system. The second option creats transport request and u can use the normal way of transporting to the other system.
When i try to do export to generate Transport request using above way, I am getting following information and transport request is not generated.
Export log : List of exported objects
Test export only
InfoSet ZCREDIT (import option REPLACE )
Query ZCREDIT of user group ZCREDIT (import option REPLACE )

Hi kpreddy reddy,
please try deselecting checkbox "test run". This should work.
I hope it helps. Best regards,
Alvaro

Transporting an ABAP query from DEV to QAS/PRD

Hi all,
I am trying to modify an existing query in DEV and move it to QAS and then to PRD. After making the changes in DEV, there was new transport request created, in which I had the changes for the query and in se93, i changed the name of the prog to the newly generated prog. after moving the transport to QAS, it is giving me a dump saying that the new prog generated in dev does not exist in QAS and hence the tcode does not work.
after that i tried with the standard SAP report "rsaqr3tr" and tried to make another transport assuming that the program would be together with the transaction and will be transported together. But this does not work.
I need help regarding this please - since it is an urgent rek - how do i transport the query after making changes to the already existing one - from DEV to QAS or PRD?
Please explain in detail where and what I am missing.
Thanks!
Related answers are appreciated and rewarded.

Hi Shyam.
I would like to suggest a few references,
[SDN - References for Query related to transport request|Query Related to Transport Request;
[SDN - Reference for Transport Management System (TMS)|Transport Management System (TMS) of R/3;
[SDN - Reference for Transport Request Problem|Transport reruest problem............;
[SDN - Reference for Transport request Query|Query Transport;
Hope that's usefull.
Good Luck & Regards.
Harsh Dave

How to get the transport request number of ABAP query.

I want to find out last Transport Request number used of a transporting changes Abap query from development to quality system.
Also is it possible to do some comparison on version existing in development and quality for abap query.

goto SE03 ..
In Object Directory -> Double click on
Change Object Directory Entries
Enter AQQU(This is for ABAP Query) in the modifiable box ..
press enter ...
Check this check box ... Enter the ABAP query and press F8.
Double click on the Query and in the popup click on the
Lock Overview ...
U'll find the request number ...
Edited by: Srinivas Gurram Reddy on Apr 2, 2008 6:53 PM

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

ABAP Query not transporting properly

Hi,
I m trying to transport an ABAP Query and infoset together in a single change request. The infoset of query has generated fine except for some warnings about currency. And the query is also running fine on development. But when I transport the infoset and query together to the quality client the transport log shows the transport as successful, but doesnt show the.
Activate inactive runtime objects at all.
Also the query and infoset have not been transported, I checked in SQ02.
Please see the transport log below. I dont know what I m doing wrong. I cant move the infoset and query separately to production, I have to move them together. Any suggestions, will give points for the right answer. Thanks for reading
QTD Master Data QA
600 Selection for Import 11/30/2006 17:08:14 (0) Successfully Completed
 Check Versions 11/30/2006 17:13:03 (0) Successfully Completed
 600 Selection for Import 11/30/2006 17:13:50 (4) Ended with Warning
 600 Import 11/30/2006 17:14:30 (0) Successfully Completed
5 Import steps not specific to transport request
Feedback after export or import 11/30/2006 17:13:15 (0) Successfully Completed

Hi
After transport the request from original system to destination system, you have to do the import.
So run trx SQ02, Enviroment->Transports
Here you should be in the same screen where you have created the request.
Now choose IMPORT options, Overwriting allowed chekbox ans insert the request number in Dataset with imports.
Max

ABAP Query transport problem

Dear All,
I need to copy queries from Standard Area to Global area. When I use the transport facility (SQ03 --> Environment --> transport), it does pop-up the transport workbench request screen at the first time. I created one transport request number for it. After that, I accidently deleted the transport request without released it first. Now I have problem to add back the queries into the new transport request since the prompt for transport workbench request is not pop-up even I successfully copied the query from standard area to global area.
Is there any suggested solution?. Thank you in advance for any suggestion.
Edited by: shahrir razlan on Apr 16, 2008 6:36 PM
Edited by: shahrir razlan on Apr 16, 2008 6:37 PM

chances are very very slim.. (i think zero) to delete a request, when it has objects .
so your statement - "I accidently deleted the transport request without released it first " doesnt sounds logical...
either you have removed your objects from the list before deleting the request..
but if that was teh case, then it shud pop up for new request..
as it is not asking for new request.... it is almost sure, that it is still in some request..
look hard in se01 - your request shud be there... description shud be something like 'transport for abap query'.

Question in ABAP query

Hello All:
I created ABAP query and when I transported the system created transport number but it also creates defualt description "transport for ABAP query". I did a mistake by not going to tranports and updating the description to something meaningful! I created several queries and all have same description "Transport for ABAP query" and when I go to se10 it does not tell me what query the transport is tied to!! Is there a way I can find the query I created based on tranport request number? Please help me.
Thanks.
Mithun

Hi Mithun,
Go into SQ02 or SQ03 and click the Transport button to get into the Query Transport functions (or you can execute RSAQR3TR from SA38).
Select the Display radiobutton at the top of the screen.
Input the transport number in the "Dataset with imports" field at the bottom of the screen.
Click execute and you will get a list of the Query Transport contents.
hope that helps
Points Appreciated
Robin

How Transportation of Adhoc Query is done through RSAQR3TR report.

Hi,
How Transportation of Adhoc Query is done through RSAQR3TR report.i want to transport a new usergroup, new infoset and a query from Develpment to Quality and Production.
I have gone through the documentation of the RSAQR3TR report and as well as the SAP library material, but still i am confused.
Please help

Hi,
http://www.sap-img.com/basis/transport-of-abap-query.htm
Hope this helps.
Regards,
Rashmi

ABAP Query: How to transport?

We have created one ABAP query in Development system. In Query we did some changes related to code.
We want to transport it to Quality system.For this we are running "RSAQR3TR" program in Devp System . through which we are exporting "User Group, Infoset, Query" in same sequesnce, Which is generating request.
After transporting it to Quality, We are Importing it by running same program.
User group, Infoset , And Query Layout is getting updated but it is not updating the code which we have added into the query.
Please advice

Hi Reddy,
For the second part of question :
When you create a abap query SAP generates a program at the background. You can copy that program to a Zprogram and assingn a Tcode to it.( You can add some more features to the report like drilldown etc.. )
Your technical consultant should be able to help you out on this .
Regards
Balaji

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

ABAP Query Transports

How to do ABAP Query Transports?

Hi,
Use the SAP std report - RSAQR3TR.
Reward points if helps.
Regards,
JLN

ABAP query transport issue

Hi,
   I have copied an abap query ZGA to ZGA_IND1 and changed the title to INDIA. I gave transport number and released and transported to Quality. A transaction has been assigned to this Query
But when I execute this query from Quality machine using transaction, it says program AQZZZGA=========ZGA_IND1======   is missing.
   Transaction code is transported but not the ABAP query program. I retransported and failed couple of times.
Not sure why underlying program is not transpoorted to Quality.
Any idea, what I am missing here.
Cheers.
Sudhaker

hi,
I guess the transaction code directly calls the generated ABAP program, which is the bad approach, because the generated ABAP program might have different names in different systems (like here). You have to create a transaction, which calls transaction START_REPORT with the following parameters/attributes filled :
D_SREPOVARI-REPORTTYPE= AQ "parameter indicating Abap Query
D_SREPOVARI-REPORT= '...' "Query User group
D_SREPOVARI-EXTDREPORT= '...' "Query name
Of course you have to replace the dots with real usergoup and query names. You create this transaction code in the development system and transport it to test and production. It will work everywhere (in case the query is transported as well).
hope this helps
ec

Transport of Abap Query

Similar Messages

Maybe you are looking for