Categories
- All Categories
- 15 Oracle Analytics Sharing Center
- 15 Oracle Analytics Lounge
- 208 Oracle Analytics News
- 41 Oracle Analytics Videos
- 15.7K Oracle Analytics Forums
- 6.1K Oracle Analytics Idea Labs
- Oracle Analytics User Groups
- 76 Oracle Analytics Trainings
- 14 Oracle Analytics Data Visualizations Challenge
- Find Partners
- For Partners
Hierarchy - "Supports rollup to higher level of aggregation" option
Has anyone ever played around with the "Supports rollup to a higher level of aggregation" option when setting up a level in a level based hierarchy in OBIEE? I've never even looked at this option before - it's on by default, and I've never needed to turn it off. But I've run into a case where the values in children levels do not necessarily add up to the parent level. I'm wondering if this checkbox is going to help me out.
Please let me know if you do, I'll also post an update after I've finished playing / breaking this.
Thanks,
Scott
Answers
-
p.s. as a follow up, the RPD builder's guide doesn't exactly have a detailed description of what this option does, what the use cases are for not using it, etc. Just a single sentence that mentions this option....and manages not to say anything useful.
Thanks,
Scott
0 -
Yes that's precisely what th box does. But you need to have thr correct sources actually populating the higher levels with data.
Non-linear aggregates are handled like that.
0 -
Hi Christian, thanks for the info. Have you used this in the past, and has it worked ok? I'm assuming when turned on, then I simply need to supply an LTS that hits at the lower level which doesn't aggregate up, as well as one at that next level up the food chain (in my case, level 3 doesn't aggregate to level 2, but level 2 does aggregate to level 1).
Appreciate the help!
Scott
0 -
Yes it works fine. I wouldn't say "simply supply" because when you start this then obviously have to make sure that both the data and the RPD model are both 100& fine. Dynamic aggregates are much more lenient :-)
And yes your other use case will also work - you're just making it extra clever. Relationally this means more effort / config than for example cubes which manage this quite transparently.
0 -
Yeah, I've been looking for a solution which is both a) simple to implement / maintain and b) calculates everything properly, and haven't hit on the right combination yet. At least this option gives me some other alternatives to try.
Thanks!
Scott
0