Author: Zack Carman, Performance Architects
The introduction of Oracle’s Planning and Budgeting Cloud Services (PBCS) not only saw Oracle EPM’s (Hyperion’s) introduction into the cloud but also the addition of more acronyms. One of these acronyms, EPMA, has caused confusion because this acronym describes different capabilities within PBCS versus on-premise Oracle Hyperion Planning solutions. So, what’s the difference?
Enterprise Performance Management Architect (EPMA) is an on-premise component that is used for creating and managing Oracle EPM (Hyperion) applications. Within EPMA, Hyperion applications can be created and deployed from a shared library, which contains a centralized repository of hierarchies and members. By using this piece of Hyperion software, administrators can streamline the addition of applications across multiple Hyperion technologies, including Essbase, Planning, and Hyperion Financial Management (HFM).
EPM Automate is an Oracle Planning and Budgeting Cloud Services (PBCS) tool that is used to communicate with server utilities for situations including automation, or repetitive manual jobs. EPM Automate requires an installation wherever it needs to be called, whether that be on a server or an administrator’s desktop. Through the use of the tool, EPM Automate can run metadata loads, data loads, business rules, etc. This functionality allows EPM Automate to be the true communication source of any lights-out automation that may be needed.
And there you have it. For further information on either one of these components or how to implement them as part of an Oracle EPM initiative, please don’t hesitate to contact the Performance Architects team at sales@performancearchitects.com.