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.

Similar Messages

  • Loading Metadata from ODI to Hyperion Planning Custom Dimension

    Customer want to load a metadata from ODI to Hyperion planning customer dimension using flat files(.txt files).
    Is it possible to load the metadata into custom dimension? If this is possible, do we need any other KM for planning except RKM Hyperion Planning?
    Because when i try to map the dimension from source to taget the connection is blanck. Getting "Used by target columns none".
    Please refer the image
    http://1.bp.blogspot.com/_Z0lKn46L41I/TJuZcsQxIjI/AAAAAAAAA90/TTv79fbQ9ks/s1600/ODIIssue.JPG
    Thanks
    Vikram

    Yes you can load to custom dimensions just like the other dimensions, the custom dimensions should be reversed into the model.
    You need to use the IKM SQL to Hyperion Planning, make sure you set the staging area different than the target.
    If you want to see how to load metadata to planning, have a read of :- http://john-goodwin.blogspot.com/2008/10/odi-series-part-5-sql-to-planning.html
    Cheers
    John
    http://john-goodwin.blogspot.com/

  • Multiple planning periods on a day

    Hi All,
    I am using periodic lot sizing where in I am getting deliveries from vendor for number of times on a day to cover multiple requirements on a day. I have defined planning calendar where in at this moment I am able to maintain maximum three periods on a day. But vendor delivers almost 10 times a day. So I want to define upto 10 periods on single day. Do we have any BAdi or user exit to make it possible?
    Please let me know If you need more information about requirement.
    Thanks,
    Shirish

    Hi,
    Can you check whether Time Phased Planning in R3 suits your needs.Here you define Planning cycle along with delivery cycle.
    Thanks,
    nandha

  • Hyperion Planning- Account dimension - Sort Order Issue with ODI 11.1.1.5

    Hello Experts,
    First of all, I thank you everybody in this forum for posting their valuable suggestions.
    I am facing a strange issue with ODI (Version 11.1.1.5) while loading metadata to Planning ACCOUNT dimension (Version 11.1.2.x). I am using a Oracle view to load metadata to this dimension. I have defined the sort order in the view and enabled SORT_ORDER_BY_INPUT. For the fresh load to the dimension, everything is working fine. But, when I move a member from one parent to another parent, and define it as the top member of new parent, it is missing its sort order.
    But it is working fine if you define it as the second, third...or last member under new parent. I have tried all the possible ways by flipping all the properties but unable to fix it.
    Please help me here to resolve this issue.
    Your help is greatly appreciated!!
    Thanks
    Edited by: user11965311 on Sep 20, 2011 7:07 PM

    To be honest I think you are best logging it with Oracle because it sounds like you are doing everything correctly so it could be a bug.
    Have you tested this on any previous versions of ODI or is it a new installation?
    If it does get logged with Oracle please keep me informed of the outcome as I would be interested to hear.
    Cheers
    John
    http://john-goodwin.blogspot.com/

  • SOP planning periods

    We are planning products in SOP where the planning period is a generated period (weeks and months). Planning will be done first in period weeks and then in months i.e., the requirements will be entered for first 4 periods as weeks and then for next 2 periods as months.
    Example
    Planning
    Period           Requirements
    Week 1     100
    Week 2     250
    Week 3     300
    Week 4     400     
    Month 1     1500
    Month 2     2000
    Now we redesigned our planning period pattern as days, weeks and months.
    i.e., Week 1 and Week 2 as days then weeks and months as above.
    Example
    Day 1
    Day 2
    Day 15
    Week 1
    Week 2
    Month 1
    Month 2
    In Set parameters for info structures and key figures if we define the planning periodicity as T (Day), W (Week), M (Month) and generate the period, the system is giving an information message
    No technical period generated for period unit 'day'
    Message no. MA866
    And the period is automatically changed to day.
    Period unit 'day' is used as planning period unit
    Message no. MA859
    There is NO PERIOD GENERATION in the info structure?
    Is it possible to generate the period pattern as Days, weeks and months ? How ?
    Thanks
    Soundar

    Dear rajesha
    The fiscal year variant will be generated when you save the set parameters for info structure.
    In this case the the planning period is chaged to days and no fiscal year variat is generated.
    Thanks
    Soundar

  • 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

  • Can planning have 366 days in Period Dimension

    All,
    There is a business requirement where the users need to enter data in webforms on a daily basis. Can I planning cube have 366 days in their period dimensions?
    Thank you
    n

    update HSP_OBJECT SET OBJECT_NAME='1月1日' where object_name='TP1';
    update HSP_OBJECT SET OBJECT_NAME='1月2日' where object_name='TP2';
    update HSP_OBJECT SET OBJECT_NAME='1月3日' where object_name='TP3';
    update HSP_OBJECT SET OBJECT_NAME='1月4日' where object_name='TP4';
    update HSP_OBJECT SET OBJECT_NAME='1月5日' where object_name='TP5';
    update HSP_OBJECT SET OBJECT_NAME='1月6日' where object_name='TP6';
    update HSP_OBJECT SET OBJECT_NAME='1月7日' where object_name='TP7';
    update HSP_OBJECT SET OBJECT_NAME='1月8日' where object_name='TP8';
    update HSP_OBJECT SET OBJECT_NAME='1月9日' where object_name='TP9';
    update HSP_OBJECT SET OBJECT_NAME='1月10日' where object_name='TP10';
    update HSP_OBJECT SET OBJECT_NAME='1月11日' where object_name='TP11';
    update HSP_OBJECT SET OBJECT_NAME='1月12日' where object_name='TP12';
    update HSP_OBJECT SET OBJECT_NAME='1月13日' where object_name='TP13';
    update HSP_OBJECT SET OBJECT_NAME='1月14日' where object_name='TP14';
    update HSP_OBJECT SET OBJECT_NAME='1月15日' where object_name='TP15';
    update HSP_OBJECT SET OBJECT_NAME='1月16日' where object_name='TP16';
    update HSP_OBJECT SET OBJECT_NAME='1月17日' where object_name='TP17';
    update HSP_OBJECT SET OBJECT_NAME='1月18日' where object_name='TP18';
    update HSP_OBJECT SET OBJECT_NAME='1月19日' where object_name='TP19';
    update HSP_OBJECT SET OBJECT_NAME='1月20日' where object_name='TP20';
    update HSP_OBJECT SET OBJECT_NAME='1月21日' where object_name='TP21';
    update HSP_OBJECT SET OBJECT_NAME='1月22日' where object_name='TP22';
    update HSP_OBJECT SET OBJECT_NAME='1月23日' where object_name='TP23';
    update HSP_OBJECT SET OBJECT_NAME='1月24日' where object_name='TP24';
    update HSP_OBJECT SET OBJECT_NAME='1月25日' where object_name='TP25';
    update HSP_OBJECT SET OBJECT_NAME='1月26日' where object_name='TP26';
    update HSP_OBJECT SET OBJECT_NAME='1月27日' where object_name='TP27';
    update HSP_OBJECT SET OBJECT_NAME='1月28日' where object_name='TP28';
    update HSP_OBJECT SET OBJECT_NAME='1月29日' where object_name='TP29';
    update HSP_OBJECT SET OBJECT_NAME='1月30日' where object_name='TP30';
    update HSP_OBJECT SET OBJECT_NAME='1月31日' where object_name='TP31';
    update HSP_OBJECT SET OBJECT_NAME='2月1日' where object_name='TP32';
    update HSP_OBJECT SET OBJECT_NAME='2月2日' where object_name='TP33';
    update HSP_OBJECT SET OBJECT_NAME='2月3日' where object_name='TP34';
    update HSP_OBJECT SET OBJECT_NAME='2月4日' where object_name='TP35';
    update HSP_OBJECT SET OBJECT_NAME='2月5日' where object_name='TP36';
    update HSP_OBJECT SET OBJECT_NAME='2月6日' where object_name='TP37';
    update HSP_OBJECT SET OBJECT_NAME='2月7日' where object_name='TP38';
    update HSP_OBJECT SET OBJECT_NAME='2月8日' where object_name='TP39';
    update HSP_OBJECT SET OBJECT_NAME='2月9日' where object_name='TP40';
    update HSP_OBJECT SET OBJECT_NAME='2月10日' where object_name='TP41';
    update HSP_OBJECT SET OBJECT_NAME='2月11日' where object_name='TP42';
    update HSP_OBJECT SET OBJECT_NAME='2月12日' where object_name='TP43';
    update HSP_OBJECT SET OBJECT_NAME='2月13日' where object_name='TP44';
    update HSP_OBJECT SET OBJECT_NAME='2月14日' where object_name='TP45';
    update HSP_OBJECT SET OBJECT_NAME='2月15日' where object_name='TP46';
    update HSP_OBJECT SET OBJECT_NAME='2月16日' where object_name='TP47';
    update HSP_OBJECT SET OBJECT_NAME='2月17日' where object_name='TP48';
    update HSP_OBJECT SET OBJECT_NAME='2月18日' where object_name='TP49';
    update HSP_OBJECT SET OBJECT_NAME='2月19日' where object_name='TP50';
    update HSP_OBJECT SET OBJECT_NAME='2月20日' where object_name='TP51';
    update HSP_OBJECT SET OBJECT_NAME='2月21日' where object_name='TP52';
    update HSP_OBJECT SET OBJECT_NAME='2月22日' where object_name='TP53';
    update HSP_OBJECT SET OBJECT_NAME='2月23日' where object_name='TP54';
    update HSP_OBJECT SET OBJECT_NAME='2月24日' where object_name='TP55';
    update HSP_OBJECT SET OBJECT_NAME='2月25日' where object_name='TP56';
    update HSP_OBJECT SET OBJECT_NAME='2月26日' where object_name='TP57';
    update HSP_OBJECT SET OBJECT_NAME='2月27日' where object_name='TP58';
    update HSP_OBJECT SET OBJECT_NAME='2月28日' where object_name='TP59';
    update HSP_OBJECT SET OBJECT_NAME='2月29日' where object_name='TP60';
    update HSP_OBJECT SET OBJECT_NAME='3月1日' where object_name='TP61';
    update HSP_OBJECT SET OBJECT_NAME='3月2日' where object_name='TP62';
    update HSP_OBJECT SET OBJECT_NAME='3月3日' where object_name='TP63';
    update HSP_OBJECT SET OBJECT_NAME='3月4日' where object_name='TP64';
    update HSP_OBJECT SET OBJECT_NAME='3月5日' where object_name='TP65';
    update HSP_OBJECT SET OBJECT_NAME='3月6日' where object_name='TP66';
    update HSP_OBJECT SET OBJECT_NAME='3月7日' where object_name='TP67';
    update HSP_OBJECT SET OBJECT_NAME='3月8日' where object_name='TP68';
    update HSP_OBJECT SET OBJECT_NAME='3月9日' where object_name='TP69';
    update HSP_OBJECT SET OBJECT_NAME='3月10日' where object_name='TP70';
    update HSP_OBJECT SET OBJECT_NAME='3月11日' where object_name='TP71';
    update HSP_OBJECT SET OBJECT_NAME='3月12日' where object_name='TP72';
    update HSP_OBJECT SET OBJECT_NAME='3月13日' where object_name='TP73';
    update HSP_OBJECT SET OBJECT_NAME='3月14日' where object_name='TP74';
    update HSP_OBJECT SET OBJECT_NAME='3月15日' where object_name='TP75';
    update HSP_OBJECT SET OBJECT_NAME='3月16日' where object_name='TP76';
    update HSP_OBJECT SET OBJECT_NAME='3月17日' where object_name='TP77';
    update HSP_OBJECT SET OBJECT_NAME='3月18日' where object_name='TP78';
    update HSP_OBJECT SET OBJECT_NAME='3月19日' where object_name='TP79';
    update HSP_OBJECT SET OBJECT_NAME='3月20日' where object_name='TP80';
    update HSP_OBJECT SET OBJECT_NAME='3月21日' where object_name='TP81';
    update HSP_OBJECT SET OBJECT_NAME='3月22日' where object_name='TP82';
    update HSP_OBJECT SET OBJECT_NAME='3月23日' where object_name='TP83';
    update HSP_OBJECT SET OBJECT_NAME='3月24日' where object_name='TP84';
    update HSP_OBJECT SET OBJECT_NAME='3月25日' where object_name='TP85';
    update HSP_OBJECT SET OBJECT_NAME='3月26日' where object_name='TP86';
    update HSP_OBJECT SET OBJECT_NAME='3月27日' where object_name='TP87';
    update HSP_OBJECT SET OBJECT_NAME='3月28日' where object_name='TP88';
    update HSP_OBJECT SET OBJECT_NAME='3月29日' where object_name='TP89';
    update HSP_OBJECT SET OBJECT_NAME='3月30日' where object_name='TP90';
    update HSP_OBJECT SET OBJECT_NAME='3月31日' where object_name='TP91';
    update HSP_OBJECT SET OBJECT_NAME='4月1日' where object_name='TP92';
    update HSP_OBJECT SET OBJECT_NAME='4月2日' where object_name='TP93';
    update HSP_OBJECT SET OBJECT_NAME='4月3日' where object_name='TP94';
    update HSP_OBJECT SET OBJECT_NAME='4月4日' where object_name='TP95';
    update HSP_OBJECT SET OBJECT_NAME='4月5日' where object_name='TP96';
    update HSP_OBJECT SET OBJECT_NAME='4月6日' where object_name='TP97';
    update HSP_OBJECT SET OBJECT_NAME='4月7日' where object_name='TP98';
    update HSP_OBJECT SET OBJECT_NAME='4月8日' where object_name='TP99';
    update HSP_OBJECT SET OBJECT_NAME='4月9日' where object_name='TP100';
    update HSP_OBJECT SET OBJECT_NAME='4月10日' where object_name='TP101';
    update HSP_OBJECT SET OBJECT_NAME='4月11日' where object_name='TP102';
    update HSP_OBJECT SET OBJECT_NAME='4月12日' where object_name='TP103';
    update HSP_OBJECT SET OBJECT_NAME='4月13日' where object_name='TP104';
    update HSP_OBJECT SET OBJECT_NAME='4月14日' where object_name='TP105';
    update HSP_OBJECT SET OBJECT_NAME='4月15日' where object_name='TP106';
    update HSP_OBJECT SET OBJECT_NAME='4月16日' where object_name='TP107';
    update HSP_OBJECT SET OBJECT_NAME='4月17日' where object_name='TP108';
    update HSP_OBJECT SET OBJECT_NAME='4月18日' where object_name='TP109';
    update HSP_OBJECT SET OBJECT_NAME='4月19日' where object_name='TP110';
    update HSP_OBJECT SET OBJECT_NAME='4月20日' where object_name='TP111';
    update HSP_OBJECT SET OBJECT_NAME='4月21日' where object_name='TP112';
    update HSP_OBJECT SET OBJECT_NAME='4月22日' where object_name='TP113';
    update HSP_OBJECT SET OBJECT_NAME='4月23日' where object_name='TP114';
    update HSP_OBJECT SET OBJECT_NAME='4月24日' where object_name='TP115';
    update HSP_OBJECT SET OBJECT_NAME='4月25日' where object_name='TP116';
    update HSP_OBJECT SET OBJECT_NAME='4月26日' where object_name='TP117';
    update HSP_OBJECT SET OBJECT_NAME='4月27日' where object_name='TP118';
    update HSP_OBJECT SET OBJECT_NAME='4月28日' where object_name='TP119';
    update HSP_OBJECT SET OBJECT_NAME='4月29日' where object_name='TP120';
    update HSP_OBJECT SET OBJECT_NAME='4月30日' where object_name='TP121';
    update HSP_OBJECT SET OBJECT_NAME='5月1日' where object_name='TP122';
    update HSP_OBJECT SET OBJECT_NAME='5月2日' where object_name='TP123';
    update HSP_OBJECT SET OBJECT_NAME='5月3日' where object_name='TP124';
    update HSP_OBJECT SET OBJECT_NAME='5月4日' where object_name='TP125';
    update HSP_OBJECT SET OBJECT_NAME='5月5日' where object_name='TP126';
    update HSP_OBJECT SET OBJECT_NAME='5月6日' where object_name='TP127';
    update HSP_OBJECT SET OBJECT_NAME='5月7日' where object_name='TP128';
    update HSP_OBJECT SET OBJECT_NAME='5月8日' where object_name='TP129';
    update HSP_OBJECT SET OBJECT_NAME='5月9日' where object_name='TP130';
    update HSP_OBJECT SET OBJECT_NAME='5月10日' where object_name='TP131';
    update HSP_OBJECT SET OBJECT_NAME='5月11日' where object_name='TP132';
    update HSP_OBJECT SET OBJECT_NAME='5月12日' where object_name='TP133';
    update HSP_OBJECT SET OBJECT_NAME='5月13日' where object_name='TP134';
    update HSP_OBJECT SET OBJECT_NAME='5月14日' where object_name='TP135';
    update HSP_OBJECT SET OBJECT_NAME='5月15日' where object_name='TP136';
    update HSP_OBJECT SET OBJECT_NAME='5月16日' where object_name='TP137';
    update HSP_OBJECT SET OBJECT_NAME='5月17日' where object_name='TP138';
    update HSP_OBJECT SET OBJECT_NAME='5月18日' where object_name='TP139';
    update HSP_OBJECT SET OBJECT_NAME='5月19日' where object_name='TP140';
    update HSP_OBJECT SET OBJECT_NAME='5月20日' where object_name='TP141';
    update HSP_OBJECT SET OBJECT_NAME='5月21日' where object_name='TP142';
    update HSP_OBJECT SET OBJECT_NAME='5月22日' where object_name='TP143';
    update HSP_OBJECT SET OBJECT_NAME='5月23日' where object_name='TP144';
    update HSP_OBJECT SET OBJECT_NAME='5月24日' where object_name='TP145';
    update HSP_OBJECT SET OBJECT_NAME='5月25日' where object_name='TP146';
    update HSP_OBJECT SET OBJECT_NAME='5月26日' where object_name='TP147';
    update HSP_OBJECT SET OBJECT_NAME='5月27日' where object_name='TP148';
    update HSP_OBJECT SET OBJECT_NAME='5月28日' where object_name='TP149';
    update HSP_OBJECT SET OBJECT_NAME='5月29日' where object_name='TP150';
    update HSP_OBJECT SET OBJECT_NAME='5月30日' where object_name='TP151';
    update HSP_OBJECT SET OBJECT_NAME='5月31日' where object_name='TP152';
    update HSP_OBJECT SET OBJECT_NAME='6月1日' where object_name='TP153';
    update HSP_OBJECT SET OBJECT_NAME='6月2日' where object_name='TP154';
    update HSP_OBJECT SET OBJECT_NAME='6月3日' where object_name='TP155';
    update HSP_OBJECT SET OBJECT_NAME='6月4日' where object_name='TP156';
    update HSP_OBJECT SET OBJECT_NAME='6月5日' where object_name='TP157';
    update HSP_OBJECT SET OBJECT_NAME='6月6日' where object_name='TP158';
    update HSP_OBJECT SET OBJECT_NAME='6月7日' where object_name='TP159';
    update HSP_OBJECT SET OBJECT_NAME='6月8日' where object_name='TP160';
    update HSP_OBJECT SET OBJECT_NAME='6月9日' where object_name='TP161';
    update HSP_OBJECT SET OBJECT_NAME='6月10日' where object_name='TP162';
    update HSP_OBJECT SET OBJECT_NAME='6月11日' where object_name='TP163';
    update HSP_OBJECT SET OBJECT_NAME='6月12日' where object_name='TP164';
    update HSP_OBJECT SET OBJECT_NAME='6月13日' where object_name='TP165';
    update HSP_OBJECT SET OBJECT_NAME='6月14日' where object_name='TP166';
    update HSP_OBJECT SET OBJECT_NAME='6月15日' where object_name='TP167';
    update HSP_OBJECT SET OBJECT_NAME='6月16日' where object_name='TP168';
    update HSP_OBJECT SET OBJECT_NAME='6月17日' where object_name='TP169';
    update HSP_OBJECT SET OBJECT_NAME='6月18日' where object_name='TP170';
    update HSP_OBJECT SET OBJECT_NAME='6月19日' where object_name='TP171';
    update HSP_OBJECT SET OBJECT_NAME='6月20日' where object_name='TP172';
    update HSP_OBJECT SET OBJECT_NAME='6月21日' where object_name='TP173';
    update HSP_OBJECT SET OBJECT_NAME='6月22日' where object_name='TP174';
    update HSP_OBJECT SET OBJECT_NAME='6月23日' where object_name='TP175';
    update HSP_OBJECT SET OBJECT_NAME='6月24日' where object_name='TP176';
    update HSP_OBJECT SET OBJECT_NAME='6月25日' where object_name='TP177';
    update HSP_OBJECT SET OBJECT_NAME='6月26日' where object_name='TP178';
    update HSP_OBJECT SET OBJECT_NAME='6月27日' where object_name='TP179';
    update HSP_OBJECT SET OBJECT_NAME='6月28日' where object_name='TP180';
    update HSP_OBJECT SET OBJECT_NAME='6月29日' where object_name='TP181';
    update HSP_OBJECT SET OBJECT_NAME='6月30日' where object_name='TP182';
    update HSP_OBJECT SET OBJECT_NAME='7月1日' where object_name='TP183';
    update HSP_OBJECT SET OBJECT_NAME='7月2日' where object_name='TP184';
    update HSP_OBJECT SET OBJECT_NAME='7月3日' where object_name='TP185';
    update HSP_OBJECT SET OBJECT_NAME='7月4日' where object_name='TP186';
    update HSP_OBJECT SET OBJECT_NAME='7月5日' where object_name='TP187';
    update HSP_OBJECT SET OBJECT_NAME='7月6日' where object_name='TP188';
    update HSP_OBJECT SET OBJECT_NAME='7月7日' where object_name='TP189';
    update HSP_OBJECT SET OBJECT_NAME='7月8日' where object_name='TP190';
    update HSP_OBJECT SET OBJECT_NAME='7月9日' where object_name='TP191';
    update HSP_OBJECT SET OBJECT_NAME='7月10日' where object_name='TP192';
    update HSP_OBJECT SET OBJECT_NAME='7月11日' where object_name='TP193';
    update HSP_OBJECT SET OBJECT_NAME='7月12日' where object_name='TP194';
    update HSP_OBJECT SET OBJECT_NAME='7月13日' where object_name='TP195';
    update HSP_OBJECT SET OBJECT_NAME='7月14日' where object_name='TP196';
    update HSP_OBJECT SET OBJECT_NAME='7月15日' where object_name='TP197';
    update HSP_OBJECT SET OBJECT_NAME='7月16日' where object_name='TP198';
    update HSP_OBJECT SET OBJECT_NAME='7月17日' where object_name='TP199';
    update HSP_OBJECT SET OBJECT_NAME='7月18日' where object_name='TP200';
    update HSP_OBJECT SET OBJECT_NAME='7月19日' where object_name='TP201';
    update HSP_OBJECT SET OBJECT_NAME='7月20日' where object_name='TP202';
    update HSP_OBJECT SET OBJECT_NAME='7月21日' where object_name='TP203';
    update HSP_OBJECT SET OBJECT_NAME='7月22日' where object_name='TP204';
    update HSP_OBJECT SET OBJECT_NAME='7月23日' where object_name='TP205';
    update HSP_OBJECT SET OBJECT_NAME='7月24日' where object_name='TP206';
    update HSP_OBJECT SET OBJECT_NAME='7月25日' where object_name='TP207';
    update HSP_OBJECT SET OBJECT_NAME='7月26日' where object_name='TP208';
    update HSP_OBJECT SET OBJECT_NAME='7月27日' where object_name='TP209';
    update HSP_OBJECT SET OBJECT_NAME='7月28日' where object_name='TP210';
    update HSP_OBJECT SET OBJECT_NAME='7月29日' where object_name='TP211';
    update HSP_OBJECT SET OBJECT_NAME='7月30日' where object_name='TP212';
    update HSP_OBJECT SET OBJECT_NAME='7月31日' where object_name='TP213';
    update HSP_OBJECT SET OBJECT_NAME='8月1日' where object_name='TP214';
    update HSP_OBJECT SET OBJECT_NAME='8月2日' where object_name='TP215';
    update HSP_OBJECT SET OBJECT_NAME='8月3日' where object_name='TP216';
    update HSP_OBJECT SET OBJECT_NAME='8月4日' where object_name='TP217';
    update HSP_OBJECT SET OBJECT_NAME='8月5日' where object_name='TP218';
    update HSP_OBJECT SET OBJECT_NAME='8月6日' where object_name='TP219';
    update HSP_OBJECT SET OBJECT_NAME='8月7日' where object_name='TP220';
    update HSP_OBJECT SET OBJECT_NAME='8月8日' where object_name='TP221';
    update HSP_OBJECT SET OBJECT_NAME='8月9日' where object_name='TP222';
    update HSP_OBJECT SET OBJECT_NAME='8月10日' where object_name='TP223';
    update HSP_OBJECT SET OBJECT_NAME='8月11日' where object_name='TP224';
    update HSP_OBJECT SET OBJECT_NAME='8月12日' where object_name='TP225';
    update HSP_OBJECT SET OBJECT_NAME='8月13日' where object_name='TP226';
    update HSP_OBJECT SET OBJECT_NAME='8月14日' where object_name='TP227';
    update HSP_OBJECT SET OBJECT_NAME='8月15日' where object_name='TP228';
    update HSP_OBJECT SET OBJECT_NAME='8月16日' where object_name='TP229';
    update HSP_OBJECT SET OBJECT_NAME='8月17日' where object_name='TP230';
    update HSP_OBJECT SET OBJECT_NAME='8月18日' where object_name='TP231';
    update HSP_OBJECT SET OBJECT_NAME='8月19日' where object_name='TP232';
    update HSP_OBJECT SET OBJECT_NAME='8月20日' where object_name='TP233';
    update HSP_OBJECT SET OBJECT_NAME='8月21日' where object_name='TP234';
    update HSP_OBJECT SET OBJECT_NAME='8月22日' where object_name='TP235';
    update HSP_OBJECT SET OBJECT_NAME='8月23日' where object_name='TP236';
    update HSP_OBJECT SET OBJECT_NAME='8月24日' where object_name='TP237';
    update HSP_OBJECT SET OBJECT_NAME='8月25日' where object_name='TP238';
    update HSP_OBJECT SET OBJECT_NAME='8月26日' where object_name='TP239';
    update HSP_OBJECT SET OBJECT_NAME='8月27日' where object_name='TP240';
    update HSP_OBJECT SET OBJECT_NAME='8月28日' where object_name='TP241';
    update HSP_OBJECT SET OBJECT_NAME='8月29日' where object_name='TP242';
    update HSP_OBJECT SET OBJECT_NAME='8月30日' where object_name='TP243';
    update HSP_OBJECT SET OBJECT_NAME='8月31日' where object_name='TP244';
    update HSP_OBJECT SET OBJECT_NAME='9月1日' where object_name='TP245';
    update HSP_OBJECT SET OBJECT_NAME='9月2日' where object_name='TP246';
    update HSP_OBJECT SET OBJECT_NAME='9月3日' where object_name='TP247';
    update HSP_OBJECT SET OBJECT_NAME='9月4日' where object_name='TP248';
    update HSP_OBJECT SET OBJECT_NAME='9月5日' where object_name='TP249';
    update HSP_OBJECT SET OBJECT_NAME='9月6日' where object_name='TP250';
    update HSP_OBJECT SET OBJECT_NAME='9月7日' where object_name='TP251';
    update HSP_OBJECT SET OBJECT_NAME='9月8日' where object_name='TP252';
    update HSP_OBJECT SET OBJECT_NAME='9月9日' where object_name='TP253';
    update HSP_OBJECT SET OBJECT_NAME='9月10日' where object_name='TP254';
    update HSP_OBJECT SET OBJECT_NAME='9月11日' where object_name='TP255';
    update HSP_OBJECT SET OBJECT_NAME='9月12日' where object_name='TP256';
    update HSP_OBJECT SET OBJECT_NAME='9月13日' where object_name='TP257';
    update HSP_OBJECT SET OBJECT_NAME='9月14日' where object_name='TP258';
    update HSP_OBJECT SET OBJECT_NAME='9月15日' where object_name='TP259';
    update HSP_OBJECT SET OBJECT_NAME='9月16日' where object_name='TP260';
    update HSP_OBJECT SET OBJECT_NAME='9月17日' where object_name='TP261';
    update HSP_OBJECT SET OBJECT_NAME='9月18日' where object_name='TP262';
    update HSP_OBJECT SET OBJECT_NAME='9月19日' where object_name='TP263';
    update HSP_OBJECT SET OBJECT_NAME='9月20日' where object_name='TP264';
    update HSP_OBJECT SET OBJECT_NAME='9月21日' where object_name='TP265';
    update HSP_OBJECT SET OBJECT_NAME='9月22日' where object_name='TP266';
    update HSP_OBJECT SET OBJECT_NAME='9月23日' where object_name='TP267';
    update HSP_OBJECT SET OBJECT_NAME='9月24日' where object_name='TP268';
    update HSP_OBJECT SET OBJECT_NAME='9月25日' where object_name='TP269';
    update HSP_OBJECT SET OBJECT_NAME='9月26日' where object_name='TP270';
    update HSP_OBJECT SET OBJECT_NAME='9月27日' where object_name='TP271';
    update HSP_OBJECT SET OBJECT_NAME='9月28日' where object_name='TP272';
    update HSP_OBJECT SET OBJECT_NAME='9月29日' where object_name='TP273';
    update HSP_OBJECT SET OBJECT_NAME='9月30日' where object_name='TP274';
    update HSP_OBJECT SET OBJECT_NAME='10月1日' where object_name='TP275';
    update HSP_OBJECT SET OBJECT_NAME='10月2日' where object_name='TP276';
    update HSP_OBJECT SET OBJECT_NAME='10月3日' where object_name='TP277';
    update HSP_OBJECT SET OBJECT_NAME='10月4日' where object_name='TP278';
    update HSP_OBJECT SET OBJECT_NAME='10月5日' where object_name='TP279';
    update HSP_OBJECT SET OBJECT_NAME='10月6日' where object_name='TP280';
    update HSP_OBJECT SET OBJECT_NAME='10月7日' where object_name='TP281';
    update HSP_OBJECT SET OBJECT_NAME='10月8日' where object_name='TP282';
    update HSP_OBJECT SET OBJECT_NAME='10月9日' where object_name='TP283';
    update HSP_OBJECT SET OBJECT_NAME='10月10日' where object_name='TP284';
    update HSP_OBJECT SET OBJECT_NAME='10月11日' where object_name='TP285';
    update HSP_OBJECT SET OBJECT_NAME='10月12日' where object_name='TP286';
    update HSP_OBJECT SET OBJECT_NAME='10月13日' where object_name='TP287';
    update HSP_OBJECT SET OBJECT_NAME='10月14日' where object_name='TP288';
    update HSP_OBJECT SET OBJECT_NAME='10月15日' where object_name='TP289';
    update HSP_OBJECT SET OBJECT_NAME='10月16日' where object_name='TP290';
    update HSP_OBJECT SET OBJECT_NAME='10月17日' where object_name='TP291';
    update HSP_OBJECT SET OBJECT_NAME='10月18日' where object_name='TP292';
    update HSP_OBJECT SET OBJECT_NAME='10月19日' where object_name='TP293';
    update HSP_OBJECT SET OBJECT_NAME='10月20日' where object_name='TP294';
    update HSP_OBJECT SET OBJECT_NAME='10月21日' where object_name='TP295';
    update HSP_OBJECT SET OBJECT_NAME='10月22日' where object_name='TP296';
    update HSP_OBJECT SET OBJECT_NAME='10月23日' where object_name='TP297';
    update HSP_OBJECT SET OBJECT_NAME='10月24日' where object_name='TP298';
    update HSP_OBJECT SET OBJECT_NAME='10月25日' where object_name='TP299';
    update HSP_OBJECT SET OBJECT_NAME='10月26日' where object_name='TP300';
    update HSP_OBJECT SET OBJECT_NAME='10月27日' where object_name='TP301';
    update HSP_OBJECT SET OBJECT_NAME='10月28日' where object_name='TP302';
    update HSP_OBJECT SET OBJECT_NAME='10月29日' where object_name='TP303';
    update HSP_OBJECT SET OBJECT_NAME='10月30日' where object_name='TP304';
    update HSP_OBJECT SET OBJECT_NAME='10月31日' where object_name='TP305';
    update HSP_OBJECT SET OBJECT_NAME='11月1日' where object_name='TP306';
    update HSP_OBJECT SET OBJECT_NAME='11月2日' where object_name='TP307';
    update HSP_OBJECT SET OBJECT_NAME='11月3日' where object_name='TP308';
    update HSP_OBJECT SET OBJECT_NAME='11月4日' where object_name='TP309';
    update HSP_OBJECT SET OBJECT_NAME='11月5日' where object_name='TP310';
    update HSP_OBJECT SET OBJECT_NAME='11月6日' where object_name='TP311';
    update HSP_OBJECT SET OBJECT_NAME='11月7日' where object_name='TP312';
    update HSP_OBJECT SET OBJECT_NAME='11月8日' where object_name='TP313';
    update HSP_OBJECT SET OBJECT_NAME='11月9日' where object_name='TP314';
    update HSP_OBJECT SET OBJECT_NAME='11月10日' where object_name='TP315';
    update HSP_OBJECT SET OBJECT_NAME='11月11日' where object_name='TP316';
    update HSP_OBJECT SET OBJECT_NAME='11月12日' where object_name='TP317';
    update HSP_OBJECT SET OBJECT_NAME='11月13日' where object_name='TP318';
    update HSP_OBJECT SET OBJECT_NAME='11月14日' where object_name='TP319';
    update HSP_OBJECT SET OBJECT_NAME='11月15日' where object_name='TP320';
    update HSP_OBJECT SET OBJECT_NAME='11月16日' where object_name='TP321';
    update HSP_OBJECT SET OBJECT_NAME='11月17日' where object_name='TP322';
    update HSP_OBJECT SET OBJECT_NAME='11月18日' where object_name='TP323';
    update HSP_OBJECT SET OBJECT_NAME='11月19日' where object_name='TP324';
    update HSP_OBJECT SET OBJECT_NAME='11月20日' where object_name='TP325';
    update HSP_OBJECT SET OBJECT_NAME='11月21日' where object_name='TP326';
    update HSP_OBJECT SET OBJECT_NAME='11月22日' where object_name='TP327';
    update HSP_OBJECT SET OBJECT_NAME='11月23日' where object_name='TP328';
    update HSP_OBJECT SET OBJECT_NAME='11月24日' where object_name='TP329';
    update HSP_OBJECT SET OBJECT_NAME='11月25日' where object_name='TP330';
    update HSP_OBJECT SET OBJECT_NAME='11月26日' where object_name='TP331';
    update HSP_OBJECT SET OBJECT_NAME='11月27日' where object_name='TP332';
    update HSP_OBJECT SET OBJECT_NAME='11月28日' where object_name='TP333';
    update HSP_OBJECT SET OBJECT_NAME='11月29日' where object_name='TP334';
    update HSP_OBJECT SET OBJECT_NAME='11月30日' where object_name='TP335';
    update HSP_OBJECT SET OBJECT_NAME='12月1日' where object_name='TP336';
    update HSP_OBJECT SET OBJECT_NAME='12月2日' where object_name='TP337';
    update HSP_OBJECT SET OBJECT_NAME='12月3日' where object_name='TP338';
    update HSP_OBJECT SET OBJECT_NAME='12月4日' where object_name='TP339';
    update HSP_OBJECT SET OBJECT_NAME='12月5日' where object_name='TP340';
    update HSP_OBJECT SET OBJECT_NAME='12月6日' where object_name='TP341';
    update HSP_OBJECT SET OBJECT_NAME='12月7日' where object_name='TP342';
    update HSP_OBJECT SET OBJECT_NAME='12月8日' where object_name='TP343';
    update HSP_OBJECT SET OBJECT_NAME='12月9日' where object_name='TP344';
    update HSP_OBJECT SET OBJECT_NAME='12月10日' where object_name='TP345';
    update HSP_OBJECT SET OBJECT_NAME='12月11日' where object_name='TP346';
    update HSP_OBJECT SET OBJECT_NAME='12月12日' where object_name='TP347';
    update HSP_OBJECT SET OBJECT_NAME='12月13日' where object_name='TP348';
    update HSP_OBJECT SET OBJECT_NAME='12月14日' where object_name='TP349';
    update HSP_OBJECT SET OBJECT_NAME='12月15日' where object_name='TP350';
    update HSP_OBJECT SET OBJECT_NAME='12月16日' where object_name='TP351';
    update HSP_OBJECT SET OBJECT_NAME='12月17日' where object_name='TP352';
    update HSP_OBJECT SET OBJECT_NAME='12月18日' where object_name='TP353';
    update HSP_OBJECT SET OBJECT_NAME='12月19日' where object_name='TP354';
    update HSP_OBJECT SET OBJECT_NAME='12月20日' where object_name='TP355';
    update HSP_OBJECT SET OBJECT_NAME='12月21日' where object_name='TP356';
    update HSP_OBJECT SET OBJECT_NAME='12月22日' where object_name='TP357';
    update HSP_OBJECT SET OBJECT_NAME='12月23日' where object_name='TP358';
    update HSP_OBJECT SET OBJECT_NAME='12月24日' where object_name='TP359';
    update HSP_OBJECT SET OBJECT_NAME='12月25日' where object_name='TP360';
    update HSP_OBJECT SET OBJECT_NAME='12月26日' where object_name='TP361';
    update HSP_OBJECT SET OBJECT_NAME='12月27日' where object_name='TP362';
    update HSP_OBJECT SET OBJECT_NAME='12月28日' where object_name='TP363';
    update HSP_OBJECT SET OBJECT_NAME='12月29日' where object_name='TP364';
    update HSP_OBJECT SET OBJECT_NAME='12月30日' where object_name='TP365';
    update HSP_OBJECT SET OBJECT_NAME='12月31日' where object_name='TP366';

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

  • Cannot find Version, Year, Period dimension while reversing Planning App

    Hi
    I am using Planning application as target for dimension loading.
    When i try to reverse the planning app using RKM Hyperion Planning.
    On reversing i could not find Version, Year & Period as datastores after reverse.
    Is it dependent on planning application version or ODI version.
    I am using 10.1.3.5 for ODI & 11.1.1.3 for Planning.
    Just to update, i was able to get Version as datastore on reversing, but didnt do anything special in that case.
    Now i am facing the problem, that on trying to reverse, i could not get Version, Year, Period as datastores.

    Hi,
    I believe if you are using 11.1.1.3 then it should reverse the extra datastores by default, as far as I am aware the core java files for planning were updated in 11.1.1.3 for this to happen.
    Cheers
    John
    http://john-goodwin.blogspot.com/

  • Security on Year dimension in Hyperion Planning.

    Need to enable security on Year dimension on Hyperion Planning for below requirement. I know that we cannot enable security on year dimenison in Hyperion Planning, but want know if there is any custom solution.
    Requirement:
    IT users to have write access to Scenario: FY12FCSTJUN for year FY12 for period JUN to DEC & FY13 for Period OCT to SEP. (Calender year starts at OCT of every year)
    Normall users they want to have read access to Scenario: FY12FCSTJUN for year FY12 for period JUN to DEC and write access to Scenario: FY12FCSTJUN for Year FY13 for Period OCT to DEC
    1)we can modify the start period, end period, start yr and End yr for FY12FCSTJUN Scenario dimension to make FY12 FY12FCSTJUN as read/write for Specific year, but it won't meet the requirement.
    2)I have already tried making modification to the Planning respository table ( changed the value for ENFORCE_SECURITY parameter to 1 for DIM_ID 38 for Year in the HSP_Dimension table)on one of VM environments,but it won't enable security on the Year dimension.
    3)We can create a Budget scenario to achieve above, but it involves too many changes accross all the webforms and B rules, so we want to see if there is any custom solution available.
    Any suggestion/workaround to resolve the issue?

    Oracle will be releasing a patch in dec 2012 to fix/enable the security on year dimension. this patch is applicable for 11.1.2.2 version.

  • Unable to load Dimension into Hyperion planning using ODI ?

    Hi All
    We are trying to load Dimension into hyperion planning Ver. 11.1.2 using ODI. We have created the interface and mapped the source csv file to target planmning application using ODI KM.
    LKM file to SQL
    IKM SQL to Planning
    We get success in ODI's Operator but the Dimension is not updated nor new data is insreted.
    We get this message in Error file:-
    +
    Retail Format,Parent,Alias: Default,Data Storage,Two Pass Calculation,Smart List,Data Type,Plan Type (APlan),Error_Reason
    ABC,Total Format,,StoreData,,,,Aplan,Cannot load dimension member, error message is: java.lang.RuntimeException: Fetch of saved member "ABC" failed.
    +
    We get this message in log files:-
    +
    2010-07-22 07:04:06,550 INFO [DwgCmdExecutionThread]: Oracle Data Integrator Adapter for Hyperion Planning - Release 9.3.1.1
    2010-07-22 07:04:06,550 INFO [DwgCmdExecutionThread]: Connecting to planning application [******] on [********]:[11333] using username [admin].
    2010-07-22 07:04:06,597 INFO [DwgCmdExecutionThread]: Successfully connected to the planning application.
    2010-07-22 07:04:06,597 INFO [DwgCmdExecutionThread]: The load options for the planning load are
         Dimension Name: Retail Format Sort Parent Child : false
         Load Order By Input : false
         Refresh Database : true
    2010-07-22 07:04:06,612 INFO [DwgCmdExecutionThread]: Begining the load process.
    2010-07-22 07:04:06,612 DEBUG [DwgCmdExecutionThread]: Number of columns in the source result set does not match the number of planning target columns.
    2010-07-22 07:04:06,659 INFO [DwgCmdExecutionThread]: Load type is [Load dimension member].
    2010-07-22 07:04:06,675 ERROR [DwgCmdExecutionThread]: Record [[ABC, Total Format, null, null, StoreData, null, null, null, null, null, null, null, null, null, Aplan, null, null, null]] was rejected by the Planning Server.
    2010-07-22 07:04:06,675 INFO [DwgCmdExecutionThread]: Planing cube refresh operation initiated.
    2010-07-22 07:04:08,425 INFO [DwgCmdExecutionThread]: Planning cube refresh operation completed successfully.
    2010-07-22 07:04:08,425 INFO [DwgCmdExecutionThread]: Load process completed.
    +
    Please help out .....

    Can you check the error log file as you have posted the log file, it should give more information to why the records were rejected.
    Cheers
    John
    http://john-goodwin.blogspot.com/

  • Help! Hyperion Planning Dimension formula no longer works after name change

    Hi,
    I am having an issue with Hyperion Planning. I recently changed an account's dimension name from ASales & Property Taxes (D) to AProperty Taxes (D). However, the original name was used in a formula of another account. When I ran my refresh I got the following error:      
    Error [1200354] detected in member formula for member "AFacilities Costs as a % of Revenue".
    So I went into planning and went to the referenced account and looked at the formula. The formula still had the old member name ASales & Property Taxes (D) so I changed the formula to the new name AProperty Taxes (D). However, when I went to validate the formula I got the following error message:
    Error compiling formula for [] (line 1): expected type [NUMBER] found [STRING] (["ASales & Property Taxes (D)"]) in function []
    However, my formula has the new name not the old name. Here is my formula:
    ("AMaintenance (D)" + "AMaintenance (SG&A)" + "ANon Cap Equipment & Rentals (D)" + "ANon Cap Equipment & Rentals (SG&A)" + "AOperating Leases (D)" + "AOperating Leases (SG&A)" + "ARent & Occupancy Costs (D)" + "ARent & Occupancy Costs (SG&A)" + "AProperty Taxes (D)" + "AProperty Taxes (SG&A)" + "ASecurity (D)" + "ASecurity (SG&A)" + "AInsurance (D)" + "AInsurance (SG&A)")/ARevenue;
    Does anyone know how to fix this problem? Please help, as a result of this issue none of my accounts or clients are getting pulled into the Balance Sheet causing it to not tie with Oracle :( Thanks!!

    Hi,
    What happens if you try and refresh with updating the formula to reference the correct name?
    You won't be able to validate the formula because the member does not yet exist in essbase until the refresh has completed.
    If you have problems you could always, remove the formula and store it, refresh so the new member gets created, then put the formula back and refresh again.
    Cheers
    John
    http://john-goodwin.blogspot.com/

  • How to migrate dimension member text files from ODI to Hyperion Planning

    Hi
    We are having an issue with ODI that it was not connecting to planning.
    Later with some instructions from oracle, we have tried to set some RMI path in websphere and we tested the RMI connectivity test.
    It was successfully connecting to planning.
    Then we want to test that ODI is connecting to planning or not.
    For this I think if anyone can send the doc relating to dimension member upload thru ODI to hyperion planning using text files, it will be helpful.
    Appreciate if anyone can help us on this.
    Please communicate to [email protected] for doc sending.
    Thanks
    Rajesh Reddy

    Go through His(John's) earlier blogs which very clearly explains how to get connected & keep the ball rolling.
    If you're so scared to use the existing connections, you may want to-
    i) Set up new Master & work repository;
    ii) Do few quick configurations from Topology Manager;
    iii) Create your project, models, Interface;
    Let us know if something isn't still clear.
    - Natesh

  • Remove access for each member of a particular dimension from Hyperion Planning Applciation

    We are trying to remove access for groups for each member of a particular dimension( which has more than 1000 members) of a Hyperion Planning application. We are going through Administration->Manage DImensions -> member , Under security click view and select the group and then remove access But the problem is there are more than 1000 members under this dimension , so it will be time consuming to go to each member and then remove access for the group. Is there any other way we can do this?
    Also is there a way to bulk delete native directory groups from Hyperion Shared services, instead of deleting each native group manually one by one?

    The reaso we want to go for Relational tables is that when we did Exportsecurity utility for that planning application  and imported back the SecFile.txt without doing any changes ,still it errored out giving errors like :
    "The following access not imported:-"PLN-ORG-0278-999 Bureau Strtgc & Oprtnl ""PLNning",0278-999,READWRITE,MEMBER due toInvalid user name found in the file."
    It is erroing out even if we did not do any modifications to the secfile.txt.
    Moreover there are more than 1000 members for which we have to remove access permissions manually one by one. It is a tedious process.
    So we are looking at other options like , which relational tables have got Native directory groups information, and the sql queires we can execute to remove the unwanted Native directory groups from Shared Services?

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

Maybe you are looking for

  • Is there a way to create tables that can't update rows

    Hi I have an application where security is very importante. I have tables that con only be inserted and queried, not updated or deleted. Is there a way I can tell Oracle to prohibit update and delete on that table. Regards, Néstor Boscán

  • Can install a hard drive formatted and used on a MacBook (Late 2006) to a MacBook Pro (I believe Mid 2006)

    I just bought a used MacBook Pro and would like to install a hard disk with an existing copy of OS 10.6.8 into what I believe is a Mid 2006 MacBook Pro.  The specs on the MBP are Model Name:          MacBook Pro   Model Identifier:          MacBookPr

  • B75A-G43 low memory frequency

    I have bough MSI B75A-G43 motherboard and four AMD AE34G1609U2-U memory modules (built by Patriot). In BIOS each of modules frequency shown as 1600, but memory frequency set to 1333, and no option 1600 provided in menu. I have updated BIOS to latest

  • How to map primary table for CMP?

    I am using the SunONE studio EE and trying to deploy a CMP Entity bean and get the following error: Validation failed for board.ejb.user.UserBean. Verify that all fields are mapped. CMP Mapping Error in bean User:: Warning: The bean pcImpl0.moduleCom

  • DB to use stand alone Softwares ? Need Help

    Hi friends, My Housing Society has asked me to develop a software for their accounting purpose. As I am well versed with JAVA I would using it for GUI thing. But I could not decide on DB software. I would like to open source softwares and it should b