The idea is to leverage Smart View-style, Essbase-native MDX data processing is integrated with Oracle Analytics Cloud (OAC) Data Visualization rendering with in OAC DV.
Today, Smart View can connect to OAC, consume OAC dashboards, analyses, tables, pivots, and graphs, and even create simple views using OAC as the data source; Smart View also supports Essbase MDX query execution when connected to Essbase or OAC-Essbase sources.
By contrast, when OAC DV connects directly to Essbase or Oracle EPM Cloud, OAC creates datasets from Essbase/EPM cubes and uses the Oracle Analytics/DV query layer to process multidimensional data, hierarchies, filters, calculations, and visual interactions. This can introduce issues such as suboptimal MDX generation, excessive CrossJoin behavior, hierarchy navigation complexity, CASE statement limitations because CASE logic is not supported inside MDX and must be applied in Oracle Analytics, and additional runtime/network overhead.
The idea is therefore to let Smart View or Smart View-like MDX retrieval handle cube-aware data access, while OAC DV focuses on visualization, interaction, dashboarding, and user experience
This approach can improve performance, reliability, and user adoption by separating cube-optimized query execution from visual presentation.
References:
Smart view with OAC , OAC Essbase Connection, OAC EPM Connection, OAC Semantic Model Hierarchies
