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.

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

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 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

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.

Transport Tool Not able to connect the DB

Hi,
When i check the Transport Tool in STMS i got this problem :
Link to database failed
This is tp version 372.04.08 (release 700, unicode enabled)
ERROR: No connect due to DbSl Load Lib Failure
ERROR: environment variable dbms_type is not set.
ERROR: Connect to S52 failed (20090729160937).
INFO: no trace information stored
tp returncode summary:
TOOLS: Highest return code of single steps was: 0
ERRORS: Highest tp internal error was: 0249
standard output from tp and from tools called by tp:
connect failed due to DbSL load lib fa..

set the enviroment varible based on your database software as per the link below.
[http://help.sap.com/saphelp_sm32/helpdata/EN/2b/f8993af7700577e10000000a11402f/content.htm]
Try to connect database manually using sqlplus if it is oracle.

Problem in Query Designer Tool Bar

Hi
In BI 7.0, Query Designer Tool Bar unable to see Table View. Is their any patch problem ?.
Thanks in advance
Mahesh.

OSS note: 1002271.
Reason and Prerequisites
After much discussion we have decided
not to include the table mode in BI 7.0.
Solution
There is (in our opinion) a better alternative to the table view:
Create a query with only one structure and use
Report Designer to design your own table view. This allows you
to arrange the columns and many other
formatting and grouping options as you wish.

Query transport-normal transport or BEx transport?

I could able to transport the backend objects but not sure about query transport. I would like to know difference between normal TRUCK transport and TRUCK-BEx transport in transport connection for queries. Can I use any or there are specific rules when to use what.

HI,
Bex transport truck mean you can create a global transport for you queries, when you transport your queries from dev to qa those queries wont be editable in development system unless you define this global transport. Everytime you make the changes in those queries these changes will be automatically gets updated in this global transport. Finally you dont have to retransport these changed queries, you have to simply release this global transport and the changes gets updated into quality server. The second transport truck is normal transport, and can be used to transport reports from dev to quality.
So bex transport is useful and you dont need to create a request after every change in report.
Hope this will help
regards,
ray

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

Dear All,
we want transport ABAP Queries from one SAP instance to another..these ABAP Queries under Global area (cross client).
please suggest me how to create a transport request to transport these old queries , one more thing is all standard area (client specific) queries are copied .
Regards,
Gopala.S

Check this link:
ABAP Query Transport request related
ABAP Query transport problem
Creating t.code for ABAP query and Transport it TO Production and run it .
Edited by: Afshad Irani on Jul 20, 2010 12:30 PM

STMS -- TRANSPORT TOOL ERROR DB CONNECT : LINK TO BD FAILED ? HELP

HAI,
     i have installed a new sandbox with SAP 4.7c x200 , on windows 2003 and 64 bit kernel.
I have to apply support packages to it .
After fresh installation , i configured TMS and now when i check the tp as
STMS>OVERVIEW>SYSTEMS>SAP SYSTEM>CHECK-->TRANSPORT TOOLS , there a tree structure opens and everything is fine except the tree part tp call having DB CONNECT : LINNK TO DATABASE FAILED AND
offline call having CONNECT FAILED DUOE TO DBSL LOAD FAIL
these two comes in yellow and when i follow the detail it gives a pop up message
as below:
      This is tp version 340.16.24 (release 640)
Warning: Parameter DBHOST is no longer used.
Warning: Parameter DBNAME is no longer used.
ERROR: No connect due to DbSl Load Lib Failure
ERROR: environment variable dbms_type is not set.
ERROR: Connect to UPG failed (20071102130751).
INFO: no trace information stored
tp returncode summary:
TOOLS: Highest return code of single steps was: 0
ERRORS: Highest tp internal error was: 0249
standard output from tp and from tools called by tp:
So when i apply package it stops in CHECK_REQUIREMENT PHASE indicating that connection with db failed, also whe i reun to connect it is giving everything fine
help me out
regards
manu

Hi,
please try to set the env variable 'dbms_type=mss' globally - just to make sure that we don't get confused here by specific users. I think tp should run under the account SAPService<SID>. Lets see what happens then...
Regards,
Sven

DB failed in transport tool test STMS

Hi all,
I have a problem. It looks simple but I tried to resolve it with known way without sucess.
I have two systems BWD (develop) and BWP (production).
I configured in stms domain and transport group for these systems. Auth on DIR_TRANS is set properly, variable SAPTRANSHOST is set in hosts file.
Tests in STMS of connection, transport tool and tsadm for BWD is ok. BWD is the domain controller.
When i'm testing BWP connection, tsadm are ok but transport tool return an error.
(dbms_type is not set. error code 0249.)
db is mssql.
I check env variables for user bwpadm and they disapear. I try to use ntenv2reg.exe but no variables are set.
I try to add from OS to user bwpadm all necessary variables but after restart they disapear.
Also I try to add these variables via regedit software-sap-bwp-enviroment and also after restart variables are missing.
I don't have any other idea how to do set these variables...
please help
Regards,
Michal

1. Check to see you are running the right kernel, sometimes a 32 bit kernel will actually run in a 64 bit environment, but when cycling the service the registry won't get updated.
2. Make sure you are running the latest version of the kernel.
3. Worst case, remove then add the service back in, do both with sapstartsrv.exe. When adding the service back, make sure to check the box which says use the user environment variable and put in the user running the service there.
4. The user environment variable should contain all the necessary information.

Query Admin Tool

Hello:
Can someone tell me if the criteria used in the query admin tool are actual delivered queries in peoplesoft? There is about 10 criteria that you can run but no way of dumping to excel so I was wondering if there are delivered queries for these criteria. Working in PS tools 8.49.09 on Financials 8.9
Thanks
Mike Allegretti

Query admin tool is a delivered tool from peoplesoft. but the devlopers in ur group might customize certain options while making queries run to database from excel sheets.
please paste the error that u get for further help... what kind of problems do u encounter in running the queries.
Thnks!

Disable Query Builder Tool access to end users

Hi,
Did any of you block the Query Builder Tool access to your end users?
In our Netweaver 2004s BI implementation, we have a special need to restric the access to Query Builder Tool. Mostly our users are using BEx Analyzer tool (Front end service pack- SP12). Any ideas in this regards would be highly appreciated? Of course I can restrict access on the back end that our end user is only able to read the Query. What I am looking what is, how to stop the user even from launching Query Builder tool?
Thanks
Jay Lakshmanan

Hi Altera,
If the role doesnt give access to transaction RRMX and if none of the Reporting Auth Objects (S_RS_COMP, S_RS_COMP1, S_RS_FOLD) exists, than the user will not have access to Query Builder.
Hope it helps.
Please award points if it is useful.
Thanks & Regards,
Santosh

Query transport

HI SDN,
A query transport is failed due to missing of Query object(Query name) and a variable. I have collected those those two elements in differerent request and transported sucessfully. Now in which sequence these transports should be sent to PRD?
Thanks

hi,
i think this failure normally happened to the query that has been transported when we add a new variable to the query, since the transported query changes will be recorded in BEx request and the new variable won't be recorded anywhere.
we transport the BEx request before the new variable, then we find out error,
and send a new request to transport the new variable, and re-import again in PRD the BEx request (you can mark to let the request can be transported again)
so i think if you remember to transport the variable first then it's fine but if you forget, still you can re-import BEx again.
hope this helps.

Query transport tool

Similar Messages

Maybe you are looking for