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

Similar Messages

How to transfer ABAP query from one server to another server

Hi all,
I have a ABAP query in development server and i need to transport it to production server.
I have attached a transaction to it using the program which got generated in the back ground
from the abap query in the developemnt server.
I have downloaded and uploaded a ABAP query from one server to another server.
But the program which got generated in the back ground in the production server is different from
program which is generated in the development server.
But my transaction is attached to the program in the development server.If i transport the transaction
to production server,it is giving error since that program is not present in the production server.
Am i going in the right way......?
Is there any problem in my upload/download procedure ?
Is there any way to achieve my purpose ...............?
Please kindly reply me at the earliest.

You have different ways to call a query using a t.code. One way is to create a pgm with the following code and attach a t-code to it.
data: gv_test type sy-repid.
DATA: GV_USERGROUP TYPE AQADEF-BGNAME VALUE 'FI',
 GV_QUERY TYPE AQADEF-QUNAME VALUE 'ZCON_FI_QUERY',
 GV_RNAME TYPE AQADEF-PGNAME .
CALL FUNCTION 'RSAQ_REPORT_NAME'
EXPORTING
 WORKSPACE = ''
 USERGROUP = GV_USERGROUP
 QUERY = GV_QUERY
IMPORTING
 REPORTNAME = GV_RNAME
* For the dynamic excution of the called query assisgn GV_RNAME to <gv_test>.
gv_test = GV_RNAME.
SUBMIT (gv_test) via selection-screen and return.
Alternate way is while creating T-Code you choose option Transaction with parameters.
Transaction as START_REPORT and in default values table control at bottom give as follows
D_SREPOVARI-REPORTTYPE = AQ
D_SREPOVARI-REPORT = User group
D_SREPOVARI-EXTDREPORT = Your Query name
Regards
Sathar

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.

I have deleted one query from production server

some one have deleted one query from production server. i would like to know who has deleted that query.
pls let me ASAP.
regards
raja

Hi,
You can get the time stamp( when it was deleted) from table RSRDELREPORTS. Based on that time check with basis guys to get the more info.
regards,
raju

How to transport infoset query to Production serveR?

when i transport everything is transported to production server. when i run the transaction in production server it shows me the error saying . PROGRAM Does not exist .. how to resolve this..
can any one help me to transport my infoset query from step-to-step.
Regards
Saad Nisar

Well there is no button as such.
I hope you must have found the Transport button.
When you click it, it gives selection screen there you can find the redio buttons.
Export will create a transport request and Download will download it to local machine.
Let me know if it doesn't work. But you have to do more analysis as to how to go this way.
Regards
Shital

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

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.

Transporting object from development to production server

Hi Everyone,
Could you plz tell me how can i transport a object from development server to production serevr if that object is local in production server. And also could u tell me if the transfer structure is replaced if the names are different in both the server???

Could you plz tell me how can i transport a object from development server to production serevr if that object is local in production server.
Case 1: Object is in Prod, but not in Dev. and you want to align the systems through transports.
You will have to send it to D (which could be done by changing transport routes & then following normal transport procedure) & then will have to bring it back with overwrite originals.
Case 2: Object is present both in Prod & Dev.
You can send the transports D->P with Overwrite originals (following the transport procedures).
And also could u tell me if the transfer structure is replaced if the names are different in both the server???
If technical names are different in both the servers, the transfer structure will not be overwritten.

How to transport requests from development to production server

hi gurus
i am new to SDN
can u pls give me detailed information how to transport requests from development server to production server?if possible give me screen shot documents
regards
surya

Hi
Transporting
There are help pages that discuss creation of transports.
In simple terms, you: create a transport package
add objects to the package export the package, plus optionally any related objects to a predefined folder/directory on the portal server into a file with an extension of .EPA copy the .EPA file to the import folder of your QA system and import it test the contents on the QA system copy the .EPA file to the import folder of your production system and import it Create a transport package file
Here is the step by step procedure to create a transport package:
For Export
1. Go to system administration, and click on transport?export.
2. In the middle pane, select the folder you want to export and right click on the Transport Package. 3. Fill in the General Properties i.e the name of the package, id and description. 4. And say finish and open the object for editing.
5. When the object has been opened then right click on the object you want to transport, and say "Add object to the Transport Package".
6. Check the checkbox of the item u have added and see the properties if it has been added properly. 7. Now click on the save button.
8. After the object is saved, click on the export button. 9. U will have an option to select where to store the .epa file which will be generated. U can overwrite an existing one by selecting the browse button, or store it with the generated name in the location it automatically generates. 10. Now Click on the Start Export button.
11. once the export is completed, it shows a report on how much time is taken to generate the .epa file. 12. Here there is an option for downloading the .epa file. Click on the link and download the file. This file is ready to be uploaded into any other EP Server.
For Import:
Pre-requisites: You have to copy the .epa file created while export into the local drive. Optionally, you have to manually copy the .epa file generated in the export function into the Import directory of the server ie. chooseFollow the steps below for importing a certain file. 1. Go to System Administration in the portal, and click on Transport?Import. 2. For the source of the package, Click on the radio button Server for the .epa file you have copied lately. Else, click on the radio button on client if you are operating in the client and select the .epa file you have stored on the local drive. 3. Now select the file from the browse option and click on Upload.
4. Now click on the import button. 5. Once the import process is finished, the report is shown. In the whole process, the par files are not included in the .epa files. For the par files to be included into the .epa files then we have to change the pcdStartup.properties file in the server. The property to be changed is Pcd.TransportApplication.Export.ExcludeObjectTypesAfterRuleProcessing: Keep this property's value as empty for enabling the par files to be uploaded into the .epa. You can check for this property in the portal in the following -System Administration-Support-Portal Content Directory-PCD Configuration.

Deleting query in production server

Hi,
Some of the duplicate queries are deleted in Development server, which are not transported to other servers by some mistakes.
Now we need to delete those duplicate queries in production server.
Plsease suggest immediately.
Regards,
Archana

Hi,
use the Tcode RSZDELETE.
If you dont have authorization use the program COMPONENT_REORG.
Regds,
Shashank

Import issue for ABAP program in Production Server ?

Hi Experts,
I have an ABAP program which gets executed properly in BW Development server but getting the following error when I am trying to execute it in the BW Production while I could activate the program successfully.
Kindly help me to resolve this issue.
Thanks in advance !!!
Regards,
Gokulkumar RD

Hi Golkul,
Can you debug the program while execute?
I think there is some hardcoding in the program for checkiing the client and then raised a custom message in the program.
Can you share the coding of the prorgam if possible?
Try to check for any messages raised in the program. Also click on the on the message pop up and see the details on the message and let us know.
Thanks
Amit

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

ABAP query changes

Hi All
I have one abap query in Production server.
1. I wanted to know if there is any way to know who has done the changes and when.
2. If i want to transfer the query from test server to productions server then how can I do that?

Ans for your first question 1. SQ01 - > Select your query - > in the Menu Select Extras -> Status Information
Ans for your second question 2. SQ02 -> Environment - >Transports ->fill all the required values and execute.
Regards
Sasi
Edited by: sasikumar palanichamy on Dec 29, 2008 2:04 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

Transport of ABAP query to production server

Similar Messages

Maybe you are looking for