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/
Similar Messages
-
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/ -
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..
ThanksWhile 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 -
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?
ThanksBest 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.
-
Planning - Possible to Remove Period Dimension?
Hi,
Client doesn't need Period as everything they do is at year only. Can I remove Period and just use the Year as the 'Time' dimension in a Classic Planning application? Or am I required to have period?Period is one of the required dimensions. At best, you'll have to include a Period dimension with at least one member. (I've never tried it with just one member. I THINK that will work but I'm not certain.)
- Jake -
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
nupdate 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'; -
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,
XXXEPMA!!!!! 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 -
Labels before Page dimensions in Planning web form
Hi,
Is it possible to have the labels before the page dimensions in Planning web forms?
Eg: Entity <Entity dropdown in Page view> Products <Product dropdown in Page view>
I am using EPMA 11.1.1.3 version
Thanks,
Naveen SuramHi,
This sort of question was asked before, have a look at Data form customization
There is nothing available out of the box
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 -
Period dimension error in EPMA
Hi,
We recently imported the ads file using "replace" option in the import profile and we get the below error when we try to deploy the planning application. Tried to reassign the Begbalance member. But still not resolving the problem.
Error : Period dimension 'Period' is missing a Base Time Period member 'BegBalance' that has been deleted since the last deployment. Base Time Period members cannot be deleted once the dimension is deployed.
Error : Period dimension 'Period' contains a Base Time Period member 'BegBalance' that has been added since the last deployment. Base Time Period members cannot be added once the dimension is deployed.
Regards,
Ragav.Hello Mady,
We are using EPMA applications and Classic applications; unfortunately we haven't taken any backup's of these applications.
I heard from some one that by performing EPMA re-configuration there is a chance of loosing the applications. Only Classic applications can be restored.
Please let me know if my understanding is wrong and kindly suggest the next steps to restore the applications.
Currently we are able to login only to Shared Services only; we can login to Workspace/planning but unable to access the applications.
Thanks for your help in advance!
Thanks,
VA -
EPMA Period Dimension - cannot move Base members
I am trying to move Periods out of Quarters and under YearTotal in an already deployed application in EPMA (Planning app).
I want to have YearTotal above Jan-Dec, and Q1-Q4 as Dynamic Calcs with months shared below.
This is all well and good in planning classic where you can just delete the quarters and the months fall under year total.
In EPMA, because this change was not made in advance of deployment, when I make it now I get a validation fail about
"Base Time Periods cannot be moved after an application has been deployed". Fair Enough - if that is the rule then fine but hopefully there is a workaround.
So I moved them back to the original structure, and now I am getting double the number of validation errors - one for moving, and another one for removing !!
Rolled back the EPMA database to resolve the above but my question is has anyone figured a way to move months post deployment ?
Thanks,
DaveI had the same problem and I found a solution.
1/. You have to transform the EPMA application to classic following these instructions:
- Connect to the planning application, in the top menu click on "Administration > Application > Properties"
- Add the property "EDIT_DIM_ENABLED", and set the value to "true"
- Restart Planning Service
- Connect to the "Application Library", right click on your application and select "Diagnostics"
- Check the option “Deployed but classic application in product”, click on “run selected test”, then into the “Test Detail” part check the option “delete from EPMA only” and finally click on "apply".
2/. Connect to the Planning application you make your change into the period dimension. ("Administration > Manage > Dimensions")
3/. Finally you transform your Classic to EPMA application following these instructions:
- Connect to the workspace and use the wizard to convert your classic to epma application ("Navigate > Administer > Transform Classic to EPM Architect")
- Connect to the "Application Library", right click on your application and select "Diagnostics"
- Check the option "Deployed but not in product" click on “run selected test”, then into the “Test Detail” part check the option "Retrieve" and finally the option "Syncronize".
Hope it helps you.
Regards,
David MENDELE
EPM/BI Project Manager at Business & Decision, Lima, Peru. -
Security Access on Period Dimension
Hi,
my system version is 9.3.1. I have a Planning application and i want manage security for the Period dimension.
I was able to define Security access for other standard dimension like Account or Entity but can't understand why it doesn't work with Period.
My Period dimension is quite common (Month-Quarter-TotalYear) and i have implemented Dynamic Time Series on it.
Have you ever implemented Security access on Period Dimension?If yes, how?
Thanks in advance.
StefanoI assume that setting the start period and end period on the scenario is not adequate for your needs? (this will restrict access to periods for a given scenario as long as you are using web input forms or smart view).
- Jake -
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/ -
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,
SivaAs 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. -
How to delete a custom dimension in planning - 9.3.1
Hi
some one please let me know how to delete a custom dimension in planning
ThanksI never promote the method the deletion unless you understand the underlying tables of planning, if you search on the forum you will see posts on the subject just like this one - Delete dimension from planning application
Cheers
John
http://john-goodwin.blogspot.com/
Maybe you are looking for
-
I have a Mac-book, i always use Firefox and never Safari nor anything else! I had it on for a long time, never done any sever crashes! but just a few days ago, Firefox asked for an upgrade which I've done. Now every time I try to run an online video
-
Mysql DataBase connectivity with PI 7.1
Dear Experts, I need to connect Mysql DB table to access the data using PI 7.1 and pass it to ECC RFC. I have configured the sender JDBC channel details as below JDBC Driver : com.mysql.jdbc.Driver Connection : jdbc:mysql://<Server>:<port>/<d
-
Hi, I maintained a price in vk12, and the condition record for today states a price of 17, And i'm creating a billing doc for today. In the codition type, pricing date is set as 'C' to pick the billing date for pricing. Sales order price how ever pic
-
Hello, I want to count how many times the Boolean state has changed. But somehow the stop button cannot abort the statement. Solved! Go to Solution. Attachments: counter test.vi 8 KB
-
ITunes cannot play media from alternate hard drive.
Out of nowhere one day my iTunes (Windows 7) stopped playing my music. I could double click on a song and iTunes would freeze up for a minute, then just unfreeze (No error message or anything). With more research I found out that the only songs that