Database Reference
In-Depth Information
Figure 3.45
EIS catalog migration.
to be rebuilt as Studio hierarchies and deployed to Essbase using the Cube Deployment
Wizard.
often, what people want to do with Studio when they talk of retrofitting exist-
ing models is the population of existing cubes (including hyperion Planning cubes)
with Studio drill-through reports. to reliably populate a drill-through report defini-
tion into an Essbase cube, Studio must deploy the outline. An additional complexity
with Studio drill-through report definitions is that to execute and display reports you
need to use Smart view for office and the Essbase Smart view Provider (Analytic
Provider Services). As such, properly deploying the cube via the Studio (even if just
deploying the application and database definition with Load rule) through the cube
deployment wizard is the best way to ensure your drill through definitions work as
designed.
Instead of concentrating on retrofitting an existing Essbase or Planning model to
contain drill-through definitions, you should consider building a secondary report-
ing model (likely in ASo) to leverage for both larger user reporting and drill-through.
many Planning deployments, for example, contain an ASo component for either
quicker reporting or to combine the Planning data with other required data for com-
plete reporting. you can use Studio to build and deploy this reporting model using the
same dimensionality as the Planning or custom Essbase cubes, and embed the desired
drill-through reports.
In addition to directly connecting to the source relational or flat-file sources, when
working to mimic an existing Planning model, there are a number of options to keep
the dimensionality synchronized between the source Planning model and the Studio
generated cube:
• use shared EPmA dimensions (Figure 3.46): Studio can connect to EmPA as a
data source (Dimension Server) and use “shared” dimensions to build a cube.
• Data relationship management (Drm) exports: Studio can use flat file exports
from Drm to build the reporting cube.
• Financial Quality Data management (FDm): Studio can use either flat file
exports from FDm or can connect directly to the FDm relational table to source
hierarchies.
