Using PeriodToDate MDX function in an ASO cube (Dynamic Time Series)

Hyperion Essbase 7.1.2
Since ASO doesn't support Dynamic Time Series (DTS), I am trying to use the "PeriodToDate" MDX function to get MTD and YTD totals. Below is my Time dimension:
Time (Time - Stored)
...I---> 2007
......l---> Q1-2007
.........l---> Jan-2007
............l---> 2007-01-01
............l---> 2007-01-02
............l---> 2007-01-03
.........l---> Feb-2007
.........l---> Mar-2007
......l---> Q2-2007
......l---> Q3-2007
......l---> Q4-2007
Syntax:
PeriodsToDate ( [layer [, member ]] )
I tried many different ways to get the right syntax but it didn't work when I set the formula on member "2007" for YTD totals or on months to get MTD. Any help would be appreciated.
Message was edited by:
user597443

ASO does not have Dynamic Time Series at all (unless something just recently changed)
Period to date functionality has to be managed via MDX formulas and/or alternate roll ups in your time dimension.
Time Balancing does have to be a stored hierarchy, which is what you generally want anyway. The issue you have with Time balancing is that some times if you have an alternate roll up in your time dimension, it can cause problems with Time balancing.
If you want to use Time balancing, I would sugest a single stored time heriarchy and use an anakytic view dimension for the period to date functionality.
You can see a post I have on my blog that talks about this: garycris.blogspot.com
One other thing to mention. If you wan to use built in time balance functionality, you must tag a dimension as Account Type and it will have to be a dynamic dimension.

Similar Messages

  • [Essbase] - using TopCount MDX  function

    Hi,
    I would like to use the TopCount MDX function in an ASO cube.
    I did manage to write the MDX query but did not find how to "convert" it as a MDX formula on the "MEASURE" dimension (well I am guessing).
    I thank you for your help!
    Thomas
    MDX query :
    IND_HITS is from the MEASURE dimension
    A2008 is from the YEAR dimension
    M1013210 is from the MESSAGE dimension
    SELECT
    [MOIS].Generations(1).Members
    ON COLUMNS,
    TopCount([USERS].Children,10, [IND_HITS] )
    ON ROWS
    FROM Cube_Log.Cube_Log
    WHERE ([A2008], [M1013210], [PARAMETRES],[HEURES],[TYPE])

    Hello
    I have an aggregate measure in a cube ASO, aggregating to a minimum, I tried to use the MIN function but have not worked out as expected in the first Essbase is the sum of the data and then calculates the minimum.
    This is the function used:
    IIF ( NOT IsLevel ( [Hospital].CurrentMember, 0 ),
    MIN( Descendants(CurrentMember ( [Hospital] ),[L.Unknown].Level),[PrzListinoMINInput]),
    IIF ( NOT IsLevel ( [Marketing].CurrentMember, 0 ),
    MIN( Descendants(CurrentMember ( [Marketing]),[A.Unknown].Level),[PrzListinoMINInput]),
    IIF ( NOT IsLevel ( [Listini].CurrentMember, 0 ),
    MIN( Descendants(CurrentMember ( [Listini]),[C.Unknown].Level),[PrzListinoMINInput]),
    IIF ( NOT IsLevel ( [Bravo].CurrentMember, 0 ),
    MIN( Descendants(CurrentMember ( [Bravo]),[D.Unknown].Level),[PrzListinoMINInput]),
    IIF ( NOT IsLevel ( [Product Cluster].CurrentMember, 0 ),
    MIN( Descendants(CurrentMember ( [Product Cluster]),[E.Unknown].Level),[PrzListinoMINInput]),
    IIF ( NOT IsLevel ( [Area].CurrentMember, 0 ),
    MIN( Descendants(CurrentMember ( [Area]),[F.Unknown].Level),[PrzListinoMINInput]),
    IIF ( NOT IsLevel ( [Area2].CurrentMember, 0 ),
    MIN( Descendants(CurrentMember ( [Area2]),[G.Unknown].Level),[PrzListinoMINInput]),
    IIF ( NOT IsLevel ( [Area3].CurrentMember, 0 ),
    MIN( Descendants(CurrentMember ( [Area3]),[H.Unknown].Level),[PrzListinoMINInput]),
    IIF ( NOT IsLevel ( [Area4].CurrentMember, 0 ),
    MIN( Descendants(CurrentMember ( [Area4]),[I.Unknown].Level),[PrzListinoMINInput]),
    IIF ( NOT IsLevel ( [Customer].CurrentMember, 0 ),
    MIN( Descendants(CurrentMember ( [Customer]),[N.Unknown].Level),[PrzListinoMINInput]),
    0))))))))))
    how to proceed in these cases?
    Thank you

  • How to use dynamic time series in formula

    I have Time dimension with active Dynamic Time Series for Y-T-D.
    I'd like to use it in member formula - e.g. IF (@ISMBR("Y-T-D(Aug)")) - but this doesn't work as I get error message Unknown variable or member name.
    Any idea how to work with dynamic time series members in formula?
    Still using Essbase 6.5 X-(.

    As Glenn mentioned, I also don't believe you can reference a DTS member in a formula, you would have to calc the YTD. Take a look at the @PTD function to calc Period to date numbers, I believe this function was available in v6.
    Having said that, we're assuming you want to calc a ptd number, but your example was based on an IF @ISMBR(). So the question becomes what are you trying to do? Given what I assume your time dim looks like, what would be the difference between @ISMBR("Y-T-D(Aug)") and @ISMBR("Aug")

  • How to use Dynamic Time Series YTD on a calc script / member formula?

    Hi,
    I activated Dynamic Time Series on Essbase and would like to use the YTD function of a measure for a certain month.
    I tried to use
    MeasureName->YTD(Dec)
    MeasureName->Y-T-D(Dec)
    But couldn't use it to syntax problems. How can I call this function instead of using @Accum or @SumRange?
    Thank you
    Edited by: Icebergue on 10/Ago/2011 11:07

    I could be wrong, but I don't think you can use DTS members in calc scripts or member formulas. As you probably know, they can be used in Financial Reports, SmartView and Excel Add-in.
    You can create an alternate hierarchy in your Time dimension though:
    Jan (YTD): Jan ->Jan is being a shared member
    Feb (YTD): Feb+Jan (YTD) ->Both Feb and Jan (YTD) are being a shared members
    Dec (YTD): Dec+Nov (YTD) ->Both Dec and Nov (YTD) are being a shared members
    Cheers,
    Mehmet

  • Issues using two-pass with dynamic time series?

    Is there any issues with using Dynamic time series [Q-T-D(May)] on a dynamic calc account which is defined as two-pass and has time balance property associated with it.
    The account is defined as "Dynamic Calc"+"Two-pass"+"TB First" and it works fine, but does not fetch result when used with DTS as Q-T-D(May). But, the same seems to work fine without the two-pass calc option on.
    Thanks in advance,
    cheers,
    revati

    Hi Revati,
    Yes u r right, I also tried with same scenario as you mentioned.
    Y-T-D values are not fetching with Twopass,but in that case Twopass is not required because of that member already having "Dynamic calc".
    so you can proceed with Dynamiccalc without twopass.
                   Actual                    
                   Sales     COGS     Margin     Margin %     Margin1 %
    New York     Cola     Jan     6000     5500     500     8.333333333     8.333333333
              Feb     5500     5000     500     9.090909091     9.090909091
              Mar     7000     6500     500     7.142857143     7.142857143
              Qtr1     18500     17000     1500     8.108108108     8.108108108
    With twopass          Q-T-D(Mar)     18500     17000     1500     8.108108108     #missing
    with out twopass          Q-T-D(Mar)     18500     17000     1500     8.108108108     7.142857143
    Praveenkumar.I
    TSPL
    mobile:09975686985

  • MDX query performance on ASO cube with dynamic members

    We have an ASO cube and we are using MDX queries to extract data from that cube. We are doing some performance testing on the MDX data extract.
    Recently we made around 15-20 account dimension members dynamic in the ASO cube, and it is taking around 1 and a half hour for the query to run on an empty cube. Earlier the query was running in 1 minute on the empty cube when there were no dynamic members in the cube.
    Am not clear why it takes so much time to extract data from MDX on an empty cube when there is nothing to extract. The performance has also degraded while extracting data on the cube with data in it.
    Does dynamic members in the outline affect the MDX performance? Is there a way to exclude dynamic members from the MDX extract?
    I appreciate any insights on this issue.

    I guess it depends on what the formulas of those members in the dynamic hierarchy are doing.
    As an extreme example, I can write a member formula to count every unique member combination in the cube and assign it to multiple members, regardless if I have any data in the database or not, that function is going to resolve itself when you query it and it is going to take a lot of time. You are probably somewhere in between there and a simple function that doesn't require any over head. So without seeing the MDX it is hard to say what about it might be causing an issue.
    As far as excluding members there are various function in MDX to narrow down the set you are querying
    Filter(), Contains(), Except(), Is(), Subset(), UDA(), etc.
    Keep in mind you did not make members dynamic, you made a hierarchy dynamic, that is not the same thing and it does impact the way Essbase internally optimizes the database based on Stored vs dynamic hierarchies. So that alone can have an impact as well.

  • Using a user-defined element in ASO cube.

    I have an ASO cube to which I'm adding a new hierarchy/dim containing a single user-defined element as a member. This dim is set to dynamic at dimension level, since I'm going to add additional members with formulas.
    My issue is that as soon as I add this new hierarchy to my cube, all my fact values double! What could cause this and how should I fix this? The user-defined element in this new dim is not connect to the rest of my data in any way, i.e. it is not in any table of my minischema. So why should it have any impact on my data values? Should I be adding a filter of some kind on this user-defined element?
    Fyi- I'm using Essbase Studio (EPM 11.1.2) for cube building and data loading.
    Appreciate any help.
    thanks,
    Axe

    A colleague suggested a reason that SDO_GEOMETRY works is that it is granted to PUBLIC with GRANT OPTION. PUBLIC is not a proper role, somewhere between a user and a role and the issue of having to receive permissions on the type explicitly do not apply.
    If I GRANT EXECUTE ON XTYPE TO PUBLIC WITH GRANT OPTION; it works!
    Thanks for the replies.
    C

  • Using "left" mdx function in script logic

    Hello experts,
    I'm fetching a selection from a package prompt into a logic.
    The dimension name is ENTITYCC, so the variable name is %ENTITYCC_SET%.
    In this prompt user can select members from a hierarchy like that :
    CH20
    --- CH201000
    --- CH202000
    --- CH203000
    FR20
    --- FR201000
    --- FR202000
    --- FR203000
    and so on
    In my logic I need to have the parent node selected, but in case the user select a leave, I need to keep only first four caracters of his selection (to simulate the fact he select the parent)
    left(%ENTITYCC_SET%,4)
    What would be the instruction to get in another variable only the first four caracters of %ENTITYCC_SET% ?
    Thanks for your ideas.
    G.

    Solved by myself, sorry for the useless post.
    (my solution is :
    *SELECT(%ENTITY%,"left([ID],4)","ENTITYCC","[ID] = '%ENTITYCC_SET%'")
    and remember to use lgf file and not lgx when there is mdx in the logic

  • How to properly use H-T-D Dynamic Time Series Function

    Hello all.
    Our Period Dimension goes like default
    Period
    -Year Total
    --Qtr1
    ---Jan
    etc..
    Now when I set up HTD (lack of any explanation on the Documentation)
    I put the generation to Level 2. The function pretty much does what YTD does, sums up the total for hte year given the current month. What we want to try and accomplish is get values summed from the very first data saved to the current datal current. Now this can't happen since years are in a differnet dimension. So my main question is. Is this possible to do? and what is the main function of H-T-D? Thank you.

    HTD or History to date is meant for when you have a single time dimension with multiple years in it. If your outline liiked something like
    Years
    2008
    2008-q1
    2008-jan
    2008-feb
    2008-mar
    2008-Q4
    2008-Dec
    2009
    etc
    You could use set up qtd, ytd and htd and get totald for each.
    In your case if Years is in a separate dimension from periods, you would have to roll your own as formulas on created members. in either the period or year dimension (I'll guess the years dimension) where you add from my example 2008->period +( range of jan to the current member) look at sumrange and currmbrrange functions

  • Dynamic Time Series in ASO

    We have time hiearchy like the below is ASO, we are using essbase 11.1.2.2
    Time
    2011
    First Half 2011
    Q1 2011
    Jan 2011
    Week 01/01/2011
    2011-01-01
    2011-01-02
    Week 01/03/2011
    2011-01-03
    2011-01-04
    2011-01-05
         2011-01-06
    2011-01-07
    2011-01-08
    2011-01-09
    We have this hiearchy continuing for 5 years same like the above. How can i acheive QTD, MTD, WTD and DTD in ASO. Kindly help me out.
    Regards,
    AS

    I'd also look at Dan Pressman's 2010 Kscope presentation. I think even Gary agrees that using hierarchies rather than 'straight' MDX is usually preferable (based on his remarks in 'Developing Essbase Applications', which is another excellent source for the details of both Crisci and Pressman solutions).

  • ASO Time and Periods combined - Dynamic Time Series?

    I am looking to do period-to-date calculations in ASO using the method outlined by Gary Crisci but I have Time and Periods combined into one heirarchy.
    I have seen suggestions that this can be done, but I cannot find any example code for the calculations.
    My MDX skills are not up to the challange yet so I was hoping someone is doing this and could shed some light.
    I am exploring the options of hard-coded alternate heirarchies, but data is stored at the day level and users want
    the same capability they have in BSO.
    Thanks,
    Kenneth

    You can create the calculated members within the existing time dimension, but it get ugly and probably won't perform great. For starters you will have to create a calculated member with a formula for every stored time member you have. Not too bad for 12 months, but if you ahve years and months in same dim or daily model, its not realistic. That is the beauty of View dimension, a single formula goes a long way.
    Other option is to not have alternate roll-ups in time dim - perhaps you can use Attribute dims to simulate the alternate groupings you need.

  • Building Drill through reports from aso cube using odi in webanalysis11.1.3

    I need some urgent help as i have a important requirement for an essbase aso cube .I was trying to establish a database connection to build a drill through report in webanalysis from oracle datawarehouse.the integration tool which we are using to get data from oracle datawarehouse to hyperion is odi.My question are
    1) Can drill through reports be built using odi like eis from an aso cube?if yes whats the procedure?
    2) is there any alternate ways to bring transaction level or relational data for reporting in webanalysis?
    regards,
    praveen.
    Edited by: user13070887 on Oct 11, 2010 3:48 PM

    Hi Glenn,
    We tried optimizing the drill through SQL query but actually when we run the directly in TOAD it takes *23 secs* but when we do drill through on the same intersection
    it took more than 25 mins. Following is our query structure :
    (SELECT *
    FROM "Table A" cp_594
    INNER JOIN "Table B" cp_595 ON (cp_594.key = cp_595.key)
    WHERE (Upper(cp_595.*"Dim1"*) in (select Upper(CHILD) from (SELECT * FROM DIM_TABLE_1 where CUBE = 'ALL') WHERE CONNECT_BY_ISLEAF = 1 START WITH PARENT = $$Dim1$$ CONNECT BY PRIOR CHILD = PARENT UNION ALL select Upper(CHILD) from DIM_TABLE_1 where CUBE = 'ALL' AND REPLACE('GL_'||CHILD, 'GL_IC_', 'IC_') = $$Dim1$$))
    And ----same for 5 more dimensions
    Can you suggest some improvement ? Please advice.
    Thanks

  • ASO Cube with BSO Partition as a Target

    Hi,
    Can someone please explain me the following because after reading different blogs as well as some other Essbase documents I am not able to understand,
    What is the actual use of having a BSO Transparent partition (target) of an ASO cube (source)?
    How exactly does the Write-Back functionality works if I have a BSO Transparent partition (target) of an ASO cube (source)?
    And lastly, in what business scenario one would implement a BSO Transparent partition (target) of an ASO cube (source)?
    Your help is much appreciated.
    thanks,
    fikes

    I have a situation where I have a BSO (target) on top of an ASO (source).  This was to try and resolve the dynamic time series (where time and periods are in different dimensions).  The DTS works almost great in the BSO partition.
    The other problem (or why we wanted to go to ASO) was that BSO cubes do not handle attributes across partitions (we have quarterly data in transparent partitions) to the target cube. -- but we do have dynamic time series.
    What I'm facing now it that the attributes work in the BSO (target) except when using a dynamic time series.
    The attributes are defined in both the BSO and ASO cubes.
    Any suggestions on how to handle attributes AND dynamic time series ?

  • MDX Function Descendants

    Hey,
    I'm trying to use a mdx function on the business model using Evaluate_AGGR.
    Any idea why this is not working?
    EVALUATE_AGGR('Descendants( \[%1], 1, AFTER)', "ES_FIN_BGATE_BIRE"."BGATE".."Pnl"."Gen6,SITES" )
    I've got the following error:
    Syntax error in input MDX query on line 2 at token 'member' (HY000)
    Generate code:
    member \[Accounts].\[MS1] as 'Descendants( \[\[SITES].Generations(6)], 1, AFTER)', SOLVE_ORDER = 101
    select
    { \[Accounts].\[MS1]
    } on columns
    from \[BLUEGATE.Pnl]
    Thanks!

    The "Descendants" function needs a dimension member specification. You can't simply put a dimension level (as OBIEE uses for referencing hierarchy generations of an outline).
    This will work:EVALUATE('Intersect(Descendants([Deltas],1,SELF_AND_BEFORE),%1.dimension.members)', Scenario."Gen3,Scenario")This will work as long as you don't use any other columns (speaking OBIEE terms) from the specified dimension (in this case Scenario).EVALUATE('Intersect(Descendants(%1.dimension.CurrentMember,1,SELF_AND_BEFORE),%1.dimension.members)', Scenario."Gen3,Scenario")So as long as you manage to get a singular dimension member into the function you're ok. Think prompts / presentation variables. Lists of dimension members retrieved through dimension level specifications and filters will not work.
    Cheers,
    C.

  • Time Balance and Time series in ASO

    We are building an ASO application and we need Time balance and dynamic time series functionality.
    If I go and use the TB functionality in ASO, my Time dimension has to be stored and I cannot put mdx formulas on my members (YTD,QTD,MTD)
    I see various threads here and the recommendation is to have a new dimension to view the time series members (gary's blog...tnx for him)
    However we cannot afford to have a separate dimension. The time series should be under Time.
    How can we go with this?
    Please help me with your suggestions/ideas. Thanks for your time.
    TIA
    - Sai

    Any ideas guys?
    John, can you please shed some light on this.
    TIA

Maybe you are looking for