Transport of query variant

Hi Experts,
Is transport of new variant (from development to production) for a query already available in production possible?
If yes, please guide on the same.
Regards,
Rohit

Rohit,
There are some issues with transporting queries already available in Production.
1. If the query was created natively in the Production System - delete the query using RSZDELETE before transporting to Production.
If the query was however transported into Production and then changed in Production - you need not delete anything before transporting.
In case of case 1 - this leads to duplicate queries in the production system.
Arun

Similar Messages

Can we transport BW QUERY VARIANT (created in DEV) to QAS and PRD?

Hi gurus,
I created a lot of QUERY VARIANT ( parameters saved when we execute queries ) in BW DEV.
I am using those variants in my Analisys Process Designer and i do not want to create again in QAS and PRD.
Somebody knows how to transport those variants?
Is possible to assign by SE03? What is the code that object?
Thanks for any Help!!!
Carlos Eduardo Olinto

I transported my Query Variants.
- Variants must be created in DEV
- Download the records from:
> tables
RSRVARIANT
RSRVARIANTDIR
RSRVARIANTTXT
> Filter Field: VARI = "Query Variants Code"
- Create request in DEV
- Assign R3TR TABU <Table name>
Tables:
RSRVARIANT
RSRVARIANTDIR
RSRVARIANTTXT
- Save the contents in each table (Only KEY FIELDS)
- Verify the Lenght in each field, it must be correct (no spaces for each Field)
I hope it helps you!
Carlos Eduardo

How to transport Query variant used in APD

Hello Experts,
I have created 2 query variants for a query in Development system. And, these variants are being used in APD. Now, when APD is transported to next system, query variants does not exist in next system, so cannot execute APD.
Please let me know how can i transport the query variants.
Note: Gone through SDN, and found, query variants can be transported through some tables.
Please let me any other possibile sloutions for the same.
Thanks
Lavanya

Hi Lavanya,
To the best of my knowledge, you cannot transport query variants. You have to manually create them in each system. The reason being, when you try to create variants through RSRT -> Query Variants, you are basically trying to create variants for a temporary program generated during run time!
These run time programs do not have TADIR entries (not transportable) and hence any sub elements (like variants) created on these programs are not transportable as well.
Actually you can export variants.Please follow the below steps:
1. Go To TCode SE38.
2. Execute "RSTRANSP".
3. Input your program name.
4. Input your variant name ie. "Z**** ".
5. Execute.
6. Click on continue.
7. You should be able to create a new transport at this point.
Hope It Helps,
Thanks,
Amit Kr.

Transport query variants

Hi,
I have a lot of query variant which I need in every system.
Is it possible to transport query variants? I already tried to transport the query and variable in the transport connection. Addionally I figured out that the variants are stored in table rsrvariant, but I'm not able to transport the entries.
Regards,
Karen

Hi,
Pls transport the table RSRVARIANT ,which contains the entry for all bex variants, all variants will be transported then.You should transport the table contents(via SE16 or SE10).Create a request in SE09 or SE10. From the context menu of the transport no, go to object list (or double click). On the next screen go to 'change' mode.Press 'add new entry' (plus icon).
Rgds,
Murali

Copy Query Variants from InfoCube to MultiProvider

Hi,
Is it possible to copy query variants from an infocube to a multiprovider?
Basically, we used RSZC to copy the queries from the infocube to the multiprovider, but it doesn't look like the variants were copied over. Is there an ABAP program or some other workaround that can expedite/facilitate in recreating the variants on the multiprovider queries?
Your help is much appreciated.
Thanks,
KK
Edited by: Kristin Kalalau on Jan 29, 2009 10:48 PM

It is possible to copy but the only requirement is your target cube structure should match with the source cube structure.
Thanks...
Shambhu
Edited by: Shambhu Kumar Gupta on Jan 30, 2009 12:01 PM

RC 8 error while transporting the query from Dev to Qa - Element missing

Hi All,
I have made a multiprovider by copying one existing one.
I have copies one of the Bex queries using RSZC from the source to Target MP.
While transporting the query from Dev to QA i have got the following error. (I have already moved the Multi Prov in a previous TR)
Has anyone seen similar types before. Any inputs will be highly appreciated.
Start of the after-import method RS_ELEM_AFTER_IMPORT for object type(s) ELEM (Activation Mode)
Error when activating element 4LUSZK561QN74UDBJ7BPU9GFM
Element 4LUSZJXHIS1HM7TVDD9DK7HPU is missing in version M
End of after import methode RS_ELEM_AFTER_IMPORT (Activation Mode) - runtime: 00:00:06
Start of the after-import method RS_ELEM_AFTER_IMPORT for object type(s) ELEM (Delete Mode)
End of after import methode RS_ELEM_AFTER_IMPORT (Delete Mode) - runtime: 00:00:14
Errors occurred during post-handling RS_AFTER_IMPORT for ELEM L
RS_AFTER_IMPORT belongs to package RS
The errors affect the following components:
   BW-WHM (Warehouse Management)
Post-import method RS_AFTER_IMPORT completed for ELEM L, date and time: 20110517070045
Post-import methods of change/transport request BDAK959603 completed
     Start of subsequent processing ... 20110517070025
     End of subsequent processing... 20110517070045
Kind regards,

Hi Jith,
First of all try to consolidate all your objects in a single TR and then move to Q from D.
In this case check for the list of objects that you have in your TRs. If TR 3 have all the Objects that were in TR1, TR2, then transporting TR3 alone will work.
Also, you can find the information related to the elements that were missed in your TR1,TR2 by following process.
1. Go to your transport Logs and then to the entries marked as Error.
2. There you will find the Query Element Ids, copy them
3. Now, go to Table(Se16) RSZELTDIR, there enter those query elements.
Now, you can able to find the elements that you have missed in your TRs. Hope this helps you.

Steps involved in transporting a query/workbook

Hello Gurus,
What are the steps/objects involved in transporting a query and a workbook to a particular user.
Should roles be transported with them?
Thanks for the help.
Simmi

Hi,
Please check the doc below which contains all about transports in BW.
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/3010ba90-0201-0010-2896-e58547c6757e
Also check the help site.
http://help.sap.com/saphelp_nw04s/helpdata/en/38/5ee7377a98c17fe10000009b38f842/content.htm
Regards,
®

How to disable GLOBAL query variants in Portal (ANALYSIS Template)

Hello Experts,
Does anybody know how to disable the saving of global query variants on the selection screen?
Currently if anybody goes in and saves the variant with Description and puts something in the Technical Name, it saves that variant as global, so that everybody can see it. If they put something in the description only and leave the technical name blank, then it saves the variant as local. Therefore, how would I go about disabling the saving of global query variants?
Thank you,
Andrei
Message was edited by:
AG

This object S_ALV_LAYOgoverns the way ALV layouts are saved.
For more info see the OSS Note 601803.
Hope This Helps
Anand Raj

Bex Query variants not working

Hello Experts,
I have a unique problem with one of my queries, the query variants which are created before Nov 1 are not fetching any vaules instead it gives a message MAKE ENTRY IN ALL THE FIELDS......
the variants which are created in Nov are working fine.....we have not done any upgrade....
does anyone faced this kind of problem? what needs to done to get back the variant values in the selection screen.
Any help is highly appreciated.
Regards

Was there a change to an InfoObject that is in the InfoProvider that is also one of the query input options?
e.g. IO ZHARA used to be defeined as a Char with a length of 4, but was changed after Nov 1 to Char, length of 8.
If you change an IO like this that is in the variant, that will render the variant unusable.
There is a program that checks for variants that have been broken like this, and another that you enter the query's technical name and it repairs the variant.
Try a search on SDN for something like "query variant program". I'll post the program names after I get back in the office tomorrow.

Creating transport in Query designer

Hi Guys,
I am trying to create a transport in query designer before i make any changes to the query, how do i go about doing this please?
Thanks

Hi,
You can also goto SE01/SE09/SE10 tcodes and create a workbench transport from there. Modify you r query and attach it to the transport you created. But the best practice is to create it through the transport connection.
Also check the threads below on creating Query transports :
Correctly transport BEx queries
http://help.sap.com/saphelp_nw04/helpdata/en/d2/cb467f455611d189710000e8322d00/frameset.htm
Cheers,
Kedar

Transport an Query without the standard transport system

Hello Experts,
is there a function (similar to the report-painter-reports) to transport a query via pc to an other system?

Jurgen,
As pointed out , it is not possible to transport from production to another system without using the transports , however the query would be under a request in production , you could then use that request to transport the query into another system either by specifying a transport connection or manually importing the data and co files...
Arun
Hope it 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.

Transport of query

hi all,
When i try to create a transport request for a query a local request is created.which i cannot transport.this query is in standard area.please help me to transport query.
thanks ,
mahesh

Hi Mahesh,
The query which u want to transport is makes sure that it is under a particular devlopment class.
U can create ur development class including all the includes and make sure to include in transport.
reward if useful..
thanks and regards
suma

Creating Query Variant

Hi,
I am trying to create a query variant in BI7. I want the values to be populated from TVARVC table. In RSRT, if i am giving Create variant, i am getting the next screen to enter the values.(same as we get in 3.5). but it does not show the query fields. It is showing these fields in attributes.
Query
HTML
URL
URL2
URL3
URL4
Where i can get the query fields (Like in 3.5) to populate from TVARVC table?
Thanks Pravender.

If you are on BI 7 better to handle the variants in table RSRVARIANT than TVARVC.
You can write code to update the table RSRVARIANT as per requirement.
Hope this helps.

How to transport a transaction variant and her related screen variant?

Hello to every SDN member,
I am looking to transport a transaction variant and the related screen variants.
I read the help and I am concerned by the paragraph about the Client-specific transaction variants because when I created the transaction variant, no dialog box appeared.
In the paragraph about the Client-specific transaction variants, it is told to transport the variants with the Transport function but the problem is that I cannot find it. How can I use this function? It is not in the toolbar and not in the differents menus.
Can you please give me the solution to transport the transaction variant and the screen variant?
Thank you very much in advance.
Best regards,
Matthieu Chérier

Hi,
You can transport a variant by :
1. Running the program RSTRANSP. Mention your program and variant name there.
2.Create a variant with prefix 'CUS&'. This type of variants will be automatically transported to target system through transport request.
3.Go to Se38 --> Input report name --> Select Variants
On the screen --> Go to Utilities -> Select transport request
--> Provide the program name and Variant --> Assign Transport request to variant. Then release the transport.
Regards.

Transport of query variant

Similar Messages

Maybe you are looking for