Cannot save query variant in RSRT

I am trying to create query variants in RSRT. I am able to do it for most of the queries. But there are couple of queries for which I am not able to save it. Has anyone come across this issue before.
FYI - We are right now on SAP 7.31 and SP 4.
Thanks,
Kal

Hi Kal,
Did you upgraded to BW7.31 recently?. if yes, run the report: RSR_VARIANT_XPRA.. This is the post upgrade activity. Can you check with the basis team run the same first in SAN system and then in actual landscape.
Regards,
Rajesh

Similar Messages

Query variant in rsrt

In RSRT, there is an option to create a query variant. How can we use this? I have a variable on 0calmonth and I want to create variants based on this so I can use it in a APD process. How can I do this? Thanks

Hi Uday,
You can create and maintain the query variants in RSRT. Type in the name of the query and click to execute it. The variable screen will pop-up and you can create the variant here. Or also you can click onthe Variants button and change any existing variants as required.
Hope this helps...

Cannot save query as local object

Dear community,
One of our users is not able to save a query change as a local object (not to be transported). While another user is able to do this.
Since we don't want the query changes to be transported, I must find a way to allow the save as local object in $TMP.
An authorizations trace shows everything is OK from job role perspective.
When the user changes a query in development and chooses "Save As", she is prompted for a transport. At this time if she chooses "local object" then she is taken to the create a transport dialog.
For another user this is not the case, and the 2nd user is able to save query changes locally without a transport request.
Any thoughts on what might be the cause for this ?

Hi Keith,
without knowing the details of you system settings and the system where it happens (prod, dev, ...). One general remark:
If you save a query lots of repository objects are generated an written to a transport request (i.e. structures, selections, ...), not only one for the query itself. Maybe in your case, the original query uses a globally defined structure in the columns or rows. If you now want to "save as" new query, many objects are checked for transportation. The global structure can not be saved as local object, because it was already transported before. Whilst the new query itself can be stored as local object. Means not all objects of the new query can be saved as local, because some are already transported.
One way to check if this could also be your problem, both of your mentioned example users should try to save exactly the same query as new local query.
Regards
Adios

Oracle 10g Express Edition: cannot save query

Hi everyone,
anyone knows if there's a limit of characters to save queries? I'm trying to save a query 2520 characters long, but I can't. I don't get any error message either.
Thanks in advance.

Hello,
Which tool do you use to edit and "save" your query ? sqlplus ? sqldeveloper ?
Did you try to create a view so as to simplify your query ? or to store your query in an external script "<script>.sql" ?
Best regards,
Jean-Valentin

Cannot save query in SAP 2007 Patch 11

Hi,
I urgently need assistance here.
We have created a query in SAP B1 2007 Patch 11. However, when we save the query, we received the following error.
'To generate this document, first define the numbering series in the Adminsitration module'.
To make it slight completed, we copy some queries from another company using Copy Express.
Your advice is highly appreciated.

Dear,
Please give the link to download PL15
Thanks in advance
Gauraw

FBCJ: Print cash journal, cannot save own variant

Dear experts,
We have implemented SAP in our romanian company and have implemented country specific settings.
We have a problem saving our own layout in the 'Print cash journal' in transaction code FBCJ. We have the possibility of changing the layout, but not saving it. Also the headers of the different columns remain the same even though column content is changed.
In customizing the following settings have been made (transaction code FBCJC3):
Company Code:                         0028
Cash jour. print program:           /CEECV/RO_RFCASH00
Report variant:                           CASHRO
Corr.:                                          SAP01
I don't quite understand the impact of these settings.
In our setup for 'Print cash jorunal' for our polish company we have the possibility of saving our own layout. But for our romanian company we don't.
Any help would be appreciated
Thank you
Regards Naja

Hi,
Business area put it optional entry, if u want business area enret other wise leave it,
now u will try it will work
if it's useful assigne points
Regards
gvr

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.

Tables where BEx query variants are saved (BI 7.0)

Hi Experts,
I'm looking for the BI tables where BEx 7.0 saves query variants, but I don't find nothing.
In BW 3.5 there were Table RSRVARIANT, but in BI 7.0?
Could someone help me?
Thanks in advanced
Fede

Hi Sunmit,
thanks, I found my query variants RSRPARAMETRIZA.
In RSRPARAMETRIZA there aren't information about single variable who make the variant!
In RSRVARIANT I find only variants I have created with Business explorer 3.5.
All variants of queries I have created with BEx 7 aren't in RSRVARIANT,
Should I have them in RSRVARIANT?!
or There is another table for those information about variant query of BEx 7.0...
bye
Fede

Query variant with exit variable on selection

Hello,
I have created a query with exit variable for Date. This date will be defauled to system date -1 using the exit code.
This variable is ready for input with default value. If user want to change the default value he can change it.
however when i save the variant for this query, the default value is not getting populated automatically. The value of this field in variant is date on which the variant is created.
Is there ay way to make sure the variant will always pick up the value from Exit

Hi,
I am trying to create a variant from web template.
In web template, i am not getting this option of not saving value for calendar day.
I think this option is available only from RSRT.

Query Variants in 2004s

Hi Gurus,
I am saving variants on the bEx query prompt in 2004s.But I dont find them when I run the query again in BEX or in RSRT. I see that entries are not maintaind in the table RSRVARIANTDIR.
When I run the same query in RSRT and save the variants there, then the entries are maintained in the above table.
I checked the same in 3.5 and in 3.5, if i save the variabts in BEX, the entries are maintained in the table and are avaiulable for selection when run the next time.
I am assuming thus that this is a bug. Has some one faced the same in 2004s? If not can folks who are on 2004s try this out and let me know.
We are on BW SP 11 and FEP 12.
Thanks in advance ! Needless to say, points would be awarded....
Prakash

Hello All,
As I was debugging (in RSRT), the code traverses through the INSERT commands in the class CL_RSR_QUERY_VARIANT where it inserts values of the variants in the RSRVARIANT, RSRVARIANTTXT etc tables.
I am assuming that this insertion is not happening or the internal tables where these values are stored for insertion are empty WHEN THE VARIANTS are attempted to be maintained through BEX.
My question is how do i get into the debug mode (into the code) when i run the query from BEX ? I could debug through RSRT, but as I mentioned before, the variants get successfully populated in the tables when maintained through RSRT.
I saw a trace list option in the BEX settings, but that doenst tell me anything.
Thanks for your help in advance!
Prakash

Variable Selections in BEx Query Variants

I am trying to save a variant for a BEx query that uses a floating date range. I want the date range to move with the calendar. I r/3 this is done with the variable selection. In BW 3.5, I don't see how this is possible. I only see options for TVARVC which are user exit selections. Can someone point me in the right direction.
Regards,
Kevin B

Hi Kevin
Your requirment is that date range should move with calendar (ex. In first week , the date range should be from 1 to 7 of the current month & in second week the date range should be from 1 to 15 of current month) ...if it is like this then you can go ahead with - create a variable and do the coding with sydatum (system date ) and embed the required logic. But if your requirement is completely random then you can not use this.
Hope this helps
Regards
Pradip
(Rewarding points is the way of saying thanks on SDN !!)

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

Execute generated query report in RSRT

Hello experts,
I tried to execute the generated report for a query in transaction RSRT and it failed ("query not found on server" was the error). Now my question is more general - what is this report for? Is it just a "background program" for a query and should not/cannot be executed in SE38? Can you execute your generated query programs in SE38?
Thanks in advance!
Greetings,
Daniel

Hi Daniel,
Basically the queries are Subroutine Pools and you can call this in ABAP.
Please see the following links.
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/41c97a30-0901-0010-61a5-d7abc01410ee
Re: Execute generated query report in RSRT
I hope this will help you to get more clarity as well to me to get more points!!!!
Regs
Gopi.

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.

Save query

hi all,
when i am trying to save query i got this errors"
1.The query could not be saved due to a problem in transport.
2.BEx transport request '' is not available or not suitable.
3.Choose an existing request .
please any one help me this is urgent.
Thanks
sada.k

hi Sada,
you need to create BEx request first.
rsa1->transport connection->click button 'bex with truck' and assign package.
there is oss note 194051 for details.
hope this helps.
oss note 194051
Symptom
An error occurs when you save a query:
Error when saving
"The query could not be saved due to a problem in transport".
Other terms
Business Explorer, query, transport, save, R9 124
Reason and Prerequisites
There are 4 possible reasons for this problem:
1. The BEx default transport request or the development class-dependent transport request is not maintained or released in the Administrator Workbench.
2. The system is set to "cannot be changed". Refer to Note 337950 (as of 2.0b SP 11), which describes how query objects can be edited in systems that cannot be changed.
3. You are not authorized to write to Workbench requests.
4. The BEx default transport request or the development-class-dependent transport request in the Administrator Workbench has another target system than the query (the transport destination of the query is determined via the transport layer of the query's development class (as of 3.0: of the package)).
The error only occurs for query objects which already have a development class, that means, which were already placed on a transport request.
Solution
Solution for Cause 1:
a) Start the Administrator Workbench
b) Choose 'Goto' to change to Transport connection
c) Choose "Request BEx" or "BEx development classes" in the toolbar.
d) Create a (new) request.
e) All changes in the BEx are now written to this request.The end user is no longer confused by 'Transport' dialog boxes.
Solution for Cause 2:
See Note 337950
Solution for Cause 3:
Authorize user to write to Workbench requests.
Solution for Cause 4:
Create a request for each target system. Assign the request suiting the target system of the transport layer of the development class (of the package) to each development class (as of 3.0: to each package) used for BEX objects.
If this does not change the situation, further information is useful for error analysis.
Go to Transaktion SE16, Table RSZCOMPDIR. In field COMPID, select the technical name of your query. Read the COMPUID of your query.
Go to SE37, function module rso_elem_get_related. Parameter I_IOBJNM is set to the COMPUID, and parameter I_OBJVERS (object version) is set to A. Only the export parameters E_T_OBJ_EXISTENTIAL and E_T_OBJ_DEPENDENT are of interest.
These entries are then entered in function module rs_tr_objects_check_insert in import parameter I_T_TR_OBJECT. In this parameter, fill field PGMID fixed with 'R3TR' and field OBJECT fixed with 'ELEM'. Field OBJ_NAME is filled with the contents of field OBJNM from export parameters E_T_OBJ_EXISTENTIAL and E_T_OBJ_DEPENDENT. The other fields are not relevant.
The export parameters of this function module are required for further error determination. Add this information to your OSS message. The table of messages E_T_MSG is important in particular.

Cannot save query variant in RSRT

Similar Messages

Maybe you are looking for