Infoset Query Transport

Hi All,
I have enhanced an ECC infoset query.From the data field I have added the new field in to a Field group.After transporting the infoset query in the Data field area the new field is getting reflected but the new field is not getting reflected under the Field Group area,Can anybody tell me how to transport an Infoset query,including the Field group?
Thanks
SREEJA
Edited by: Sreeja SSP on Aug 24, 2009 12:30 PM

Hi,
Can you please let me know how did you resolve the problem?
We have a scenario where in we have to add 17 fields to infoset which we have done. But these fields are not getting reflected in the data source.
Moreover in Infoset field group, if you click on the newly added field. On the below area you will get info about that field. There is a button which displays field queries. When I click on it, it displays messsage as 'No queries found'.
My question is - how to add those queries to that field.
Can you please help?
Thanks
Subodh

Similar Messages

Transport of infoset query urgent ?

Hi ,
any one can help me on this topic..
i want to transport the infoset query ..
please any body give the steps....regarding this topic..
regards,
goodyear,

Hi,
Goto SE10--> Find your request number (F5) -->ensure that you have all the required objects in your transport -->release all the tasks one by one by selecting the request and clicking on the red truck (F9) and finally release the request by selecting it and clicking on the red truck(F9).
Once you have released it, contact your Basis/Transport Administrators to import into the required target system.
Cheers,
Sree

Transport of infoset query

Hi ,
while i am doing transport in infoset query,i select the infoset and query and next i wnt to transfort and metioned there requried names of infoset &query. i done every thing ok but in SE10 transport organizer ...displaying request is wrong missing the system name and request number..
on this topic any body help me its urgent foe me..
thanks ,
good year..

Hello Good year,
Have you attached the objects to a transportable package?
When you created the transport request, did you make a note of the request number, did the system give any errors or messages while writing the object to the request?
If you do know the request number, goto SE10, and then press F5 and fill your request number and press enter, and then you should be able to see your request.
Cheers,
Sree

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

Infoset query to QA server

hi friends,
can we transfer an infoset query made from SQVi in dev to QA ?how????
Thanks,
Gaurav

you would have to convert your 'quickie' to a proper query using SQ01 -> Query -> Convert Quick View. But this would only be possible if you are working in the Standard Area (check: Environment, Query Areas) and you would have to be in the Global Area in order to make the thing transportable, so i guess there's no easy way to do it. i do not know of a way to 'push' a query from Standard to Global Area.

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 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 :transport number generation

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, I am getting information.
Export log : List of exported objects
Test export only
InfoSet ZCREDIT (import option REPLACE )
Query ZCREDIT of user group ZCREDIT (import option REPLACE )

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.

Reg:Infoset query Uploading..

Hi all,
I am facing problem in infoset query uploading.We have some queries in Old system we need them in ECC.I am using program RSAQR3TR to download and upload the queries (not import and export).
I am able to download but while uploading i am getting an error..
'F Error when generating transport dataset'....
Any inputs guys..
Thanks in advance,
KK
Edited by: krishna kishore on Apr 24, 2009 9:56 PM
Edited by: krishna kishore on Apr 27, 2009 4:02 PM

Hi all,
I am facing problem in infoset query uploading.We have some queries in Old system we need them in ECC.I am using program RSAQR3TR to download and upload the queries (not import and export).
I am able to download but while uploading i am getting an error..
'F Error when generating transport dataset'....
Any inputs guys..
Thanks in advance,
KK
Edited by: krishna kishore on Apr 24, 2009 9:56 PM
Edited by: krishna kishore on Apr 27, 2009 4:02 PM

Infoset query field changes

Hi All,
I have one issue.
I am changing length of one infoobject in DSO from 4 to 7 and also its description.
Now, infoset and infoset query existing on this DSO should also change with new length and description.
Could anyone please tell me how i can do this ?
I have tried "Adjust" option in infoset , but its not changing its length and description.
Thanks for the help !!

Hi,
Can i do this directly in production system.
Can we transport infoset and infoset query changes from developemt to production
Thanks

How to create infoset query

Hi,experts
Can anybody give me documents on infoset query and step by step showing how to create infosetquery. I will really greatful to you all.
Thanks
Preeti

Hi Preeti,
1. You can query the data using 'Listcube' transaction.
2. Instead of builing on tables, it sits on ODS (no need to worry about underlying tables).
3. Visible on the Bex 'info area' as like other infoproviders.
4. It generates additional key figure called 'Number of records' in the Bex. This will be useful for query.
5. No additional ABAP can be used. But in RSQ02, you can use piece of ABAP.
6. Queries created on data provider infoset can work like other queries including transport functionality.
Hope helps.
For more info check Re: Query on Infoset
Bye
Dinesh

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.

Data load failure with datasource Infoset Query

Dear Experts,
I had a data load failure today,where i am getting data from the datasource which was built on Infoset Query.
we had a source system upgrade and when i checked Infoset query in the development of Source sytem im getting the below message :
"Differences in field EKES-XBLNR
Output Length in Dictionary : 035
Output Length in Infoset : 020
Message was saying Adjust the INFOSET,I dont have authorisation to create the transport in the source system.I requested the respective person to Adjust the Infoset and also to regenerate the same and move to production system.
I think this will solve my problem,Please correct me if am wrong.
Regards,
Sunil Kumar.B

Hi Suman,
i am still facing the problem even after adjusting the Infoset.The problem is we are facing the short dump with length mismatch.
when i checked the Infoset we are taking the field xblnr from table EKES and data element for teh field was XBLNR_LONG(char-35) but when i checked the datasource in RSA2 the dataelement for XBLNR was showing as BBXBL(char20).
i think this was causing the problem and i checked in SQ02 we will take the field directly from the table and how there is chance to change the dataelement.
Please help me to correct the same.
Regards,
Sunil Kumar.B

Infoset query BI 7.0

Hi All BW gurus ,
i want a clear picture how to create an infoset query and when to go for infoset and infoset query in GENERIC Extaction . anyone pls send the screen shots how to create and extract data to bw side from infoset query ,
my email is [email protected],
100% points will be assined to the gurus
regards
Sherwin

<b>Look at</b>
http://help.sap.com/saphelp_erp2004/helpdata/en/92/43ec39d0383f09e10000000a11402f/frameset.htm
Re: Infoset
https://www.sdn.sap.com:443/irj/sdn/thread?threadid=199410&messageid=2217326
https://www.sdn.sap.com:443/irj/sdn/thread?threadid=189150&messageid=2113030

Infoset Query Transport

Similar Messages

Maybe you are looking for