Request to eliminate 'ghost nodes' caused by flattening of hierarchies in FDI as this causes significant confusion for end users.
Hi, Can you provide us with a screenshot which explain the ghost nodes ?
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.
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.
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?
I have a use case for FDI connectors whereby I need to use the EPM Integrator to include planning data in my environment but I have 2 separate EPM environments, one for ERP and one for HCM. Once you create a connection using a connection type, the option to create a new one disappears. This creates an issue where customers…
In the out of the box workbooks, many have default filters for items such as Ledger and Business Unit. Most of these default to the first value alphabetically. This can be incredibly frustrating for users who, when logging in for the first time often get no results or results they are not expecting when they first log in.…
With continuous capabilities being brought into the modern Data Visualisation (DV) experience in OAC and FDI, a native equivalent to the View Selector from Classic Analysis / OBIEE is needed. In Classic reporting, the View Selector allowed users to dynamically swap between different chart types, tables, or analytical views…
OAC saved states are lost when the workbook is moved / migrated to another environment. This feature is intended mostly for personal user preferences but it is also useful for providing preset selecitons for users. If we want to make these presets available for all users , the only way is opening the workbook in the new…
Many organizations need to produce a single employee-level report that combines information from multiple Oracle Fusion Data Intelligence HCM subject areas, including: Workforce Core Goals and Career Development Performance Management Talent Profile Talent Profile Trends A common requirement is to extract, in a single…
