EPM Architect is retiring from EPM 11.2 and beyond - What are my options?...
Oracle EPM 11.2 brings with it a number of significant changes, which we describe here. One of these is the retirement of EPMA. If you have been using EPMA to maintain your metadata across one or more EPM products then now is the time to review your options before upgrading to EPM 11.2. Fortunately you have a number of solutions from which to choose, so there will be something to suit your needs.
Option 1: Switch to Classic
The Classic method of maintaining metadata is something you will already have. From EPMA you can convert your dimensions to be edited using the Classic method. For Planning applications, it means using the web UI within Planning to maintain the dimensions; for HFM you must use the Metadata Manager, and for Essbase EAS. If you have experience using the dimension editors within Planning, HFM or Essbase then an advantage of this option is that you will be using familiar tools. A disadvantage is that you no longer have a golden source for metadata; each EPM product will now be maintaining its own set of metadata.
Option 2: Cut-Down DRM
Oracle have provided a feature-limited version of its DRM (Data Relationship Management) tool with EPM 11.2 as a replacement for EPMA. You can use the EPMA File Generator utility to export your metadata to an ADS file and import this to DRM. You can then use DRM to make changes to the metadata and export these to Planning, HFM or Essbase. The advantage of DRM is that it offers not available in either EPMA or Classic. You could create validation rules for the metadata, such as enforcing naming conventions for members. You could also store a version history for the metadata so that you could compare current with previous versions. Be aware, however, that this version of DRM works only with EPM 11.2; you cannot use it to manage metadata for other products such as a general ledger.
Option 3: Implement a Master Data Management tool
EPM 11.2 DRM offers a way of managing your EPM metadata, but it is a closed system that cannot share the metadata outside the EPM products. The retiring of EPMA provides an opportunity to consider switching to a Master Data Management tool that will provide a golden source for metadata across your EPM, ERP and CRM products. Applications such as Qubix Cloudbridge can function as the hub for metadata across on-premises and cloud applications, and include features such as versioning, change approvals workflows and automatic synchronisation. Implementing this sort of product will not only provide a replacement for EPMA, but also enable your systems to easily adapt to future changes such as a move to the cloud.
To learn more about Qubix Cloudbridge, check out our website.