I encountered a problem while designing my data model and I hope, anyone can give me a helping hand on that.
------ General Information:
I am using BPC EPM 10.0 SP 10 .NET 3.5 / Build 8001
I have set up a standard model to save some parameters for the profit centers within my planning model (no consolidation model used). These parameters will be saved on a yearly basis. So I have set up a quite simple time dimension (named SC_TIME) with only years as leaf elements and I used the basic attributes mentioned within the online documentation (e.g.: Base Period, Level, Period, Year). The dimension now looks like that:
When I build the model / cube, no errors occur during creation. However after creation I cannot connect to the model by using web report functionality. The screen just freezes after changing the model to the new one and the model navigation pane still shows the dimensions of the old model (before changing model). When I try to connect via EPM I get an error message saying "Invalid Dimension: MEASURES".
After some research I found a document How to maintain MEASURE dimension for Business Planning and Consolidation (http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/b0facd7e-487f-2c10-05bc-8a569e1baeaa?QuickLink=index&overridelayout=true&44981192675211). After checking the tables that maintain the MEASURE formulas I recognized that no entries were made for my new created model. What I did next was:
------ My Questions about the TIME-Dimension:
Does anyone have a hint for me about what I did wrong or how a valid time dimension has to look like? Any help would really be appreciated.
You can use any type of hierarchy in the time dimension. There is no limitation on that. However, you need to be careful with the measure formulas. The document you referred to is published by me only.
The standard measure formulas consider 3 levels in the time hierarchy - YEAR, QUARTER, MONTH. If the number of levels change, you need to adjust the measure formula accordingly. Since, all the data is at the year level, you dont need any measure for YTD. You just need to maintain a formula for the PERIODIC (or better use some other name) measure.
Hope this helps.
thank you for your reply. I will try what you mentioned as soon as I get access to that table to change / add entries.
I guess the MDX statement would look something like that:
MEMBER [MEASURES].[MyMeasureName] AS [%TIME%].[LEVEL01]
MEMBER [MEASURES].[MyMeasureName] AS [%TIME%].CURRENTMEMBER
Would that work?
You mentioned in your document that it is sometimes necessary to maintain those formulas manually. I recognized that even if you take the original TIME dimension and remove the quarter elements and change the hierarchy of the month elements to their new parent <year>.TOTAL, the usage of that adapted dimension would cause the same error I mentioned above.
So, is it correct to say, that the BPC engine cannot interpret non-standard time dimensions and one have to maintain those measure-formulas manually every time you use a adapted dimension? Or is there a hint / trick to build those dimension correct so the BPC engine can interpret the dimension and set up the formulas automatically?
Thanks for your help so far,
You are absolutely right. When we create a model, it creates the measure formulas for that model. And these formulas are standard. In case of a different hierarchy, we might need to change the formula. Please note that there was no need to change the formula, if we had the hierarchy like year -> quarter -> month (the member IDs can be anything).
Hope this helps.
Recently I faced some issues creating a custom measures.
Here is a interesting documentation:
A quite easy to mantain instead tables.
And here is the thread that I opened to solve my issue: