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

Similar Messages

  • 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).

  • 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.

  • Balance for open periods in a time series enabled cube

    Hi,
    We have a request to calculate balance for open periods in a time series enabled cube, I don’t there is any inbuilt function for this.
    Any ideas on how to calculate this without adding new members/formulae in the time dimension. Currently we compute this in the report
    EX:
    BOY(May) = Jun+Jul + … + Dec
    Thanks,

    You will have to add a member somewhere. Suppose you add it in scenario, then you could use sumrange for the current member range offsetting the current monthe by 1 and use null for the end month wich gives you the last month in the time dim.

  • HT5312 Every time I click send e-mail for instructions on resetting my security questions, I don't get them? I just want to play minecraft. I already put $15 in my balance and I can't even spend it. Thank you for taking the time to read this.

    Why is it, every time I click send e-mail for instructions on resetting my security questions, I don't get them? I just want to play minecraft. I already put $15 in my balance and I can't even spend it. Thank you for taking the time to read this.

    Either they're being sent to a different email address, or got caught in a spam filter, or something's wrong at Apple's end. If you can't find the email, you need to ask Apple to reset your security questions, which can be done by phoning AppleCare and asking for the Account Security team, or clicking here and picking a method, or if your country isn't listed in either article, filling out and submitting this form.
    (105723)

  • Bad performance due to the use of AGO and TO_DATE time series functions

    Hi all,
    I'm building an OBI EE Project on top of a 1TB DW, and i'm facing major performance problems due to the use of the AGO and TO_DATE time series functions in some of the Metrics included on the reports. I discovered that when a report with one of those metrics is submited to the DB, the resulting query/explain plan is just awful!... Apparently OBI EE is asking the DB to send everything it needs to do the calculations itself. The CPU cost goes to the roof!
    I've tried new indexes, updated statistics, MV's, but the result remains the same, i.e., if you happen to use AGO or TO_DATE in the report you'll get lousy query time...
    Please advise, if you have come across the same problem.
    Thanks in advance.

    Nico,
    Combining the solution to view the data in dense form (http://gerardnico.com/wiki/dat/obiee/bi_server/design/obiee_densification_design_preservation_dimension), and the use of the lag function (http://gerardnico.com/wiki/dat/obiee/presentation_service/obiee_period_to_period_lag_lead_function) appears to be the best solution for us.
    Thanks very much.

  • SQL for Time Series Functions AGO and YTD

    When we use a time series function such as AGO or TODATE, OBIEE creates 2 physical queries. One query reads the calendar table. The other query reads the fact table without any date filter in the WHERE clause. Then the results of the 2 queries are stitched together. The query on the fact table returns a lot of rows because there is no filter on date.
    Is there a way to force OBIEE to put a filter on the date when performing the physical query on the fact table when using AGO or TODATE?
    Thanks,
    Travis
    v11.1.1.6

    We do have a date filter on the analysis. We need the analysis to show sales for a certain month and sales for that month a year ago, so we use the AGO function. However, it is really slow because it does a physical query on the sales table without filtering on date and then filters the results of that physical query by the dates from the physical query on the calendar table.

  • Time series and Order series questions

    Hi Guys - Need some help in understanding/Visualizing some basic APO concepts. I do not want to move further without understanding these concepts completely. I did read sap help and couple of apo books but none gave me a complete understanding of this very basic concept.
    1. Data is stored in livecache in 3 different ways. time series, order series and atp time series. for now I am concentrating on just time series and order series. Can some one help me understand with an example how data is stored in time series and how it is stored in order series? I read that data which is not order related is called time series data and which is order related is called order series data.
    My query is even in DP time series data, data is stored with respect to product and location that is transferred to snp. In SNP too data is processed with respect to product and location. so what is the difference in time series data and order series data?
    2. what are time series key figures and what are order series key figures? I read safety stock for example is a time series keyfigure. why is it not a order series key figure? what makes a keyfigure time series or order series? can some one xplain this in detail with an example or numbers?
    3. there is a stock category group in snp tab of location master LOC3. Stock category should be product related right? how is this related to location and what does this field mean in location master
    Thanks a lot for your help in advance. Please let me know if I am not clear in any of the questions.

    Hi,
    Time series:  Data is stored in buckets with no reference to orders.( If you place the mouse on time series data and right click for
                         display details , you will not find any information.
                          Suitable for tactical planing and aggregated planning. Usually in demand planning.
    Pre requisite: 1. You need to create time series objects for the planning area.
                           2. When creating planning area you should not make any entries for the Key figure in the field Info Cube, category
                               and  category group.
                           3. When creating planning area any entry you made in the field Key figure semantics with prefixed with TS.
                               (Optional entry)
    Order series: Data is stored in buckets with reference to orders.( If you place the cursor on the order series data and right click
                          the mouse for display details , you will find information of order details.)
                         Useful for operative planning.
                         *You will have real time integration with R3.
    Pre requisite: 1. You need to create time series objects for the planning area.( though you are creating Order series)
                          2.When creating a planning area specify a category or category group or enter a key figure semantics with prefix
                            LC.
                         3. When creating planning area you should not make an entry for the key figure in the field Info cube.
    Thanks,
    nandha

  • SAP HANA One and Predictive Analysis Desktop - Time Series Algorithms

    I have been working on a Proof-of-Concept project linking the SAP Predictive Analysis Desktop application to the SAP HANA One environment.
    I have modeled that data using SAP HANA Studio -- created Analytic views, Hierarchies, etc. -- following the HANA Academy videos.  This has worked very well in order to perform the historical analysis and reporting through the Desktop Application. 
    However, I cannot get the Predictive Analysis algorithms -- specifically the Time Series algorithms -- to work appropriately using the Desktop tool. It always errors out and points to the IndexTrace for more information, but it is difficult to pinpoint the exact cause of the issue.  The HANA Academy only has videos on Time Series Algorithms using SQL statements which will not work for my user community since they will have to constantly tweak the data and algorithm configuration. 
    In my experience so far with Predictive Analysis desktop and the Predictive Algorithms, there is a drastic difference between working with Local .CSV / Excel files and connecting to a HANA instance.  The configuration options for using the Time Series Algorithms are different depending upon the data source, which seems to be causing the issue.  For instance, when working with a local file, the Triple Exponential Smoothing configuration allows for the specification of which Date field to use for the calculation.  Once the data source is switched to HANA, it no longer allows for the Date field to be specified.  Using the exact same data set, the Algorithm using the local file works but the HANA one fails. 
    From my research thus far, everyone seems to be using PA for local files or running the Predictive Algorithms directly in HANA using SQL.  I can not find much of anything useful related to combing PA Desktop to HANA. 
    Does anyone have any experience utilizing the Time Series Algorithms in PA Desktop with a HANA instance?   Is there any documentation of how to structure the data in HANA so that it can be properly utilized in PA desktop? 
    HANA Info:
    HANA One Version: Rev 52.1
    HANA Version: 1.00.66.382664
    Predictive Analysis Desktop Info:
    Version: 1.0.11
    Build: 708
    Thanks in advance --
    Brian

    Hi,
    If you use CSV or XLS data source you will be using Native Algorithm or R
    Algorithm in SAP Predictive Analysis.
    When you connect HANA, SAP Predictive Analysis uses PAL Algorithm which runs
    on HANA server.
    Coming to your question regarding difference,
    In SAP PA Native Algorithm, we could provide the Data variable, Algorithm
    picks the seasonal information from the Data column. Both R and SAP HANA PAL
    does not support Date Column. We need configure seasonal information in
    Algorithm properties.
    R Properties
    1) Period : you need to mention the periodicity of the Data
    Monthly : (12)
    Quarter : (4)
    Custom : you can use it for week or Daily or hourly.
    2) Start Year: need to mention Start year.
    Start year is not used by algorithm for calculating Time series, but it helps
    PA to generate Visualization ( Time series chart) by simulating year and
    periodicity information.
    3) Starting Period:
    if your data is Quarterly and you have data recordings from Q2, mention 2 in
    start period.
    Example.
    If the data periodicity is Monthy and my data starts from Feb 1979, we need to provide following information,
    Period: 12
    Start year: 1979
    start Period: 2
    PAL Properties. : Same as properties defined in R.
    Thanks
    Ashok
    [email protected]

  • TB Average and Dynamic Time series

    Hi,
    In our outline, we have Time dimension tagged ad Dynamic Time series.
    There few measures which have member formula attached, they are dynamic calc, two pass.
    Among these measures which are tagged as TB average and skip missing, we get zero for QTD,YTD on retrieval.
    But for other measures which do not have TB average and skip missing, we get values for QTD and YTD.
    Please help !!

    Just an update on the above query,
    I was able to see numbers when I used the attribute dimension.
    For eg.-
    we have 5 standard dimension and 2 attribute dimensions which are attached to LOB standard dimension.
    In excel addin when i retrieve withour taking the attribute dimension, i dont see numbers and when i put the attribute dimension as header, i see numbers.
    Why this attribute dimension is making diffrence

  • Max Number of Time Series and Other Columns?

    What are the ceilings on the number of Time Series and Other Columns that BOP can handle?
    I can not find this very basic info anywhere but I have a client that I think has hit it.

    @ cfr:
    I googled. But I opened this thread the July 25th and I'd forgot about that link and the fact that my problem could be Firefox fault. Silly me. -_-
    I'm trying to surf w/ Chromium right now (I don't like very much Opera and other browsers based on Webkit don't read much stuff on the web) to check if issue returns. If so I'll try to check log.
    Edit:
    I found that I don't even like Chromium as well. So I think I'll use W3m and Elinks for "normal browsing" and FireFox just when I need to write a mail with my damned Hotmail account.
    Edit (2012-10-08):
    the issue still presist, even without Firefox.
    Last edited by rix (2012-10-08 20:16:25)

  • Add time series and CIF behaviour

    All,
    I need to delete time series and add time series again. What is the impact in a production environment? Do I need to stop CIF etc?
    Cheers

    There is no need to stop the CIF queues when you are deleting and recreating the time series. The data can flow in from R/3 and it will not have any impact on the time series deletion / recreation process.  But in general it is advisable to perform this task  after normal business hours when no business users are logged in and when no other jobs are running.
    This is necessary because if anything were to go wrong you can be sure the problem is because of the time series deletion and recreation.
    Also MAKE SURE YOU BACKUP ALL TIME SERIES DATA  to backup cube before deleting the time series , otherwise you will lose all your data as soon as you delete the time series .  In general time series is deleted only when it is absolutely necessary since it is considered a very critical process .
    Thanks
    Saradha

  • Smartview and Dynamic Time Series

    All,
    I just heard this:
    Dynamic Time Series is used in other applications on reports and works as expected in Financial Reporting. However, it does not work correctly with SmartView.
    Is this true? You can't pull DTS reports in SmartView? Version 11.1.2.1

    Have a read of http://docs.oracle.com/cd/E17236_01/epm.1112/sv_user/sel_dts.htm
    or are you saying FR reports in Smart View does not work
    Cheers
    John
    http://john-goodwin.blogspot.com/

  • Creating Dynamic Time Series in Hyperion Profitability and  Cost Management

    I am creating Dimensions in Dimension Library for Hyperion Profitability and Cost Management. Please let me know if we can set Dynamic Time Series for HPCM.
    I can see DTS Manager option for Period Dimension in Hyperion Planning but this option is not available for Period Dimension in HPCM Application.
    Is there any other way to drill down upto weeks level or day level data in Time Series.

    I am also facing the same issue. Does we have any option to create Dynamic time series in HPCM. Please let me know.

  • Time series objects and order objects on what condtion we need to use

    Dear Experts ,
    I have question regarding Time series objects and order objects
    from my understanding
    TIme series objects the data is stored in time buckets without
    reference to orders.
    Order objects the data is stored as orders. Key figure data is
    then saved as orders if semantic 000 is entered in the detail view of the key
    figures in the planning area.
    my question is when to use the option 1 and when should not use
    same for option 2
    Many thanks
    Regards
    Raj

    Hi,
    This depends on the requirement you have also the application you are using.Like DP key figures are generally time series since in DP you do not need order numbers for example for history sales the requirement is the quantity period wise but not the order numbers.
    Again in SNP the distribution and planned quantities are required order wisecoz you need the order numbers you execute the same in ECC system or for Pegging purposes.
    Now the safety stock requirement can not be at order series since this is with relevent to some periods.
    So overall i can say this depends on the requirement of the kay figure.
    Hope this can help.
    regards,
    kaushik

Maybe you are looking for

  • Installing Oracle 8i Personal Edition in Win98

    Hi, Would like to find out if there is any issue in installing Oracle 8i Personnal Edition in windows ME. I have this error message when I tried to install the programme. "Jrew has caused an error in JAVAI.DLL. Jrew will now close." Anyone can help ?

  • Latest Update downloaded - Now Blackberry Playbook doesn't work!

    I just downloaded an update for my Playbook and it said it needed to restart to finish upgrade and now my screen is black and I can't restart my Playbook - Can someone out there help me? I am pretty new to all this computer playbook items Thanks, Ter

  • Oracle query sort by case sensitive

    Hi All, I am using oracle database 11g. My use case is I do have a table with following values Table name -test product id     productsortdescription H58098        ACETAMIDOHYDROXYPHENYLTHIAZOLE 043994         Alloy .MM.INTHICK My query is select * f

  • Unwanted apps in purchase history

    How can I remove unwanted apps from my ipad purchase history. I have loads of apps i've tried and rejected but they still show up in purchase history.

  • Dump import Error

    Hi All, I'm getting the below error while importing a dump file. ORA-39126: Worker unexpected fatal error in KUPW$WORKER.PUT_DDLS [TABLE:"T24"."STUBFILES"] ORA-06502: PL/SQL: numeric or value error LPX-00007: unexpected end-of-file encountered ORA-06