Period dimension members display

Hi,
we have set up start period to Jan and end period to Mar for Actual /member of scenario/
in planning form we want to display only those three periods however we see all periods /other periods are read-only/.
thanks for help

How about using essbase substitution variables, for example actPeriod1 set as Jan, actPeriod2 set as Feb, actPeriod3 set as Mar, and do the same for Forecast months.
Then put these substitution variables in the form instead of the months.
Then when the months change you can just change the substitution variables and you won't have to touch the forms, the changing of the substitution variables can be scripted with maxl and batched up and scheduled.
Cheers
John
http://john-goodwin.blogspot.com/

Similar Messages

Period Dimension members

Hi All,
I want to calculate Period Dimension members Jan to Dec only.
I have some more period dimension members at level 0.
If I use @LEVMBRS("Period",0), it will caluculate all the level 0 members in the period dimension. But I want to calculate only Jan to Dec.
May I use Jan:Dec in the FIX Statement?
Thanks & Regards,
Sravan Kumar.

Hi,
Yes you can use them in a fix
FIX(Jan:Dec)
ENDFIX
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,
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.

BPC Dimension Members displayed as numbers/index in HANA tables

Hi,
I used the following post from Selva BPC tables in HANA to lookup a BPC model in HANA. However all the dimensions members are represented by numbers/index instead of the actual dimension member description. Is there a way in HANA to see the actual dimension member instead of an index value?
e.g. Category Actual is displayed as 2 and Category Plan as 3 and so on.
Please refer to the screenshot
yogesh

BW also has the values in text correctly. I am not sure if only the dimension member index value is passed on to HANA.
yogesh

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

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,
Dave

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

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

Cannot maintain dimension members in SAP BPC

Hello, Masters in BPC
I have just create mention and want to input data, I used maintain dimension members CUSTOMER in SAP BPC but It seem not effect although I press Process dimension already and I open excel and paste data also saved them already. When I open other dimension and reopen CUSTOMER but nothing is shown.
Please give me a advice to resolve the problem.
Thanks you so much.
Best Regards
Chinh

Dear Raju,
Yes, I did it some times but nothing is happen,
I maintain dimension members, I did it as below:
- Choose maintain dimension members
- copy data from excel file and paste into the dimension
- click process dimension
Show a dialog
- Uncheck Take system offine
This task is successful.
but I go to dimension ACCOUNT in order to insert data,
I came back maintain dimension members : CUSTOMER but I see no data is displayed.
It is the same for ACCOUNT when I want to see data on that dimension
when I try one more time , I click save to server, The Error message show that : Dump Error
I reinstall BPC client and its patch but nothing to change
How can I do???
Thanks

Attribute Dimension members in Planning Data form

Hi All,
Can we see Attribute dimension members in Planning data form ? Pls. help

Yes it is possible in 11.1.1.3, for example in your row select a dimension that has attributes associated with it. select dimension properties next to the down drop.
Tick "Enable custom attribute display (setting applies to all dimensions with associated attributes): "
Select the attribute dimension
Cheers
John
http://john-goodwin.blogspot.com/

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)

Dimension Members in BPC is not updating

Dear Friends,
I have trasfered the values of the 0GL_ACCOUNt to the account dim of my appset in BW using the transformation and i could see the values in the BPC display dimension members.
But simillary i have created the transformation and uploaded the values of the 0Move_type to the flow dimension and am trying to view the same in the BPC but am not getting any valuess in dimension member list of the Flow dim.
I too closed and reopened the admin console. What could be the reason, kindly suggest.
Thanks
Prem

There is a task in the Action Pane from BPC Administration to Refresh client dimension members. Try it. Also try to save and process your dimension again. Finally, hate to state the obvious but make sure your DTP loaded to the right infoobject which was generated from BPC. Do you see the master data in BW from RSD1?
Best regards,
[Jeffrey Holdeman|http://wiki.sdn.sap.com/wiki/display/profile/Jeffrey+Holdeman]
SAP BusinessObjects
Enterprise Performance Management
Regional Implementation Group

Top 10 lowest level dimension members based on measure

Hi,
I'm trying to create a condition with JDeveloper to show the top 10 dimension members based on a measure for the lowest level of the hierarchy, but doesn't work.
All other conditions are working well, including top 10 dimension members in other levels of the hierarchy (not in the lowest).
Any suggestion??
I think the dimension is defined ok, all other conditions are working well and the lowest level could be shown with other conditions and drills.
Thanks in advanced....

Hi,
First, my BI Beans version is 9.0.3.5 and my database version is 9.2.0.2.1
I will try to clarify my problem. I am trying to create a graph to show the top10 members of a dimension based on my measure. When I define this condition
to show the top 10 members of a middle level (not de low level), it works fine, I mean, it shows the top 10 members of that level. But, when I define the condition
to show the top 10 members of the low level, it displays me that there is no data to display (The data has an insufficient number of columns and rows).
I have been testing this case, and I have seen that if I change the low level column (number type) of the dimension to a varchar type column, it works. This low level is
the primary key of the dimension table, and it's referenced by a foreign key in the fact table.
Which could be the problem?? Is it not possible to define a level of a dimension with a number column??
I have a demo sample to see this problem (two simple dimensionS with three levels and a fact table). It's a bit large to post it complete, so I post here an extract of it.
-- Dimension and fact tables
CREATE TABLE PR_DIM_A (DIM_A_KEY NUMBER,
               LOW_A_LEVEL_NAME VARCHAR2(50),
               ALL_A_LEVEL_ID VARCHAR2(50), ALL_A_LEVEL_NAME VARCHAR2(50),
               GROUP_A_LEVEL_ID VARCHAR2(50), GROUP_A_LEVEL_NAME VARCHAR2(50),
               CONSTRAINT PK_DIM_A PRIMARY KEY (DIM_A_KEY));
CREATE TABLE PR_DIM_B (DIM_B_KEY NUMBER,
               LOW_B_LEVEL_NAME VARCHAR2(50),
               ALL_B_LEVEL_ID VARCHAR2(50), ALL_B_LEVEL_NAME VARCHAR2(50),
               GROUP_B_LEVEL_ID VARCHAR2(50), GROUP_B_LEVEL_NAME VARCHAR2(50),
               CONSTRAINT PK_DIM_B PRIMARY KEY (DIM_B_KEY));
CREATE TABLE PR_FACTS (FACT_KEY NUMBER, DIM_A_KEY NUMBER, DIM_B_KEY NUMBER,
               MEASURE_1 NUMBER, MEASURE_2 NUMBER,
               CONSTRAINT PK_FACTS PRIMARY KEY (FACT_KEY));
ALTER TABLE PR_FACTS ADD CONSTRAINT FK_DIM_A FOREIGN KEY (DIM_A_KEY)
               REFERENCES PR_DIM_A (DIM_A_KEY);
ALTER TABLE PR_FACTS ADD CONSTRAINT FK_DIM_B FOREIGN KEY (DIM_B_KEY)
               REFERENCES PR_DIM_B (DIM_B_KEY);
-- Data inserts in the dimensions
INSERT INTO PR_DIM_A VALUES (1,'ALL','ALL_NAMEa','GROUP1a','GROUP1_NAMEa','LOW1a','LOW_NAME1a');
INSERT INTO PR_DIM_A VALUES (2,'ALL','ALL_NAMEa','GROUP1a','GROUP1_NAMEa','LOW2a','LOW_NAME2a');
-- ......... dimension B is the same kind of data.
-- OLAP dimension A creation script
cwm2_olap_dimension.create_dimension('BI02', 'PR_A_DIM', 'DimA Diaplay name', 'DimA Plural name', 'DimA Short Description','DimA Description');
cwm2_olap_dimension_attribute.create_dimension_attribute('BI02', 'PR_A_DIM', 'Short Description', 'Short Descriptions', 'Short Desc', 'Description', TRUE);
cwm2_olap_hierarchy.create_hierarchy('BI02', 'PR_A_DIM', 'HIER_DIM_A', 'HIER_DIM_A Display name', 'HIER_DIM_A ShortDesc', 'HIER_DIM_A Desc','Unsolved Level-Based');
cwm2_olap_dimension.set_default_display_hierarchy( 'BI02', 'PR_A_DIM', 'HIER_DIM_A' );
cwm2_olap_level.create_level('BI02', 'PR_A_DIM', 'ALL_LEVEL_A', 'ALL_LEVEL_A DisplayName', 'ALL_LEVEL_A PluralName', 'ALL_LEVEL_A ShortDesc', 'ALL_LEVEL_A Desc');
cwm2_olap_level.create_level('BI02', 'PR_A_DIM', 'GROUP_LEVEL_A', 'GROUP_LEVEL_A DisplayName', 'GROUP_LEVEL_A PluralName', 'GROUP_LEVEL_A ShortDesc', 'GROUP_LEVEL_A Desc' );
cwm2_olap_level.create_level('BI02', 'PR_A_DIM', 'LOW_LEVEL_A', 'LOW_LEVEL_A DisplayName', 'LOW_LEVEL_A PluralName', 'LOW_LEVEL_A ShortDesc', 'LOW_LEVEL_A Desc' );
cwm2_olap_level_attribute.create_level_attribute('BI02', 'PR_A_DIM', 'Short Description', 'ALL_LEVEL_A', 'Short Description', 'All_LEVEL_A DisplayName', 'ALL_LEVEL_A ShortDesc', 'ALL_LABEL Desc', TRUE );
cwm2_olap_level_attribute.create_level_attribute('BI02', 'PR_A_DIM', 'Short Description', 'GROUP_LEVEL_A', 'Short Description', 'GROUP_LEVEL_A DisplayName', 'GROUP_LEVEL_A ShortDesc', 'GROUP_LEVEL_A Desc', TRUE );
cwm2_olap_level_attribute.create_level_attribute('BI02', 'PR_A_DIM', 'Short Description', 'LOW_LEVEL_A', 'Short Description', 'LOW_LEVEL_A DisplayName', 'LOW_LEVEL_A ShortDesc', 'LOW_LEVEL_A Desc', TRUE );
cwm2_olap_level.add_level_to_hierarchy('BI02', 'PR_A_DIM', 'HIER_DIM_A', 'LOW_LEVEL_A', 'GROUP_LEVEL_A' );
cwm2_olap_level.add_level_to_hierarchy('BI02', 'PR_A_DIM', 'HIER_DIM_A', 'GROUP_LEVEL_A', 'ALL_LEVEL_A' );
cwm2_olap_level.add_level_to_hierarchy('BI02', 'PR_A_DIM', 'HIER_DIM_A', 'ALL_LEVEL_A' );
cwm2_olap_table_map.map_dimtbl_hierlevel('BI02', 'PR_A_DIM', 'HIER_DIM_A', 'ALL_LEVEL_A', 'BI02', dim_table, 'ALL_A_LEVEL_ID' );
cwm2_olap_table_map.map_dimtbl_hierlevel('BI02', 'PR_A_DIM', 'HIER_DIM_A', 'GROUP_LEVEL_A', 'BI02', dim_table, 'GROUP_A_LEVEL_ID' );
cwm2_olap_table_map.map_dimtbl_hierlevel('BI02', 'PR_A_DIM', 'HIER_DIM_A', 'LOW_LEVEL_A', 'BI02', dim_table, 'DIM_A_KEY' );
cwm2_olap_table_map.map_dimtbl_hierlevelattr('BI02', 'PR_A_DIM', 'Short Description', 'HIER_DIM_A', 'ALL_LEVEL_A', 'Short Description', 'BI02', dim_table, 'ALL_A_LEVEL_NAME' );
cwm2_olap_table_map.map_dimtbl_hierlevelattr('BI02', 'PR_A_DIM', 'Short Description', 'HIER_DIM_A', 'GROUP_LEVEL_A', 'Short Description', 'BI02', dim_table, 'GROUP_A_LEVEL_NAME' );
cwm2_olap_table_map.map_dimtbl_hierlevelattr('BI02', 'PR_A_DIM', 'Short Description', 'HIER_DIM_A', 'LOW_LEVEL_A', 'Short Description', 'BI02', dim_table, 'LOW_A_LEVEL_NAME' );
-- OLAP dimension B creation script is similar than A.
-- OLAP CUBE creation script
cwm2_olap_cube.create_cube( 'BI02', 'PR_CUBE', 'Sample Cube', 'Sample Cube', 'Sample Cube' );
cwm2_olap_measure.create_measure('BI02', 'PR_CUBE', 'MEAS1', 'MES1 DisplayName', 'MES1 ShortDesc', 'MES1 Desc');
cwm2_olap_measure.create_measure('BI02', 'PR_CUBE', 'MEAS2', 'MES2 DisplayName', 'MES2 ShortDesc', 'MES2 Desc');
cwm2_olap_cube.add_dimension_to_cube( 'BI02', 'PR_CUBE', 'BI02', 'PR_A_DIM' );
cwm2_olap_cube.add_dimension_to_cube( 'BI02', 'PR_CUBE', 'BI02', 'PR_B_DIM' );
dimkeymap :=
     'DIM:'
|| 'BI02'
|| '.PR_A_DIM/HIER:HIER_DIM_A/LVL:LOW_LEVEL_A/COL:DIM_A_KEY;DIM:'
|| 'BI02'
|| '.PR_B_DIM/HIER:HIER_DIM_B/LVL:LOW_LEVEL_B/COL:DIM_B_KEY;';
cwm2_olap_table_map.map_facttbl_levelkey( 'BI02', 'PR_CUBE', 'BI02', fact_t, /*'ET'*/ 'LOWESTLEVEL', dimkeymap );
cwm2_olap_table_map.map_facttbl_measure( 'BI02', 'PR_CUBE', 'MEAS1', 'BI02', fact_t, 'MEASURE_1', dimkeymap );
cwm2_olap_table_map.map_facttbl_measure( 'BI02', 'PR_CUBE', 'MEAS2', 'BI02', fact_t, 'MEASURE_2', dimkeymap );
Thanks a lot for your help....

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

Sorting Attribute dimension members

Other then reloading attribute dimension members in a different order. Is there a possbility with ODI or the SortMember.cmd utility to perform such a task?
I ask since I know presently while reloading the attribute dimension with ODI it drops the latest member to the bottom. This is not the order I need it in. I tried to mess with the load in ODI and still no fix. I tried to use the SortMember and it only appears to work on all dimension but currency, period, and years as it reads in the planning admin guide. This is for 11.1.2.1.
Does anybody have any input? If so please reply.
Thanks,
DjSmeadly

It is one area that has never been addressed so sorting attribute members is not so easy, as far as I aware the sortmember utility does not work on attribute dimensions.
Cheers
John
http://john-goodwin.blogspot.com/

Period dimension members display

Similar Messages

Maybe you are looking for