ODTUG Kscope11 is right around the corner. Kscope11 offers the chance for a full day EPM Symposium on Sunday, plus the opportunity to learn from experts in the EPM and BI fields on a wide range of topics.
Edgewater Ranzal will be well represented at the conference, with our associates presenting eight presentations covering Planning, DRM, EPMA, HFM, and FDM. The sessions that we will be presenting at Kscope11 are summarized below. Each title links to an abstract for the presentation, providing additional details.
Over the past several months, and quite possibly the past year or two, there have been numerous discussions regarding the need for a separate master data management (MDM) tool such as Hyperion / Oracle Data Relationship Management (DRM) to manage Hyperion metadata outside of the Enterprise Performance Management Architect (EPMA) tool that comes with Hyperion System 9 and Oracle Fusion 11.
Recently at a users’ conference, I heard comments like “EPMA is DRM ‘Light’” and “EPMA is DRM with a Web interface”.
Hyperion, and obviously now Oracle, has invested deeply in EPMA and it is difficult to identify how and where it might differ from the DRM product. Oracle has even used portions of the DRM base code and underlying architecture in EPMA and when looking at vapor-ware demos, you might draw similar conclusions to those quotes above. In reality, EPMA, in its current state, is a pumped up version of the old Hyperion HUB as it relates to metadata management. Granted, EPMA has updated the user interface leveraging the glyphs (icons) and nomenclature from DRM while completely missing the intellectual aptitude that a master data tool provides.
Below are the key uses that were provided in a recent Oracle presentation as well shows the difference between EPMA and DRM: EPMA
Unifies and aligns application administration processes across the Hyperion EPM system
Imports and shares business dimensions in the Dimension Library
Builds, validates, and deploys applications in the Application Library
Designs and maintains business rules in Calculation Manager
Loads and synchronizes transaction data into and between EPM applications
Manages change of business master data across enterprise applications
Consolidates and rationalizes structures across source systems
Conforms dimensions and validate integrity of attributes and relationships
Synchronizes alternate business views with corporate hierarchies
Key Features include:
i. Versioning and Modeling
ii. Custom rules and validation
iii. Configurable exports
iv. Granular security
v. Change tracking