BEx variables ignored in MDX query

I am having some issues with Crystal Reports running off a Bex query. In the Bex query I have a variable defined on characteristic posting date. However, even though I select a specific posting date when prompted, records from all posting dates are returned. So I copied the MDX statement and ran it in MDXTEST only to get the same result.
MDX:
SELECT NON EMPTY EXCEPT([OPSTNG_DATE].MEMBERS, {[OPSTNG_DATE].[All]}) ON ROWS FROM [EFIGL_M01/QEFIGL_M01_4250] SAP VARIABLES [!V000001] INCLUDING "08/01/2010" : "08/01/2010"
Anyone ran into a similar problem before? The MDX statement does indicate that I only picked one posting date for SAP VARIABLE

Hi Ingo,
Yes this variable is built in the underlying Bex query, and running the query in web analyzer or RSRT shows the correct filtered reesult.
The variable is created under the Posting Date Characteristic under "Default Values" in the "Filter" tab. Now that you mentioned this, I tried moving the variable to "Characteristic Restrictions" from "Default Values" and I am able to get the correct result! What I don't get now is why the original configuration worked for Bex but not for MDX, but worked for both once moved to "Characteristic Restrictions"?
Thanks!

Similar Messages

  • Declare variables in an MDX query

    Is it possible to declare variables in an MDX query like transact sql? something like this:
    DECLARE @date1 date
    DECLARE @month1 int
    set @date1 = '12-12-2012'
    set @month1=DATEPART(m, @date1)-1
    select @date1 as dt1, @mesreferencia as mt1

    Hi ,
      In MDX , you will not be able to put variables in MDX. But Query scoped calculated measures can be used for such cases. The equivalent MDX for the above is
    WITH MEMBER [MEASURES].Dt
    As
    CDATE('12-12-2012')
    MEMBER MEASURES.DTPart
    As
    DATEPART("M", MEASURES.Dt)-1
    SELECT {MEASURES.Dt,MEASURES.DTPart} ON 0
    FROM [Adventure Works]
    Best Regards Sorna

  • Cascading LOV in BEx Query OLAP Universe + BEx variable

    Hi gurus,
    we have an universe where a Cascading LOV has been defined based on a BO Hierarchy ( based on a BW hierarchy), the OLAP universe is based on a BEx query.
    Now, when the users create a WebI report selecting a value from the value list, the Cascading LOV appears and the user selects the value, descending by the nodes.
    We are analyzing the universe performance and we are testing to add some time BEx variables in the query ( in the current version no variables are used).
    Everything works properly but when we try to select a value from the Cascading LOV and try to select a lower level the webI returns a mdx error indicanting that the time variable is not informed. (WIS 10901: A database error ocurred; MDX query can not be executed: specify a value for the variable Z... )
    We thought that the mdx for the LOV get values from the MD table because in the infoobject definition, it has the Business Explorer Settings:
       Query Def. Filter Value Selection = Value in Master Data Table
       Query Execution Filter Val. Selectn  = Value in Master Data Table
    The Query Execution Filter Val. Selectn  can be defined at the infoprovider also (with the provider specific Properties of the infoobject) and also at the query, whe have not modify none of them.
    My first question is which settings has efect at OLAP Universes, the infoobject settings; the infocube settings or the query settings ?
    Are the Cascading LOV integrated with BEx Query OLAP Universe?
    Is it an application error?
    Many Thanks in advanced.
    Best Regards,
    Nuria

    Hi Ingo,
    many thanks for your quick answer.
    That was one of the possibilities we have analized but the problem is that the user has to inform the hierarchy level for all the reports, that kind of variables is translated in the universe as a prompt
    Now we have only one universe and some business analists users create reports themselves for the business area based on that universe.
    The users create WebI filters without prompts,just filtering the hierarchy node. If we add the BEx variable then the user sould inform the prompt for all the reports based on that universe.
    We want to avoid that prompt, we have several hierarchies in the query for different infoobjects.
    Thanks again.
    Best Regards,
    Nuria

  • How to ignore a variable defined in a query when the query gets executed

    Hi SAP guru, I am creating a query, which has a user input variable, say A, and a replacement path variable, say B, Bu2019s value is determined by A and the whole purpose of A is letting user entering an initial value and A must be ignored when the query gets executed. How can I achieve this in query designer?
    Thanks

    Hi, thanks for the reply. Actually this is not my problem. My problem is the query should be filtered by  a variable, say B, but B is not allowed to be entered directly by user (i.e. B could be a replacement path variable or user exit type). So B has to be derived from another user input variable, say A. However if I defined A in the query, A is by default used as one of the filters, which is not desirable because A is a subset of B in my case and should be ignored.
    Is there options (settings) that allow the query ignore a specified variable (A) ? If not is there other ways to get around this?
    Thanks
    MichScott

  • Running MDX Query in BEX

    I've a question regarding MDX Query .
    1.Can we run MDX Query in BEx.
    2.If yes , then can you please tell me how and where can we run MDX Query in BEx.
    Regards,
    -Neha

    Hello,
    BEx does not support MDX. You can use MDXTEST transaction to generate the MDX select statements against queries or infocubes but it cannot be used with BEx.
    Thanks,
    Michael

  • SAP BW BEx query - WEBi MDX query

    Hi Experts, have we had some discussion on this?
    Does MDX query send by WEBi report to BW use the same program to extract data from BW database?
    One of the option for WEBi report source of data is to build Universe on top of BEx query. Could you share how this process actually happen.
    I think
    - WEBi query will pass parameters that is relevant for BEx query filter of the universe
    - the BEx query will then extract the data (following normal process if we run BEx query independently)
    - if WEBi has further filtering, it will then get the BEx result above and filter it further ..??
    So, how is MDX query come into the picture?
    Or is it:
    - WEBi query and the BEx query will determine what MDX query will be generated, and this MDX query will then fetch the data.
    But why BEx query extract data faster then MDX query?
    Sorry, i am new to this. hope someone could share some light here. In the meantime i continue to real those documentation and try to get some more ideas of what is actually happening.
    Thanks.

    Hi Thanks a lot for pointing this out.
    Did i understand it correctly that BEx query is using a different set of program (platform) to retrieve data compare to MDX query, and not MDX uses those program that is used by BEx to retrieve data from BW database and have extra steps on top of that?
    Can anyone share what is actually happen WEBi MDX query is executed (how the database is hit with SQL, and what are the tools to evaluate the efficiency of the WEBi (or the used BEx). As for BEx we have RSRT to analyze it right.
    And even to test the MDX query using MDXTEST and try to get the data from WEBi report, i found WEBi report still take considerably a lot longer. Why is this so? just because BO is a different system then BW?
    And as it's shared the BO 4.0 is using the same platform as BEx to retrieve data from BW database, does this mean we don't need to care about MDX usage in BW anymore as far as BO data extraction concern?
    Thank you very much.

  • VAL_FIELD selection to determine RSDRI or MDX query: performance tuning

    according to on of the HTG I am working on performance tuning. one of the tip is to try to query base members by using BAS(xxx) in the expension pane of BPC report.
    I did so and found an interesting issue in one of the COPA report.
    with income statement, when I choose one node gross_profit, saying BAS(GROSS_PROFIT), it generates RSDRI query as I can see in UJSTAT. when I choose its parent, BAS(DIRECT_INCOME), it generates MDX query!
    I checked DIRECT_INCOME has three members, GROSS_PROFIT, SGA, REV_OTHER. , none of them has any formulars.
    in stead of calling BAS(DIRECT_INCOME), I called BAS(GROSS_PROFIT),BAS(SGA),BAS(REV_OTHER), I got RSDRI query again.
    so in smmary,
    BAS(PARENT) =>MDX query.
    BAS(CHILD1)=>RSDRI query.
    BAS(CHILD2)=>RSDRI query.
    BAS(CHILD3)=>RSDRI query.
    BAS(CHILD1),BAS(CHILD2),BAS(CHILD3)=>RSDRI query
    I know VAL_FIELD is SAP reserved name for BPC dimensions.  my question is why BAS(PARENT) =>MDX query.?
    interestingly I can repeat this behavior in my system. my intention is to always get RSDRI query,
    George

    Ok - it turns out that Crystal Reports disregards BEx Query variables when put in the Default Values section of the filter selection. 
    I had mine there and even though CR prompted me for the variables AND the SQL statement it generated had an INCLUDE statement with hose variables I could see by my result set that it still returned everything in the cube as if there was no restriction on Plant for instance.
    I should have paid more attention to the Info message I got in the BEx Query Designed.  It specifically states that the "Variable located in Default Values will be ignored in the MDX Access".
    After moving the variables to the Characteristic Restrictions my report worked as expected.  The slow response time is still an issue but at least it's not compounded by trying to retrieve all records in the cube while I'm expecting less than 2k.
    Hope this helps someone else

  • Crystal Report not Adopting all possible Dropdown Values from BEx Variable

    Hi all,
    I am having an issue in a Crystal report where the drop down parameter that is sourced from a BEx query variable does not include all the possible values in the cube (or in master data). After learning my lesson the first time of not changing the name of the variable or changing it to dynamic (this causes it to break), I had the understanding that the value list may not be complete when running the report in the Crystal client or in the viewer, however, I thought it should be correct when published to the BOE and run in infoview. I am getting the same incomplete list in infoview. I published the report into infoview using the Crystal 2008 desktop client, not the /CRYSTAL/RPTADMIN transaction.
    I know there are a couple ways of sourcing a Crystal report from a BW query - using MDX vs. not, etc. I created this report using the SAP menu > "Create new report from a query". I don't believe Crystal will easily let you use that menu option to create a report off two BW queries joined together (which is what I am doing), so I built it off one originally (using the SAP menu), then added the other later on. I have the checkbox for "Use MDX driver with support for Multiple structures" checked. In database expert, my "Selected Tables" both are of database type "SAP BW Query".
    Do I have the right understanding of how the value list should work when sourced from a BEx variable? If so, can anyone offer any suggestions for getting the value list populated correctly?
    Here's some info:
    Crystal version: CR2008, version 12.2.4.507
    BOE version 3.1
    SAP BW 7.01 EhP 6
    Thanks,
    Chad

    Hi,
    - in the Crystal Reports designer the list of values is not online and there is a maximum number of values - configured by a registry setting:
    (windows 7)
    HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Business Objects\Suite 12.0\SAP\BWQueryReportWrapper
    Key: MaxPickListSize
    and correct you can not change the name of the variable or set it to dynamic as the definition is based on the BEx query.
    I know there are a couple ways of sourcing a Crystal report from a BW query - using MDX vs. not, etc. I created this report using the SAP menu > "Create new report from a query". I don't believe Crystal will easily let you use that menu option to create a report off two BW queries joined together (which is what I am doing), so I built it off one originally (using the SAP menu), then added the other later on. I have the checkbox for "Use MDX driver with support for Multiple structures" checked. In database expert, my "Selected Tables" both are of database type "SAP BW Query".
    The checkbox on the Multi Structure is not for the option to combine 2 Bex queries - it is for Bex queries with 2 structures and the BW query driver has been deprecated already and you have to use the MDX Driver.
    Do I have the right understanding of how the value list should work when sourced from a BEx variable? If so, can anyone offer any suggestions for getting the value list populated correctly?
    in Crystal Reports Designer the list is static and when you publish the report using the BW Publishing to your SAP BusinessObjects Enterprise system the list becomes dynamic in InfoView.
    regards
    Ingo Hilgefort

  • Formatting MDX report,Error=One or more axes in MDX query have been skipped

    Hi All
    Need to show the measures on row-ways instead of Column-ways in MDX report. Able to generate report with measures Column-ways.
    Getting error when tried the following:
    #) when used "{} On Rows" instead of "{} On COlumns".
    ERROR - 1200545 - One or more axes in MDX query have been skipped.
    ERROR - 1241101 - Unexpected Essbase error 1200545.
    If anyone faced something like this before, please share some work-around.
    Thanks & Regards
    sharma

    Hi,
    Take a look at this SAP Note:  1580524 - Xcelsius Dashboard does not display variable popup
    Also go through the below discussion, it may help you.
    Bex Variable PopUp does not come up launching Xcelsius dashboard
    One or more mandatory variables of query XXX no... | SCN
    Bex Variable PopUp does not come up launching Xcelsius dashboard
    BICS - Passing Mandatory Filter Variable value to a BEx Query
    Passing parameters between XCelsius dashboards using BI direct connection
    Hope this helps brother.
    Regards,
    Suman T

  • Range selection in MDX query

    Hello to everyone,
    Is there anyway to develop a MDX query, using a sap variable, and use the range interval at this query.
    For example, at BEX I can define a variable to accept year/month from xxx to yyy.
    How can I do this in MDX? I'm only able to execute only with a single value (like in this simple example). Is the other way possible?
    SELECT {[Measures].[3ZFR2WD9UJZZZBUBZNRGDIQ9X]}
    ON COLUMNS,
    NON EMPTY
    {[0SALESEMPLY].LEVELS(01).MEMBERS}
    ON ROWS
    FROM [YSD_M05/YSD_M05_Q0040]
    SAP VARIABLES
    [YKC_MESN] INCLUDING [0CALMONTH].[200503]
    Thanks and best regards from a cloudy day at Lisbon
    Bruno

    Hello,
    Ok... I just figured it out. We must use the ":" operator.
    The query must be like this:
    SELECT {[Measures].[3ZFR2WD9UJZZZBUBZNRGDIQ9X]}
    ON COLUMNS,
    NON EMPTY
    {[0SALESEMPLY].LEVELS(01).MEMBERS}
    ON ROWS
    FROM [YSD_M05/YSD_M05_Q0040]
    SAP VARIABLES
    [YKC_MESN] INCLUDING [0CALMONTH].[200503]:[0CALMONTH].[200504]
    Best Regards
    Bruno

  • MDX query failed to execute (QAAWS)

    Hi All,
    When i execute dashboard (SAP BI -> Universe -> QAAWS -> Xcelsius) i get error:
    A database error occured. The database error text is: The MDX query SELECT  { [4KQ4D7SK7G9NG7WS5G6JD60I7].[4KQ4D808QEVCYUG8BA8VN7Z7Z] }  ON COLUMNS , NON EMPTY [4KQ4D6IH1ONECGO36FSHOU87J].MEMBERS ON ROWS FROM [ZFIGL_C04/ZFIGL_C04_Q0024] SAP VARIABLES [!V000002] INCLUDING 1000/20002M03 [0P_FPER] INCLUDING 004.2010 failed to execute with the error . (WIS 10901)
    Connection test of MDX Parser in sm59 is OK.
    When i execute same MDX statement in MDXTEST i get error:
    Invalid MDX command with /
    Message no. BRAINOLAPAPI100
    some time before i was getting the error:
    Invalid MDX command with Cin
    Message no. BRAINOLAPAPI100
    I have two variables in BEx query, Fiscal year period & Profit center(Hierarchy node variable). if i don't pass value for profit center i get the data in dashboard.
    When i execute QAAWS in edit mode with both parameters i get the data in preview of QAAWS.
    I was unable to find the clear solution when i searched in SDN. please help.
    Product versions:
    Xcelsius 2008 Enterprise edition
    BOE 3.0
    BI 7.0
    Regards,
    Pruthvi R
    Edited by: Pruthvi R on Feb 6, 2011 7:50 PM

    No, not in CR 2008.
    When i execute the QAAWS in preview i get the full hierarchy for selection. i have assigned L01 L02 L03 (levels of hierarchy) to 3 combo boxes  by using Filtered Rows option in combox boxes.
    i an not entering any thing manullay in dashboard. based on combo selection i get 1 node of hierarchy which i am passing to another qaaws along with fiscal period for data.
    the problem is the data feching query is not able to understand passing value of hierarchy node.
    i copied the mdx and executed in MDXTEST with different input. I get the characteristics list in first column and measure in second column will be always balnk for:
    "20002M03" or "1000/20002M03" or "[0profit_ctr].[20002M03]" (within square brackets)
    Regards,
    Pruthvi R
    Edited by: Pruthvi R on Feb 7, 2011 3:55 PM

  • How to union results from 3 different dimensions in where clause with or - Mdx query

    Hi 
    I have a MDX Query and i need to pass the variable values to it by dynamically.
    Each time it will get any one attribute from three dimensions.
    Select 
    {} ON Columns,
    {} ON Rows 
    From
    Cube
    Where
    [Dimension1].[Attribut].&[Value]
    or
    [Dimension2].[Attribut2].&[Value]
    or
    [Dimension3].[Attribut3].&[Value]
    So It is working for two different values by using union and cross join.
    Can you please provide the solution ..
    Thanks in advance

    Hi Philip
    Thanks for replying me.
    I tried on that way, In my mdx query i am using one slice attribute (i.e [Customer].[Gender].allmembers) in rows so getting error "The  Hierarchy already appears in Axis1".
    SELECT
    {[Measures].[Internet Sales Amount] } ON 0,
    NON EMPTY
    {[Customer].[Gender].allmembers } ON 1 -- Used
    FROM
    [Adventure Works]
    WHERE
    [Customer].[Gender].&[M]
    ,[Product].[Size Range].[(All)]
    ,[Customer].[Country].[All Customers]
    [Customer].[Gender].[All Customers]
    ,[Product].[Size Range].&[XL]
    ,[Customer].[Country].[All Customers]
    [Customer].[Gender].[All Customers]
    ,[Product].[Size Range].[(All)]
    ,[Customer].[Country].&[Australia]
    Can you provide alternate ways to get resolved.
    Thanks in advance

  • Bw publish and connections not based on the sap bw mdx query driver

    Dear experts,
    we are currently facing a problem with transporting reports that are based on multiple database connections and joined using the cross database join feature of crystal reports. One connection is based on the SAP BW MDX driver, the other is based on a SAP functionmodule.
    Now when transporting the reports with STMS and publishing them via /crystal/rptadmin and bwpublish only the bex mdx query connection gets updated. The other connection is still pointing to the original location.
    e.g.
    transporting
    DEV -> PROD
    function module still pointing on dev server.
    As we need to use the sap default transport system in order to get all features (no SP4 yet) and we can not change the reports manually in the PROD system before publishnig and don't want to mix in the LCM we have no idea how get a work around for this problem.
    Changing the database connection via CMC on the PROD system has no effect either.
    Please help.
    Thank you very much!
    Thorsten

    Hello Thorsten,
    What you observe is "By Design" of the product. The dynamic update is supported only for reports using the BW MDX driver (or historically for those using the deprecated BW query driver). Other SAP drivers such as the OpenSQL driver which you use to connect to the function module do not leverage the same features when using the SAP Transport process.
    You may report directly against your target system when connecting to Function Modules.
    thanks,
    Akin

  • When using TODATE function MDX query is not correctly generated

    Essbase 9.3.1.2 and OBIEE 10.1.3.4.1.
    When using TODATE function MDX query is not correctly generated.
    This leads to unexpected values not only on cumulative columns in report (generated with TODATE), but also other columns (calculated with AGO function or directly read from cube) have incorrect values.
    The problem occurs when you filter on a column that is not in the select list. If you filter on just one level of dimension, results are fine. You can filter on multiple dimensions as long as you filter on just one level of each dimension.
    If you filter on two or more levels of one dimension, than results are not correct. In some cases results for TODATE column are all zeros, in some cases it is a random value returned by Essbase (same random value for all rows of that column), and in some cases BI Server returns an error:
    State: HY000. Code: 10058. [NQODBC] [SQL_STATE: HY000] [nQSError: 10058] A general error has occurred. Essbase Error: Network error [10054]: Cannot Send Data (HY000).
    Here is generated MDX code:
    With
    set [Grupe proizvoda2] as '{[Grupe proizvoda].[N4]}'
    set [Grupe proizvoda4] as 'Generate([Grupe proizvoda2], Descendants([Grupe proizvoda].currentmember, [Grupe proizvoda].Generations(4), leaves))'
    set [Segmentacija2] as '{[Segmentacija].[RETAIL]}'
    set [Segmentacija4] as 'Filter(Generate({[Segmentacija2]}, Descendants([Segmentacija].currentmember, [Segmentacija].Generations(4),SELF), ALL), ([Segmentacija].CurrentMember IS [Segmentacija].[AFFLUENT]))'
    set [Vrijeme3] as '{[Vrijeme].[MJESEC_4_2009]}'
    member [Segmentacija].[SegmentacijaCustomGroup]as 'Sum([Segmentacija4])', SOLVE_ORDER = AGGREGATION_SOLVEORDER
    member [Accounts].[MS1] as '(ParallelPeriod([Vrijeme].[Gen3,Vrijeme],2,[Vrijeme].currentmember), [Accounts].[Trosak kapitala])'
    member [Accounts].[MS2] as '(ParallelPeriod([Vrijeme].[Gen3,Vrijeme],1,[Vrijeme].currentmember), [Accounts].[Trosak kapitala])'
    member [Accounts].[MS3] as 'AGGREGATE({PeriodsToDate([Vrijeme].[Gen2,Vrijeme],[Vrijeme].currentmember)}, [Accounts].[Trosak kapitala])'
    select
    { [Accounts].[Trosak kapitala],
    [Accounts].[MS1],
    [Accounts].[MS2],
    [Accounts].[MS3]
    } on columns,
    NON EMPTY {crossjoin ({[Grupe proizvoda4]},{[Vrijeme3]})} properties ANCESTOR_NAMES, GEN_NUMBER on rows
    from [NISE.NISE]
    where ([Segmentacija].[SegmentacijaCustomGroup])
    If you remove part with TODATE function, the results are fine. If you leave TODATE function, OBIEE returns an error mentioned above. If you manually modify variable SOLVE_ORDER and set value to, for example, 100 instead of AGGREGATION_SOLVEORDER, results are OK.
    In all cases when this variable was modified in generated MDX, and query manually executed on Essabse, results were OK. This variable seems to be the possible problem.

    Hi,
    Version is
    BANNER
    Oracle Database 10g Enterprise Edition Release 10.2.0.5.0 - 64bi
    PL/SQL Release 10.2.0.5.0 - Production
    CORE    10.2.0.5.0      Production
    TNS for 64-bit Windows: Version 10.2.0.5.0 - Production
    NLSRTL Version 10.2.0.5.0 - Production
    Sorry, in my last post i forgot to mention that i already created a function based index but still it is not using because, there is a UNIQUE constraint on that column.
    Thanks

  • SSRS report with tabular model – MDX query how to get the sum and count of measure and dimension respectively.

    Hello everyone,
    I am using the following MDX query on one of my SSRS report.
    SELECT NON EMPTY { [Measures].[Days Outstanding], [Measures].[Amt] } ON COLUMNS,
    NON EMPTY { ([Customer].[Customer].[Customer Key].ALLMEMBERS) }
    HAVING [Measures].[ Days Outstanding] > 60
    DIMENSION PROPERTIES MEMBER_CAPTION, MEMBER_UNIQUE_NAME ON ROWS
    FROM ( SELECT ( STRTOSET(@Location, CONSTRAINED)) ON COLUMNS
    FROM ( SELECT ( {[Date].[Fiscal Period].&[2014-06]}) ON COLUMNS
    FROM [Model]))
    Over here, the data is being filtered always for current month and for a location that is being selected by user from a report selection parameter.
    I would like to get the count of total no. of customers and sum of the amount measure.
    When I am using them in calculated members it gives incorrect values. It considers all records (ignores the sub-select statements) instead of only the records of current month and selected location.
    I also tried with EXISTING keyword in calculated members but there is not difference in output. Finally, I manage the same at SSRS level.
    Can anybody please advise what are the ways to get the required sum of [Measures].[Amt] and count of [Customer].[Customer].[Customer Key].ALLMEMBERS dimension?
    Also, does it make any difference if I manage it as SSRS level and not at MDX query level?
    Any help would be much appreciated.
    Thanks, Ankit Shah
    Inkey Solutions, India.
    Microsoft Certified Business Management Solutions Professionals
    http://www.inkeysolutions.com/MicrosoftDynamicsCRM.html

    Can anybody please advise what are the ways to get the required sum of [Measures].[Amt] and count of [Customer].[Customer].[Customer Key].ALLMEMBERS dimension?
    Also, does it make any difference if I manage it as SSRS level and not at MDX query level?
    Hi Ankit,
    We can use SUM function and COUNT function to sum of [Measures].[Amt] and count of [Customer].[Customer].[Customer Key].ALLMEMBERS dimension. Here is a sample query for you reference.
    WITH MEMBER [measures].[SumValue] AS
    SUM([Customer].[Customer].ALLMEMBERS,[Measures].[Internet Sales Amount])
    MEMBER [measures].[CountValue] AS
    COUNT([Customer].[Customer].ALLMEMBERS)
    MEMBER [Measures].[DimensionName] AS [Customer].NAME
    SELECT {[Measures].[DimensionName],[measures].[SumValue],[measures].[CountValue]} ON 0
    FROM [Adventure Works]
    Besides, you ask that does it make any difference if I manage it as SSRS level and not at MDX query level. I don't thinks it will make much difference. The total time to generate a reporting server report (RDL) can be divided into 3 elements:Time to retrieve
    the data (TimeDataRetrieval);Time to process the report (TimeProcessing);Time to render the report (TimeRendering). If you manage it on MDX query level, then the TimeDataRetrieval might a little longer. If you manage it on report level, then the TimeProcessing
    or TimeRendering time might a little longer. You can test it on you report with following query: 
    SELECT Itempath, TimeStart,TimeDataRetrieval + TimeProcessing + TimeRendering as [total time],
    TimeDataRetrieval, TimeProcessing, TimeRendering, ByteCount, [RowCount],Source
    FROM ExecutionLog3
    WHERE itempath like '%reportname'
    Regards,
    Charlie Liao
    TechNet Community Support

Maybe you are looking for