Categories
- All Categories
- 121 Oracle Analytics News
- 21 Oracle Analytics Videos
- 14.4K Oracle Analytics Forums
- 5.5K Oracle Analytics Idea Labs
- Oracle Analytics User Groups
- 47 Oracle Analytics Trainings
- 7 Oracle Analytics Data Visualizations Challenge
- 4 Oracle Analytics Career
- 8 Oracle Analytics Industry
- Find Partners
- For Partners
Eliminate 'Ghost Nodes' in Hierarchies
Request to eliminate 'ghost nodes' caused by flattening of hierarchies in FDI as this causes significant confusion for end users.
Comments
-
Hi, Can you provide us with a screenshot which explain the ghost nodes ?
0 -
Hi Krishna, thanks for reaching out. Yes, please see screenshot below - I've highlighted that which I consider a 'ghost node'. This is a small example, and is more pervasive and problematic the further down our COA hierarchy a user navigates.
In our desired outcome, 'TRLBAL' would only show at Level 31 and not continue to Level 30, Level 29, and further; and the same goes for BALSHT and INCSMT where we would like for those to only show on Level 30 and not Level 29 and further.
1 -
Andrew, thanks for sharing the details.
We are hoping that this is exactly how you are seeing data in source after running the flattening process. Are you seeing any discrepancy in terms of how values are propagated to the subsequent levels between Fusion and FDI?
Depending on whether your hierarchy is Ragged (has varying levels down the hierarchy for different nodes) or implemented as skip level (has levels missing in between up the hierarchy), flattening process that you run on Fusion source ends up filling in values at various points to maintain parent child relationship. Metric values are recorded at the leaf node which would be further lower down the order like level 26 or so.
0 -
Hi @Sushil Dhoot-Oracle - our hierarchy is ragged and the duplication created by the flattening process is confusing to end users. Would it be possible to add an option to show this as I've suggested?
0
