Custom Period Dimension

Hello!
I have a question.
There is a great need for such hierarchy of "Period" dimension:
Year - quarter - month - week - day.
I know that when creating an Planning application I must choose Time Base Period "Custom" and Periods Per Year = "365".
But how then create the rest levels of this hierarchy? (week, month, quarter)
Big thx.

Have a read of the following post - Re: Custom Period problem
It is based on weeks but the logic is the same.
Cheers
John
http://john-goodwin.blogspot.com/

Similar Messages

  • Deleting custom Period dimension members

    Hi,
    We are in Planning 11.1.2.1. and we created custom period dimension members (while creating application). Now we would like to delete one of those members (whcih is at level0). Obviously we don't see an option of delete in planning web interface. One option is to recreate the application but is there any way we can delete this member in oracle database. If yes, it would be great if you can provide us the table details.
    Thanks,
    Siva

    As John suggested it is not advisible, however you can delete in Essbase using Planning:
    1. Edit custom dimsion
    2. un-select all plan type
    3. cube referesh
    Hope this will help.

  • Customize period dimension in Planning

    Hi John,
    Can we customise period dimension in classic planning application as below
    YearTotal
    Q1
    APR
    MAY
    JUN
    Q4
    JAN
    FEB
    MAR
    ADJ1
    ADJ2
    YEARTOTAL= Q1+Q2+Q3+Q4+ADJ1+ADJ2
    The source ERP system has 2 more periods apart from the 12 months ADJ1 and ADJ2. We also should have a drill back facility for this

    If you are creating a new application you could create it with 14 custom time periods, then once created add the summary time period.
    Q1,Apr,May,Jun
    Q2,Jul,Aug,Sep
    Q3,Oct,Nov,Dec
    Q4,Jan,Feb,Mar
    Adj,Adj1,Adj2
    which should all roll up to Year Total
    If you have already created the application then you could create a custom hieararchy as a child of the period
    Cheers
    John
    http://john-goodwin.blogspot.com/

  • Sparse VS Dense and neglecting Period Dimension

    Hi All,
    I am working on a classic planning application, in which i have 3 custom dimensions apart from six standard dimension. As the application grows and we start developing business rule we feel the need for optimization of our application hence along with increasing Cache Size, Block Size etc. we also make changes in JVM registry and lastly we also convert our Custom dimension to Dense from Sparse. As we are always using these dimension at either row/columns. Now i have to different questions:
    1) there are three custom attributes associated with one of my Custom dimension with 150descendants, so if i change it to Dense then i loss those three custom attributes. So is there any way to convert this from sparse to dense while having the attributes with it. Note: I am using this dimension on Row and i only want to convert it to dense in order to enhance performance. The motivation behind this change is that i piratically experiment that the business rules that take more then 20mins to executes just execute in less than a minute when i convert the other 2 custom dimensions from sparse to dense.
    2) I am not using Period Dimension in my application, because my need are fulfiled by year dimension only, so is there any way to delete it or neglect it while processing business rules?

    Hello,
    Your question gets into some advanced design topics fairly quickly and you may want to engage an experienced consultant to help you.
    It sounds like your application is past the design stage and you are making what are design level changes which is a likely risk to your project delivery time frames.
    Regarding the conversion of the dimension from sparse to dense -- there is no way to tag a dense dimension as an attribute.
    Review Chapter 10 of the Database Admin Guide at http://docs.oracle.com/cd/E17236_01/epm.1112/esb_dbag/frameset.htm?dattrib.html#dattrib524566
    Pay special attention to the "Understanding the Rules for Base and Attribute Dimensions and Members".
    In addition to loosing the attribute dimension please be aware of the implication to block size. Switching a sparse to a dense has a multiplicative effect on your block size; you should make all upper level members dynamic calc and then the number of level 0 members time your old block size will be your new block size.
    On the topic of your period dimension you may want to try renaming it and using it for one of your other dimension needs if you do not require month level data.
    On the topic of calculation speed you can usually make re-write your calculations to make them dense. In your instance it may be a good idea to make your years dense to use that to facilitate creating dense calculations.
    Good luck,
    John A. Booth
    http://www.metavero.com

  • How to customise the Period dimension in Hyperion planning

    Hi Guru's
    We are using Hyperion Planning 11.1.2.2
    We have an requirement to customise the period dimension as follows,
       -Period
         -HalfYear1
           -Q1
           -Q2
         -HalfYear2
           -Q3
           -Q4
    How to add HalfYear in the period Dimension..Please help me with this..
    Thanks

    While creating application what did you choose to have for Period Dimension , is it Periods by default or you did go for custom ?
    Also check hp_admin guide page 104
    Period Dimension Properties
    Period, Parent, Alias: Default, Alias: T1, Data Storage, Two Pass
    Calculation, Description, Formula, UDA, Smart List, Data Type,
    Operation, Type, Start Period, End Period, Aggregation (Plan1),
    Aggregation (Plan2), Aggregation (Plan3)
    Notes:
    . For Period, Parent should be specified for most update operations.
    . Type (such as Base or Rollup) cannot be changed for existing members. You can add and
    update Rollup and Alternate members. You can update BegBalance and Base time periods
    (for example, to add an alias). You cannot add or modify YearTotal time period. The DTS
    Period type is recognized, but is not supported by the Outline Load utility. If you try to load
    DTS information, the utility displays an error in the log file.
    . Start Period and End Period are valid for Rollup Period types.
    Thanks
    Amith

  • Period dimension

    I want to know why in HFM period dimension does not support days. I mean what is the point behind it, and if anyone knows a workaround to overcome this limitation.

    The reason HFM doesn't support days has to do with the RDBMS, not so much with HFM. In order to have days in the period dimension, the data tables would have 2 columns per day, plus a column for Entity, Account, ICP, Custom1..4, and Value = 366*2 + 7 = 739 columns. I forget whether it's Oracle or SQL Server that can't handle that. Even if you could, consider the memory footprint: each period consumes roughly 10 bytes of memory. In a 12 period app, that's 120 bytes. For daily, each record would use 3,660 bytes. That's a huge difference. It wouldn't take too many records befo
    For these reasons, HFM does not currently support daily applications using the period dimension. Weekly applications are rare, but they do exist. Most often they are performance problems though. What I recommend is to accomplish the daily or weekly aspect in a custom dimension, which has been discussed in this thread already.
    --Chris                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   

  • Editing the period dimension - removing quarters

    Hi,
    By default the Period dimension is composed by 19 stored members (12 months, 4 quarters, YearTotal, BegBalance and Period itself). Is it possible to delete the quarters so the block size of my application will become smaller and only have the YearTotal > Months hierarchy?
    Thank you
    Edited by: Icebergue on 4/Ago/2011 6:33
    Edited by: Icebergue on 4/Ago/2011 6:33

    you can create custom type period dim and create 12 Members under it. YOu cant modify an existing application but you can create a new application with custom period dim.
    but still you will have begBalance and YearTotal.
    BTW anytime you can change the storage property of Quarters to Dynamic Calc.
    Cheers..!!!
    Edited by: RahulS on Aug 4, 2011 7:26 PM

  • Error : Period dimension 'Period' is missing a Base Time Period member 'Jun' that has been deleted since the last deployment. Base Time Period members cannot be deleted once the dimension is deployed

    HI,
    I am using V11.1.2.2 Hyperion Planning. I am currently getting an error:
    Error : Period dimension 'Period' is missing a Base Time Period member 'Jun' that has been deleted since the last deployment. Base Time Period members cannot be deleted once the dimension is deployed
    This is what i got when i tried to add alternate hierarchy to my shared dimension. I tried to delete it and it messed up.
    NOw it wont deploy my application.
    Can any one suggest.
    Thanks in advance
    Cheers,
    XXX

    EPMA!!!!! EPMA!!!!
    I'm playing around with it to write a blog post and it is crazy. Only possible workaround (till now i'm not able to figure out a solution to it) is to copy the application and deploy it as a new one. Take copy of all objects (forms, tasklist etc). Delete the corrupted application and rename the new one to old.
    Regards
    Celvin
    http://www.orahyplabs.com

  • Logic - Average value for a particular Customer + Period

    Hello Experts,
    Please help me in the Logic to find out Average for the below scenario:
    This is the Output:
    Customer
    Period
    Payment Timeliness
    Cust-001
    01/97
    -4
    Cust-001
    01/97
    2
    Cust-001
    01/97
    3
    Cust-001
    04/97
    3
    Cust-001
    04/97
    5
    Cust-001
    06/97
    -4
    Cust-001
    07/97
    2
    Cust-001
    08/97
    3
    Cust-002
    09/97
    5
    Cust-002
    09/97
    4
    Cust-002
    10/97
    6
    Cust-002
    10/97
    -2
    Cust-002
    12/97
    -4
    Requirement is:
    Customer
    Period
    Payment Timeliness
    Cust-001
    01/97
    0.333
    Cust-001
    04/97
    4
    Cust-001
    06/97
    -4
    Cust-001
    07/97
    2
    Cust-001
    08/97
    3
    Cust-002
    09/97
    4.5
    Cust-002
    10/97
    2
    Cust-002
    12/97
    -4
    Display the Average of all the Payment Timeliness for a particular Month as shown above.
    My Code is:
    *&      Form  fetch_data
    FORM fetch_data .
      SELECT bukrs
             belnr
             gjahr
             blart
             bldat
             budat
             monat
       FROM  bkpf
       INTO  TABLE g_t_bkpf
       WHERE bukrs EQ '0470'
       AND   gjahr EQ p_year
       AND ( blart EQ 'EZ'
       OR    blart EQ 'DZ' )
       AND   monat IN s_month.
      IF sy-subrc EQ 0.
        SELECT bukrs
               belnr
               gjahr
               augdt
               buzei
               shkzg
               kunnr
               zfbdt
               zbd1t
               zbd2t
               zbd3t
               rebzg
         FROM  bseg
         INTO  TABLE g_t_bseg
         FOR ALL ENTRIES IN g_t_bkpf
         WHERE bukrs EQ g_t_bkpf-bukrs
         AND   belnr EQ g_t_bkpf-belnr
         AND   gjahr EQ g_t_bkpf-gjahr
         AND   kunnr IN s_kunnr.
        IF sy-subrc EQ 0.
        ELSE.
          WRITE:/'No Data Found'.
        ENDIF.
      ENDIF.
    ENDFORM.                    " fetch_data
    FORM display_paystats .
      DATA: l_due_date     TYPE faedt_fpos,
            l_timeliness   TYPE p,
            l_kunnr        type kunnr,
            l_counter      type i,
            l_period       type char5,
            l_tot_timeli   type p.
      IF g_t_bseg IS NOT INITIAL.
        WRITE: /10 'Customer ', 24 'Period ', 35 'Payment Timeliness'.
        WRITE: /10 sy-uline(44).
        LOOP AT g_t_bseg INTO g_wa_bseg.
          CLEAR l_due_date.
          CALL FUNCTION 'NET_DUE_DATE_GET'
            EXPORTING
              i_zfbdt       = g_wa_bseg-zfbdt
              i_zbd1t       = g_wa_bseg-zbd1t
              i_zbd2t       = g_wa_bseg-zbd2t
              i_zbd3t       = g_wa_bseg-zbd3t
              i_shkzg       = g_wa_bseg-shkzg
              i_rebzg       = g_wa_bseg-rebzg
           IMPORTING
             e_faedt       = l_due_date.
          READ TABLE g_t_bkpf INTO g_wa_bkpf WITH KEY
                                              bukrs = g_wa_bseg-bukrs
                                              belnr = g_wa_bseg-belnr
                                              gjahr = g_wa_bseg-gjahr.
          IF sy-subrc EQ 0.
            l_timeliness = g_wa_bkpf-budat - l_due_date.
          ENDIF.
          CLEAR g_wa_paystat.
          g_wa_paystat-kunnr = g_wa_bseg-kunnr.
          CONCATENATE g_wa_bseg-augdt+4(2) '/' g_wa_bseg-augdt+2(2) INTO g_wa_paystat-period.
          g_wa_paystat-timeli = l_timeliness.
          APPEND g_wa_paystat TO g_t_paystat.
          CLEAR : g_wa_bseg, g_wa_paystat.
        ENDLOOP.
        SORT g_t_paystat BY period.
        LOOP AT g_t_paystat INTO g_wa_paystat.
          WRITE:/10 g_wa_paystat-kunnr, 24 g_wa_paystat-period, 35 g_wa_paystat-timeli.
        ENDLOOP.
      ENDIF.
    ENDFORM.                    " display_paystats
    Where should I check the condition?
    I thought of assigning the Period / KUNNR in a Variable; then compare from the second record.
    But then how can I skip the check for 1st time inside a Loop?
    Since this is BSEG/BKPF entries; it is slow. So, please suggest some logic that doesn't affect the performance.
    Is it possible to write this logic within BSEG LOOP?
    Appreciate your help.
    Thank you!
    Thanks & Regards,
    Sowmya

    Found out by myself
    Closing the thread.
    SORT g_t_paystat BY kunnr period.
        LOOP AT g_t_paystat INTO g_wa_paystat.
          l_kunnr = g_wa_paystat-kunnr.
          l_period = g_wa_paystat-period.
          l_tot_timeli = g_wa_paystat-timeli.
          IF sy-tabix NE 1.
            READ TABLE g_t_paystat INTO g_wa_paystat1 WITH KEY kunnr  = l_kunnr
                                                               period = l_period.
            IF sy-subrc EQ 0.
              l_counter = l_counter + 1.
              l_tot_timeli = l_tot_timeli + 1.
            ELSE.
              g_wa_paystat-timeli = l_tot_timeli / l_counter.
              MODIFY g_t_paystat FROM g_wa_paystat TRANSPORTING timeli WHERE kunnr  = l_kunnr
                                                                       AND   period = l_period.
              CLEAR:
                l_counter,
                l_tot_timeli.
            ENDIF.
          ENDIF.
        ENDLOOP.
        DELETE ADJACENT DUPLICATES FROM g_t_paystat COMPARING kunnr period.
        LOOP AT g_t_paystat INTO g_wa_paystat.
          WRITE:/10 g_wa_paystat-kunnr, 24 g_wa_paystat-period, 35 g_wa_paystat-timeli.
        ENDLOOP.

  • Urgent Help on Custom Periods

    HI all,
    I have requirement where i have to maintain master data in BW for custom periods created in R/3 based on a special fiscal year variant.I have an idea to create a characterstic based on some date characterstic but i am not sure which datre characterstic i have to take for reference.
    I think with the help of some date functions i can get the periods into BW from transfer rules/update rules.
    Please provide the solution ASAP as i am at crucial stage.
    Thanks
    Pavan Prakhya

    Hi Pavan,
    I think you need only to upload this special fiscal variant !
    Go to source system, righ-click on it and transfer global settings...in this way you will have on fiscal variant, period and so on the same situation you already have in your R/3...(and you can continue to use the std object only by selecting the right fiscal variant)
    Hope it helps!
    Bye,
    Roberto

  • Adding Custom 1 dimension to all Balance Sheet and all PL accounts

    We added the Custom 1 dimension to all Balance Sheet and all PL accounts. Previously we only had a the Custom 1 dimension added to a few PL accounts.
    Now it takes a very long time to consolidate and we are getting warnings in the log files as follows:
    One example:
    The Node cube Scenario = Actual, 1, Year = 2009 2009, Entity = MS_UKD 589, InputValueID = USD 17, contains 110182 records
    We are consolidating a month that does not have any data in the product lines for the accounts where the product lines were added.
    Is this slowness in consolidation to be expected when doing this?
    Is there any rule or best practice to adding the custom 1 dimension to a volume of accounts?
    Thanks!

    Essentially, customs are more like sub-accounts than extra dimensions. The warning you got is not new, but this may be the first time you've noticed it. The node is a subcube that must be completely loaded to RAM on the server to do the consolidations. Take your accounts and multiply by custom 1 to see how many additional records are going into the sub cube (2797 x 232 = 648,904). You may want to have your DBA watch the server as you consolidate to see how many resources are being used and if he/she can tweak some settings to help out.
    That being said, my system has 6000 accounts, 2500 custom 1, and 1000 custom 2, but only 600 entities total in 3 hierarchies. Our full consolidation takes an hour, but doing only impacted for the current month takes about 20 minutes.

  • Value based hierarchies and Period dimension should only contain  2  monthl

    Hi,
    Can anyone tell me what is value based hierarchies. And also can anyone let me know to filter the records in AWm because in Period dimension should only contain 2 monthly values (Oct. 2008 ( 200810) and Sep. 2008 ( 200809)) it is urgent.
    Thanks
    vel

    The following definition of a value hierarchy comes from the OLAP Developers guide
    "A hierarchy defined only by the parent-child relationships among dimension members. The dimension members at a particular distance from the base level do not form a meaningful group for analysis, so the levels are not named. For example, an employee dimension might have a parent-child relation that identifies each employee's supervisor. However, levels that group together first-, second-, and third-level supervisors and so forth may not be meaningful for analysis."
    Typically this means that the source table has two columns, VALUE and PARENT, where PARENT has a (logical) foreign key relationship to VALUE. An example may be EMPLOYEE, MANAGER, where MANAGERs are also EMPLOYEEs.
    The simplest way to restrict the values loaded into the AW is to define a SQL view over the source table with an appropriate WHERE condition. You then use AWM to map the dimension to your new view. E.g.
    CREATE OR REPLACE VIEW RESTRICTED_TIME AS
    SELECT *
    FROM TIME
    WHERE MONTH IN (200810, 200809)

  • Period Dimension in XL Reporter doesn't work fine

    When I use a Period dimension in XL Reporter, that shows for example. The sales in 2008-07 like a value of a parameter or filter in a composer or designer, don't shows nothing in the result.
    If you have any idea that helps me, I will thank you a lot.
    I have these erro on a varios installations.
    Thanks for your help.
    Mariela Gómez

    Hello Wilma Wang:
    The fields that I want to show are: total line, quantity, number of document, BP Name, Product description, period.
    The problem is when you define a parameter or filter that is related with the period dimension to execute the report.  For example: you maybe select de value of 200807 to show the sales of that period.  And the result is nothing....
    Thank you for yor respond.
    Mariela Gómez

  • Error while loading period dimension in planning through DIM

    Hi,
    I am trying to load the metadata extracted from DRM into Period dimension in Hyperion Planning through Informatica using DIM. But I am getting the following error:
    Record [[YearTotal, Period, Total Year, Dynamic Calc, 0, null, null, null, null, Unspecified, null, null, null, null, ~, ~, ~]] was rejected by the Planning Server.
    Error occurred during load process. Error message is: Cannot load dimension member, error message is: java.lang.RuntimeException: Year operations not handled through this entry point.
    Record [[1stHalf, YearTotal, null, Dynamic Calc, 0, null, null, null, null, Unspecified, null, null, null, null, +, +, +]] was rejected by the Planning Server.
    Error occurred during load process. Error message is: Cannot load dimension member, error message is: java.lang.RuntimeException: Invalid First Child Id
    Appreciate your help.
    Thanks.

    The .otn file is created when essbase is restructuring and once completed renamed to otl, if it does not complete it can leave the .otn file.
    You should be able to delete the otn (maybe stop the application first) and open the outline.
    I would also check the logs generated from ODI and also the essbase app logs to troubleshoot the issue.
    Cheers
    John
    http://john-goodwin.blogspot.com/

  • Hyperion Planning : Period Dimension in Days

    I need to realize a period dimension in days! Moreover i need to have an organization in week whic include the existence of week day (Sunday, Monday..) to make a comparison beetween all Sunday in differnet Year.
    Is it possible to have a native calendar function in Hyperion Planning, or Does exist another way to solve this problem?
    Thanks

    Best practice would be to use Period dimension down to weeks then create a 'Days' dimension which holds the weekdays, this will help your blocksize too and will allow the reporting requirements you have mentioned.

Maybe you are looking for