Increase Query Designer Performance?

Hi together,
Is it possible to increase the performance of the Query Designer? I have a query which is based on a MultiProvider with several InfoCubes. If i work some minutes with the Query Designer, it becomes slower and slower. Then it takes from one up to ten seconds to see the digit in my formula, which i pressed on the keyboard just before. This is very awful! At least the half of the time i work with the Query Designer i have to wait, that this tool stops calculating something or displaying the hourglass. Very inefficient.
Thanks for hints in advance!

>
Ricardo Rosa wrote:
> Hi Timo,
>
> Usually this kind of issue should be solved with frontend patch upgrade, have you tried to reproduce this with latest FEP?
>
> Other suggestion which should help is to search for RSZ tables inconsistencies with report ANALYZE_RSZ_TABLES, this can search for inconsistencies which can decrease the performance in the query definition and also suggest a fix for that.
>
> Kind regards,
>
> Ricardo
Hi Ricardo,
Yes, i've already upgraded to latest FEP version.
But thank you for this report. It looks very helpful!
>
Arun Varadarajan wrote:
> Shikha,
> The question was regarding Query designer performance and not query performance...
>
> We faced similar issue earlier - even opening of Query designer took a huge amount of time but then on upgrading upgrading my system to 1 GB ram most of the performance issue went away... check the RAM usage in the task manager and CPU utilization. This might make query designer faster.
Hi Arun,
At this point there is no more hope for me, as my system has already 2 GB RAM and a dual core cpu with 2.2 GHz.

Similar Messages

Report burst:To increase query performance in xcelsius

Is there anyway to increase query performance in xcelsius by using report bursting

Fremlin,
Report bursting is only for distributing your reports to your end users.
You can improve performance only by following the [Best practices|https://www.sdn.sap.com/irj/boc/index?rid=/library/uuid/a084a11c-6564-2b10-79ac-cc1eb3f017ac] in xcelsius.
-Anil

Can we perform restriction on attribute in query designer?

Hi
can we perform restriction on attribute in query designer? My scenario is to restrict on an attribute..Could any one help me out i this issue?
Regards,
Suman

Hi,
Restriction can be done only for navigational attribute.U cannot do restriction for display attirbute.
if it is a display attribute u want to restrict -make it navigational for that infoobject.
Also the attribute must be 'checked on' as navigational in the infoprovider as well on which the query is built.
hope it helps.
Regards,
Rathy

% Calculactions in Bex Query Designer

Hi Experts,
Could you please on how can i perform the below % Calculactions in Bex Query Designer.
    Vendor No line item Not = L category =A status =RFQ :for items
Example : I have 8 items for vendorNo 200274 and only 4 as above condition and 5 items as not L(delete)
requament: % RFQ Without Response:
Percentage of Quotation response ={(No. of RFQReponses Received/ No. of RFQ items sent)*100},
                                                               ( 4/5 * 100= 80%)
Percentage RFQ without response= 100 - Percentage of Quotation response
                                                              = 100-80 = 20%
How can i perform the % Calculations in Bex Query Designer.
Vendor
Purchasing document
Indicator: Line Item
Purch. doc. category
Purch. doc. status
Item
Number of Records
category A item L
200274
V-LINE EUROPE EXPORT MARKETING
6000003778
L
A
Not assigned
10
1
20
1
30
1
6000003779
Not assigned
A
Not assigned
40
1
9000000046
Not assigned
A
RFQ
10
1
1
20
1
1
30
1
1
40
1
1
Result
8
4
thank you

Hope you have done some groundwork you have done on this requirement. Have you tried to create New Formula and put the required formula in it to calculate Percentage of Quotation response ?
Your formulas seems to be straight forward.
Keep in Filter: item Not = L category =A status =RFQ
You may start working on it and get back with if you are struck.

Where to write IF THEN ELASE statements in BEX Query Designer

Hi All,
I need to write a formula in query designer...
saying that to display the all Quantities in KGs.. Now articles are in Grams and KGs...
So here i need to perform calculation like... if article is in KGs divide by 1, else if article is in Grams divide by 1000.
where can i write this logic to perform calculation ...
Thanks in advance..
ravi.p

hi chetan,
No its not work.. why because i need to convert the unit of measure in Masterdata Attribute values... that means ) ' 0grooss_wt'. this is attribute as a keyfigure of ' 0material' .. this ' 0gross_wt' values has to convert in KGs. at Present ' 0gross_wt' values are in KG and Grams...
I can change these values in update rules by writting Routine.. But I need to convert it in KGS at BEX Query Designer Level..
I need calculate like this
quantity sold * Gross Weight.
here Gross Weight is the formula variable which replacing the values of gross weight...
i tried by creating conversion types in RSUOM t-code. but it works on keyfigures of infocube.. not on attribute values of master data...
is there any solution to solve this Problem...

How to create a formula based condition in bex query designer

hi all,
i have scenario in query designer where i need to calculate Key performance indexes based on characters and key figures iam using.for example the condition is like:
"if call received is less than call projection then give call received else null"
how and where to define the condition and i need to name the condition to display it seperatly.please help me in this issue.
regards
Vamshi D Krishna

hi you have to break down your conditions and then code for them.
for e.ge.
if actual == 0
vart = 0.
else if actual-target ==0
          vart = 0.001
       else
         vart = actual -target
       endif
endif
now we start with first condition use operators from boolean catagory
(Actual != 0)*(other amount)
this solves first if condition... if actual = 0 value actual != 0 will be zero we got our desired value.
if other case then we have give else condition.
(Actual != 0)*(((actual - target) == 0 )*0.001+((actual-target)!=0)*(actual-target))
in the second half we have coded the else part.
in the same way you can proceed for your logic

How to write a condition in BEX Query Designer

Hi
How can i write a condition in Query Designer
Scenario
An employee can purchase any no of policies in a day or month.each policy will have start date and expiry date.
My requirment
Count all the policies(valid) by employee on a ranges basis exception reporting
(0-10;10-20;20-30;30-40) and then able to drill down by policy start date and expiry date.
As per the requirment is to show policies which are not yet expired (active) i need to write a condition that will count only policies whose Expiry date is > Current calender day
As Policy Expiry Date is a char i am converting it to KF using fourmala variable so that i can write a condition on it using current cal day formula variable sap exit
But i char assigment of a condition i find 4 option
How can i achieve this
Thanks

Hi Aurun,
Thanks for the help,Really appreciated
As this is my first enhancement using ABAP & CMOD
What type of key (either Access or developer ) do i require to perform the following enhancement......so that i can raise request with basis team
I shall be great ful if u can asnwer below question
First, you need to create a variable for expiry date with processing type as customer exit, and then give the necessary info.
In details tab, unchk ready for input as we wont be taking the value from the prompt.
Now go to CMOD transaction.
Open the correcsponding project which has the exit code
(How can i identify the project which has exit code)
and go to ZXRSRU001 module inside taht.
Go to the module where u write the exit.
(How to locate the required module)
Then, under i step 1, write the code:
IF I_STEP = 1.
CASE V_NAME (What is 'V_NAME',Is it my variable technical name)
WHEN 'X' " X is the variable u created for the exit
l_s_range-low = SY-DATUM.
l_s_range-opt = 'I'.
l_s_range-sign = 'GT'.
APPEND l_s_range TO e_t_range.
END CASE.

Creating Restrictions in BEx query designer for (1-a), where a is variable.

Dear All,
>> Suppose for the variable in the BEx query designer, I've created restriction for 0FISCPER to the variable 0P_PER (as 0P_PER-1) by right clicking 0P_PER3, from that a dialog box appears. In that I've selected 0P_PER3 and then clicked on offset variable and when I set the offset variable, it works for (0P_PER-1.etc, 0P_PER+1,etc..)
But if I want to have (1-0P_PER), then plz tell me how to define this restriction?
Plz explain me the steps to perform (1-0P_PER) restriction in BEx query designer in BW1.
I'm using SAP BI 7.2 gui.
Expecting your reply soon,
with Regards,
Jerald

My requirement is that I want to have " 1-fiscal year"., But this I could not define using offset variables, since using offset we can define "fiscal year +1" or "fiscal year -1".
So there would be some other way to define "1-fiscalyear". So Please help me to define "1-fiscalyear" by giving me the steps.
Thank you,
with Regards,
Jerald

How to hide a single value node hierarchy in the query designer

Hi,
I would like to perform a calculation in the infocube. It concern a count "Nb of different customers" with the following hierarchy : Country / region / City.
This KF would be read at the same time by city, region and country, and certain customers exist in 2 different region, and I have to count them only once by country.
To do this, I added a new record (at the country level when loading infocube) to deduct a number of customers in doubloons.
This line added contain only a country code and the number of cutomers in doubloons (- 23 when I have 23 cutomers in doublons) with revrese sign.
Now, I would like to use this value (-23) to have a right Nb of different customers by country, without showing the not assigned line in the report hierarchy.
How can I hide, in the query designer or the WAD, a single value node from hierarchy (NOT assigned) but take in account the value (-23) at the country level ?
Is there another solution (more simple) to perform this in the infocube ?
For information,
1) The infocube is loaded once per month, and the KF (Nb of different customers" is also performed by month.
2) I can't perform this in the report (performance problem with calculated KF).
thx.

Hi,
the short answer is "you can't", the longer is: The ADF Faces tree component is stamped for better performance. This stamping means that nodes are not rendered as JSF objects but copies of an existing component (just with a changed value). For this reason the nodes don't issue their own query for data and thus cannot be refreshed individually
Frank

Grouping Free Characteristics in Query Designer?

Hello,
I have a couple reports that per busniess have many free characteristics. So many that that they do not fit on one page and you must continue scrolling the page down to view all. This makes the report look sloppy but the business owner wants all of these free characteristics. I'm looking for a way to clean up the list of free characteristics without removing any selections. Can they be grouped up or consolidated through Query Designer or WAD?
Thank You,
Alex

Hi Alex,
Actually use of free characteristic will not slow down the report performance rather free characteristics are used to enable the user for dynamic drilldown and to improve the query performance for initial output display.
What you can suggest your users is to keep only required free characteristics and then remove the rest of the characteristics and from grouping perspective all the free characteristics in query designer output are shown alphabetically so you can not manipulate the group in designer.
Regards,
Durgesh.

What are the best design requisites for a Query design?

Hi Guru's
Could you please let me know,which item will execute first when you run a query,I mean Calculated keyfigure,restricted keyfigure or formula e,t,c...How does it effects the Query performance?What are the design requisites to optimise better query performance?
Thanks in advance,
rgds,
Srini.

Hi Srinivas....
The design of queries can have a significant impact on the performance.
Sometimes long running queries are the result of poor design, not just the amount
of data. There are a number of design techniques that developers can use to
provide optimal query performance.
For example, in most cases characteristics should be placed in the rows and key
figures in the columns. A characteristic should only be used in the columns in
certain circumstances (like time). Characteristics having potentially many values
(such as 0MATERIAL) must not be added to the columns without a filter or
variables. Alternatively, it can be integrated into the query as a free characteristic
enabling it to be used in navigation.
If a relatively detailed time characteristic, such as calendar day (0CALDAY) is
added to the rows, the more aggregated time characteristics (such as calendar
month (0CALMONTH)) and calendar year (0CALYEAR) should also be included
in the free characteristics of the query. For most reports, a current period of time
(current month, previous or current calendar year) is useful. For this reason, the
use of variables is particularly relevant for time characteristics.
To improve query performance
1) Variables and drop down lists can improve query performance by making the
data request more specific. This is very important for queries against Data Store
Objects and InfoSets, which are not aggregated like InfoCubes.
2) When using restricted key figures, filters or selections, try to avoid the Exclusion
option if possible. Only characteristics in the inclusion can use database indexes.
Characteristics in the exclusion cannot use indexes.
3) When a query is run against a MultiProvider, all of InfoProviders in that
MultiProvider are read. The selection of the InfoProviders in a MultiProvider
query can be controlled by restricting the virtual characteristic 0INFOPROVIDER
to only read the InfoProviders that are needed. In this way, there will be no
unnecessary database reads.
4) Defining calculated key figures at the InfoProvider level instead
of the query level will improve query runtime performance, but may add
time for data loads.
5) Cell calculation by means of the cell editor generates separate queries at query
runtime. Be cautious with cell calculations.
6) Customer-specific code is necessary for virtual key figures and characteristics.
Check Code in Customer Exits.
7)Using graphics in queries, such as charts, can have a performance impact.
Hope this helps.........
Regards,
Debjani.........

Control display level for "display as hierarchy" in BI 7 Query Designer ?

Hi
I'm using BI 7.0 query designer and I can see there's an additional difference between BI 3.5 and BI 7.0 in rows/columns behavior, in the "display as hierarchy" functionality.
In BW 3.5 one could specify till what level the expand needed to be by default. So it could be 0 for totally collapsed. This is seems not possible anymore in BI 7.0 query designs anymore. Only on natural/technical hierarchies (cost center etc ...) this option is still there.
Is there a way (javascript or other) to have the hierarchies created by "display as hierarchy" also fully collapsed by default ?
Thanks.
Geert

HI, thanks for the reply.
But this is not about the standard InfoObject 'hierarchy" tab, with all it's options on default expand levels etc.
This is about a "pseudo structure" hierarchy which is defined at designtime (in Query Designer) and generated/shown at runtime (so bad for performance, I know). It's based on the real transaction data, not on a pre-created hierarchy as in normal hierarchies. It creates a tree view of otherwise unrelated InfoObjects, displays it in an collapsible/expandable tree shape.
it's a bit hidden in version 7 Query Designer, compared to version 3.5. In 3.5 one had a larger set of options, including the -now lacking- default expand-to level. But in Version 7, most options are dropped. Probably due to the move from the ABAP to the java backend, lots of other stuff got culled in that move as well.
For more info, look at the posts from Larry in this thread : [Display as Hierarchy|Display as Hierarchy]
I know it's an option not used a lot but can be handy in certain cases.
I really would like some help in getting a default query result with the "display as Hierarchy" collapsed.
Thanks,
Geert

Unit Conversion in Query Designer

Hi All,
In one of my report, i have to show the gross weight in column against material which i am reading from material master.
Now the weight is stored in two different unit's KG & G.
But i have to show the weight finally in KG.
Does any body has any idea of performing unit conversion at Query level i.e. in Query Designer.
Thanks.

Rakesh the same i am doing, that is reading the weight value from material master through formula variable using replacement path.
Now when i create a key figure like this, there is a tab of 'Conversion' in that there is mentioned the 'Unit conversion'
In there, there are 2 options
1. Conversion type - this is a drop down but with no vlaue
2. Target Unit - Where i selected KG.
But output remains the same, i.e. in KG.
M I missing something ?

Query Designer 3.5 does not respond when trying to restrict a charact

Hello experts!
I'm trying to restrict characteristic 0BPARTNER in query designer 3.5 but when I try to open the restrict context menu it tries to bring all the business partners to display them from master data and it freezes. We have over 2 millon business partner data in our MD.
I've already tried performing statistics over the MD tables but it's still not working. Any suggestions that might help me are kindly wanted.
Thanks,
Regards,
Salvador.

Hello Salvador,
I don't know if this is what you really need, but you can check and get a better performance in BEx queries by using t-code RSRT in section Properties there you can set ...
Read Mode
Req. Status
Cache Mode
Optimization Mode
Statistic Det.
among others. I hope this helps.
Regards!
Bernardo

Query Designer Issues Post System Copy

Hi All -
We have just performed a system copy from our production to our QA systems. Now, when we trying to view a report from Query Designer in our QA environment, we are being prompted for a username and password - which is trying to log in to our production environment! (I know this because I locked myself out of production trying to log in via our QA Query Designer). We've done all the BDLS runs, updated the RSLOGSYSDEST table poer OSS note 524554, and also updated the tRFC port in WE20. What do we need to do to be able to run a query out of the BW QA system?
Thanks for the assistance.
Abby

Hi Abby,
Once you execute the query from designer you will get one URL generated in the explorer address bar here you will have to change the name of your production app server with quality app server then report will be executed on quality server.
But this is temporary solution, you will have to check with your basis team regarding this and they will have to change some setting in system table and next time onward the system will pick proper URL.
Regards,
Durgesh.

Increase Query Designer Performance?

Similar Messages

Maybe you are looking for