Query Transport Request

HI,
I have created transport request for Bex Query. First time I created transport request , I collected all query and query elements apart from this two more additional components added to transport request ( No transport request open on that
query, Only display mode. I have created TP request for change mode)
"BW: LOIO Class Metadata and BW: PHIO Class Metadata ."
Next time i have tried with all grouping options in transport request, I have not seen
"BW: LOIO Class Metadata and BW: PHIO Class Metadata .".
anybody has idea why these "BW: LOIO Class Metadata and BW: PHIO Class Metadata ." components added transport request.
Please let me know if you have nay idea on this one.

Hi,
- Check in SE09/se10 for creating requests.
For collecting objects you have go Transport connection without missing the objects.
SE03 for checking the Request objects.
Go to transport connection in RSA1 Select u r Data target or report what ever it may be in development sys & select only necessary objectsu2026 click on transport optionu2026u2026it will ask the transport request create new req. go to SE-9 release the objectu2026go to STMS import u2026RELEASE The objects in quality sysu2026same procedure to production sys.
Thanks
sudhakar.

Similar Messages

ABAP Query transport request

Hi All,
We created an ABAP Query report for Transfer order address and it is system generated report. When I am trying to find the version management but is it showing no version found. Even I have created TR manunally and imported to quality system, But this program is not moved.
I have a doubt here this is system generated program that we cant import to other system or can we import?
Can you please let us know how can we transport ABAP query report?
Regards,
Jyothi CH.

Hi Jyothi,
Copy this report in another prog, save with package. that time it will be asking request. make request for this copy prog
so this way you can able to find transport request.
Regards,
Kunjan

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

BW Query transport request.

Hi Friends,
I have made some changes in the query and my test system is in open config.So my query is getting saved but transport request number is nt getting generated. I guess there is an option in RSA under transport connection in the menu bar....EDIT->Tranport-> Swich on /switch off standard...but i am ne sure what option needs to be selected.
Can any of u guys please help me in sorting out this issue.
Thanks in advance,
Soumya.

Hi soumya nair, Welcome to SDN.
To Collect query :
Goto RSA1 -> Transport connection --> Object Types --> Query Elements --> Query --> select required query --> drag and drop to right hand side.
Select required objects and transport.
Check: [How to Manage BW Transports|http://sapbwneelam.blogspot.com/2008/10/how-to-manage-bw-transports.html]
Hope it Helps
Srini

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

How to collect the deleted query in a transport request.

Hi Friends,
I have created a query and transported it to the Quality, the data content is all ok, except that i have not used the Project Naming conventions. Now i have a defect against my name for this. I have to copy the same query with the correct Naming convention and transport it.
My question is after copying the query with correct name i have to delete the old query (if not there would be 2 versions of the same query). How do i collect the deleted image of the query in a transport and send it to quality?.
I tried deleting a test query from Bex Designer, but this does not ask me for a transport. should i use RSZDELETE?. Not sure if it asks for a transport request when i delete the query.
Can someone pls tell me how to go about this?.
Thanks in advance.
BN

Hi BN,
I do agree that deleting directly in Quality and Prod is not good way and not recommeded.
I have not tried and deleted.But if the system is configured in such a way that if it doesnt ask for a request
then i feel you have no option.
If any object is deleted then you must have the deletion image collected into request at the same point when you are deleting.Because later when we go to transport connection we wont find the object itself.
What i think from your point as you said you have done earlier is you must have any open request regrding this query and when this query is deleted , the deletion image is also included in the same request.
So go to se03 and give your deleted query name and check all the requests.
Check in the requests when the deletion image is captured or not. we might be knowing that this is cpatured.
Regards
vamsi
Edited by: vamsi talluri on Nov 9, 2010 9:14 PM

Assigning a SAP Query to Transport Request

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

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

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

How to create a transport request with query and only with its structure.

HI guru,
how to create a transport request with query and only with its structure.transport request should not include any other query items like ( variables, conditions...etc)
thanks in advance.
venkata

Hi,
Goto RSA1 and then Transport Connection -> In SAP Transports select Object Types-> Query Elements -> Then select Query->Give Technical name of the query and then select for transfer. In the right side you can choose the components which you wanted to transport.
Regards,
anil

Unable to collect the changed query elements to a transportable request

Hi All,
I had saved the query changes to dummy request, now I have to collect the changed qurey elements in a transportable request. This I am doing in the transport connection tab in rsa1. Now I want to collect only the changed elements of the query, & not all the elements. I have made (changes) restriction to a key figure inside the keyfigure collum. Now when I try to make a collection of this to a transport request - I am unable to find it under the query elements in the transport collection.
Pls advice how to collect it in a transport request & move it?
Thanks & Reagrds,
Shreesh.

Hi Shreesh,
It may be collected under default request. You can collect changed objects by releasing default request.
aftre releasing default request
go transport connection(TX-RSOR) object type -
>query elements -
> Query--> collect your query.
Grouping option as only necessary object
then click on "Package"
then check for your objects if not checked against your query elements(which you want to collect), plz check. at the same time check for your query name it should also be checked then only query will carry the changes.
Hope this will help you.
Thanks,
Vijay.

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

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.

Query Changes Transport Request

I created TP request for query keyfigure properties decimal poing change.I imported TP request to GRA. I have not seen changes in GRA.
Query in GRA is Display mode. when i try to open the query i am getting message authorisation check is required.
anybody idea how to reflect the changes in GRA query keyfigure decimal point changes.
please let me know.

Hi,
You have to make sure that all the elements of the queries are captured in the transport request. For that, in transport connection, while capturing the query, filter on "ELEM" and include them in transport connection.
As for authorization, you will not have it except in development. Thatu2019s the reason why you can not change the query in GRA directly. You always have to transport the changes.
Regards,
Yogesh

Query - Finding Transport Request

Hello Everyone,
I have queries in different transport requests. Given a query, how do i find out the corresponding transport request it is associated with.
Thanks

Hi
There are a few way's.
here is quick one:
go to RSA1,'Transport Connection',Query here look for the Query name and copy its technical name.
next, goto se01 and list allthe open transports.
then, stand on the upper node and expand all (via right click).
now search for the Query tech string.
look at this example:
BD3K901829   EHAYUT       Repair
5 Elements of the Query Builder
08PZF7C9RLQDY096E84FDEP5P                                0FKIJTURI31LH2H7YB9QIH8RF                                0NFU8RCIYLVISNUB70IQN6653
0OPF8SUCLC6JYHIUS40FDPRTW
2KUERICC8W93EDPYQHDI24AH
Reg's
Edan

Find Query Name in Transport Request or In TR what are Queries.

Dear All,
I would like to find a Query Name in Transport Request(DEVK.....) or Vice-Versa in Transport Request (DEVK........), what are the queries are included. I created SAP Query using SQ01 and assigned the InfoSet. The query is succesfully executing and getting the required result but I dont know the Transport Request Number which was created. In stead of creating New request, I would like to know the existing Transport Request what are the Queries are assigned.
Regards,
Ujed.

Hi
If you have included the Query in Transport using SAP Query Transport tool, it creates Transport request and makes an entry in the table AQTDB. Check the table entries in the table AQTDB.
~~~Ganesh Kumar K.

Query Transport Request

Similar Messages

Maybe you are looking for