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?
Hi All, In our organization, data security is highly customized and complex. A single user can have multiple custom data roles assigned based on different security contexts, such as Line Manager, Regional Manager, Country, Area of Responsibility (AOR), Organization, and other business-specific access rules. One of the…
a { text-decoration: none; color: #464feb; } tr th, tr td { border: 1px solid #e6e6e6; } tr th { background-color: #f5f5f5; } Hi All, In our organization, data security is highly customized and complex. A single user can have multiple custom data roles assigned based on different security contexts, such as Line Manager,…
Idea / Enhancement Request Oracle Analytics Cloud (OAC) has introduced the capability to provide public access to analytics content using the BI Public Role, allowing reports and dashboards to be shared with users without requiring authentication. I would like to propose extending similar functionality to Oracle Fusion…
hi All, The existing FDI pre-built artifacts/Common Subject Areas give us useful information about data reload and warehouse refresh activities. However, I see a gap when troubleshooting Data Augmentation execution at row level. For example, we have a BI Publisher report returning approximately 1M rows, but the…
In Fusion Data Intelligence (FDI) release 26.R3.P4, Reporting Configuration provides options to hide Human Capital Management (HCM) and Enterprise Resource Planning (ERP) content. However, an equivalent option is not available for Fusion Supply Chain Management (SCM) content. SCM content remains visible in the catalog…
