Oracle Analytics Cloud Data Visualization Issue with Essbase Cube

Ajinkya Vyawahare

I'm experiencing a technical issue while working with Oracle Analytics Cloud (OAC) Data Visualization with Oracle EPM Essbase cube as the only source

Environment Details:

• Data Source: Oracle EPM Essbase Cube
• Data Preparation: Imported through RPD (Repository)
• Subject Area: Configured with all attributes and measures
• Measure Configuration: External aggregation set in RPD

Specific Problem:

When creating a pivot visualization with more than 22 measures, I'm observing unexpected data behavior:

• Data starts duplicating across all attributes

Specific Questions:

1. What could be causing this measure-related data duplication?
2. Are there known limitations with measure counts in OAC when connecting to Essbase cubes?
3. What troubleshooting steps would you recommend resolving this issue?

Any insights or guidance would be greatly appreciated.

Ajinkya Vyawahare

Can someone please help

SteveF-Oracle

Hi @Ajinkya Vyawahare

Thanks for your question.
I am not aware of any documented limits, per se.

There are some best practices

Work with Cube Measures > About Externally Aggregated Measures

Work with Oracle Essbase Data Sources

This may require a service request so that someone can review it with you, but I will leave this open to other comments.

Wayne Van Sluys

Have you turned on Developer Mode and looked at the Query/MDX that is generated?

When you imported the cube did you flatten the measures?

Ajinkya Vyawahare

HI @Wayne Van Sluys ,

Thanks for the support. Our original configuration consolidated measures into a single column, resulting in complex queries that required navigating hierarchical structures to retrieve account values. This complexity created challenges when developing reports with complex calculations.

In the new data model, after flattening the measures, individual columns for each account generate more straightforward queries by eliminating the need for hierarchical processing. This structural improvement directly addresses our data duplication issues.

I have another question. When a new account is created in the Essbase cube at the source, how do we add that measure in the RPD? Do we need to reimport the cube and then flatten the measures again, or would a metadata refresh work, allowing us to create the same measure column manually and map it to the source?