Query Transported but doesnt reflect in target

Hi guys,
I had an existing Query in Validation. In Development, I added 5 new free characteristics and redid some key figures. It got sucessfully transported but the problem is in Validation, I still see the old Query. (Not the new one with new free characteristics and recalculatted Key figures)
It would be helpful if somebody can help me with this problem.

Hello,
I think you transported an old version of you query.
Now, you goto your DEV and collect your query & all associated query elements using transport connection and create a new request.
Cheers
Praveen

Similar Messages

Navigational Attribute Transported but not reflected.

Hi,
Couple of Navigational Attributes were transported from Dev to QA.
But its not reflecting in QA now.
In the Transport Log its giving the warning message message as,
Navigation attribute ZABCLOC_ZZLINETYPE1 is deleted (not in characteristic ZABCLOC)
Navigation attribute ZABCLOC_ZZABCLOC1 is deleted (not in characteristic ZABCLOC)
Please let me know, how to transport the required Navigational Attr from one system to another system
Thanks,
Sowrabh

if the primary object is not active then u will face issues..
here as its quality u can try deleting the P table content of the Infoobject and then try activating that infoobject in the Quality system with the program.. some this like it starts with RSDG or RSVDIOBJ Activate.. u can try this in ur system...
and then try reimporting it with the overwrite mode.. this is will solve ur issue.
thanks
Vishnu

Query parameter transaction,Query transported but not found in QAS

Hello all,
I have an issue with my custom transactions pointing to queries I created. Here is one of 2 examples:
I have a query in the Global and Standard areas in DEV. Here are my transaction parameters from SE93:
D_SREPOVARI-EXTDREPORT     QUE_JPTREMB_02
D_SREPOVARI-REPORTTYPE     AQ
D_SREPOVARI-REPORT     /SAPQUERY/H2/QUE_JPTREMB_02
This works perfectly fine in DEV, in all the clients.
I transported the query using the Export/Import function to QAS. My query in QAS exists only in the Standard Area. I am not able to export/import queries from the global area.
When I try to run the transaction in QAS, I get the following message:
"Query QUE_JPTREMB_02 does not exist in user group /SAPQUERY/H2"
Can any one tell me what is going on here? How can I resolve this issue? Does this have anything to do with global VS standard areas? How do I point the transaction to the Standard Area if that's the case?
All help appreciated, thank you so much.

Hi Jean,
What are the steps you have followed? If I remember correctly the following must be carried out in the following sequence.
1) Use RSAQR3TR to export the query, usergroup and infoset in dev system.
2) release the transports in Dev.
3) import the transports into QAS using STMS (normal Transport mechanism)
4) import the query, usergroup and infoset into QAS using RSAQR3TR
5) identify the ABAP program associated with the query in QAS system.
6) create a Transaction code in dev system, assign it to the same query program (even if it does not exist in DEV) and transport the tcodes into QAS.
7) Execute the query once using SQ01 and then try again using the transaction code.
(I do not know why steps 6 and 7 are necessary, but that is the way they have worked for me, if I omit the steps, the query program dumps)
Anyway, I hope the above helps.

Transport of Query successful, but changes not appeared in the report

Hi All,
I have 2 Queries(Normal and Total stock reports on the same InfoProvider) in Prd.
For that User asked me to add one characteristic to Free characteristics.
I added one characteristic in Free Characteristics to both Queries in Dev and i collected the Transport requests for both the queries in RSA1->TRANSPORT CONNECTIONS and gave it to basis guy, he transported successfully to PRD and for both the reports the changes reflected in the
query designer, while executed the Normal stock report the characteristic added in free characteristics appeared and while drill down the data is coming, but for the Total stock report the changes appeared in Query designer but on executing the report even the characteristic added to Freecharacteristics is not appearing in Navigation Pane.
Also with the same technical name of total stock report there are 2 reports appearing in query designer. what to do now.
Help me here asap..
Thanks,
Chaitu.
Edited by: chaithu218 on Jun 21, 2011 10:37 AM
Edited by: chaithu218 on Jun 21, 2011 10:40 AM

Hi Chaithu,
As you mentioned that you can see 2 versions by the same technical name in designer for total stock report, it is highly probable that the query you are changing and the query you are executing are different.
2 versions of a query can exist with the same technical name as the system identifies the queries by their UIDs, which would be different for both these versions of queries.Following are the things you need to check:
1) In development system too, do you have 2 versions?
2) In production system, check the UID for both verions of the query
3) In Dev system, make sure you modify the query with UID which is being executed, if it is available there. Else, you need to replace the query in prod with the one you have in Dev system.
2 versions by same technical name can exist if:
1) Someone created a query directly in Prod, and transported a query by same technical name from Dev system
2) or due to system refresh, copy, etc.
Hope it helps.
Thanks,
Abhishek.

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

In Journalization updates are not reflecting in target

Hi,
I am using Simple Journalization for SQL Server tables. Only the newly added rows are reflecting in the target but not the updated ones. I have inserted two rows and updated one row in source. Only the inserted records are reflecting in target and updated record is not reflecting in target.
When I check the intermediate(I$_CDC_TARGET) and JKM tables(J$CDC_SOURCE) both inserted and updated rows are there. Why this updated records are not reflecting in target?
Both Source and Target tables have Primary keys.
Thanks,
Naveen Suram

Hi,
I am using IKM SQL Incremental Update (row by row). Updated are coming to I$ table and I am able to see these records in Journal data also.
One doubt here: In my source no extra columns are coming...I refered JohnGoodwin blog...according to the blog...there should be some extra columns related to journal right? Why they are not coming?
First I have added the JKM to my model..then added the data source to CDC...then created a sunscriber...then started a Journal....
Any thing I am missing?
Thanks,
Naveen Suram

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

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

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

Report designer Query Transport issue!

Hello ALL,
Iu2019ve created a formatted report in Report designer the basis of which is a query developed in Query designer. Now the issue is Iu2019ve captured the query developed in Query designer by going to RSA1Transport connectionQuery Elements, but Iu2019m unable to capture the report designer query i.e when I try to search with this RD query name it says query does not exit.
Can someone please help, how I can transport this Query developed by Query designer.
Regards
Madhavi

Hi,
let me know the solution?
as i know , need to save and activate? and refresh in RSA1. you can find out your object.
regards.
Ram

I cant get my playlists to sync to iphone and when i connect and clIck on iphone device, the music folder doesnt reflect content of phone.

I cant sync playlists with phone. and when device connected, the music folder under devices reflects a music library which doesnt reflect itunes music content or conten4t of phone
ive done all i can think of and more

I am having the same problem. I have just tried this. Unplug iphone > open itunes > delete all music from itunes library > close itunes > re-open itunes > add music from original folder > plug in iphone > select songs > press sync > unplug iphone using eject button onscreen > checked phone .... still nothing in music folder on phone. On itunes the "On this iphone" tab the songs remain there but greyed out.

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

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.

My blackberry curve 8520's cursor moves but doesnt click

I bought a used blackberry , the week after i bought it I had issues with my buttons going crazy , I got that fix and it cost me about $ 14 U.S , now the buttons are working fine but my cursor moves but doesnt click, I use the Enter button to click,but i still cant zoom on browser pages, will I have to change the cursor ?
If so,is it worth fixing ? How much for a new one ? Or should i just change the device ?
Help =(
thanks !!
P.S : A battery pull did not resolve the issue

Hi Solidbass,
You need to consider updating/reinstalling your device OS again.
tanzim
If your query is resolved then please click on “Accept as Solution”
Click on the LIKE on the bottom right if the post deserves credit

I click on itunes but doesnt open and says send error report or dont send

i click on itunes but doesnt open and says send error report or dont send

You will need to provide more details as we cannot see your computer screen. Does this happen every time you launch LabVIEW? What version of LabVIEW are you using? What version of Windows? Does LabVIEW crash? If so, what were you doing at the time it crashed?

In my Macbook pro camera just doesnt go off. Everytime I start it starts but doesnt detect.

In my Macbook pro camera just doesnt go off. Everytime I start it starts but doesnt detect.

Hello Abhishekrkate
Start your troubleshooting with the article below; it will assist with different options to get your iSight Camera back up and running.
How to Troubleshoot iSight
http://support.apple.com/kb/ht2090
Regards,
-Norm G.

Query Transported but doesnt reflect in target

Similar Messages

Maybe you are looking for