This content has been marked as final. Show 8 replies
if (your app. is meant to support multiple currencies,) then
you can create a max. of 13 custom dimensions
For Essbase, I never heard of upperbound. May be experts could add in here. Till then, visit the below thread:
Essbase will support the dimensionality than the required but there are performaance implications.
My Recommendation is:
In a BSO application if you are adding more than 7 standard dimensions, recheck again whether it is required or not. Up to 10 some what ok.
Try to eliminate the flat dimensions.
In an ASO application, I have successfully implemented with 17 to 18 dimensions. No issues.
Thank you ..
We have a 34 dimension ASO cube that is 150 GB aggregated. The load and agg time is approximately 9 hours.
Are the dimension number limits still the same on Planning 11?
They have not changed in 11X
As of 188.8.131.52, the limit is 20 dimensions per Planning application for all Plan Types.
This is not an Essbase limitation but is instead driven from the Planning relational schema and probably the application itself (although the latter is just conjecture on my part).
Vivek, (and all dimension hunter :-) )
Well it's more likely that you hit the limitation of human brain.
Will you (and/or your customers) really understand what is going on among all these dimensions.
Usually most people already have problems with more then 5-7 dimensions.
Have you asked how they fill the data and even more complicated how whey will retrieve data and still understand what they are speaking to them?
Maybe I'm old fashion but I suspect more then 10 "real" dimension just seems to suggest a lack of case analysis and indicated a approach of first moving hands and then using brain.
The quality and usefullness of a cube does not increases with the number of dimensions...