Since 2008, the U.S. economic position has somewhat stabilized. Many companies trimmed costs in the years following the financial crisis, but still seek solutions for producing organic growth. We are all either growing, stabilizing or merging. With that in mind, we can ask ourselves what can we build, develop or investigate today to help guide our EPM and IT strategies into 2020 and beyond.
A quick look around the software industry today will show even the most casual observer of trends that things have changed, and changed quickly. Not so long ago most software projects were complex entities that required the involvement of both the business and IT resources. Many large implementations were driven by IT as most projects required large hardware and software investments. There was a requirement for significant IT investments, in both time and resources, to get the systems installed, tuned, and to keep them running and functioning. The move to Software-as-a-Service has allowed many departments to deploy software in a much quicker, and less IT driven process. So from a business perspective, the good news is that IT is gone, right? You no longer have a need to open tickets, wait on the server guy, or even worry about what the hardware is doing…or do you?
Executing Clear or Aggregate Calculation Script for Hyperion Planning or Essbase in FDM Classic was accomplished by writing Event Scripts. FDMEE has built-in functionality to execute Calculation Scripts for target applications. Setting up this functionality is very straightforward. I will be illustrating a simple configuration for a specific FDMEE location to execute a Clear Calculation Script Before Loading Data and an Aggregate Calculation Script After Loading Data to a Hyperion Planning application.
Maintain Custom Account Structure Requirements in Planning via Oracle DRM Sourcing: The Oracle Data Relationship Management (DRM) product has always offered impressive flexibility when it comes to meeting the metadata requirements of subscribing target systems. This flexibility extends across numerous products and systems and is not limited to just the EPM stack. This core strength goes back to the origins of the product and has been key to its evolution from its inception with Razza, on to Hyperion MDM, and now within Oracle DRM.
Anyone who has used FDMEE to automate loads via OpenBatch has come across the problem of the “openbatch” directory filling up with archive directories. FDMEE creates an archive directory each time a Batch Execution is run, whether or not any files are processed. This not only clogs up the directory, but also makes it very difficult to find previously loaded files due to FDMEE’s naming convention for archived files.
Let's discuss intra-application modular database metadata hierarchy alignment. What does that mean? When a company develops an out-of-the-box Oracle Hyperion EPBCS application such as Project, Workforce, and Capital Planning there are pre-defined dimensional members and hierarchies that probably do not align with the chart of accounts or other metadata structures specific to that organization. For example, in EPBCS Project the pre-defined account structure has separation of account types such as Revenue, Expense and then more detailed COA categories.
The focus of this blog (#4 in the series) is how to leverage the investment your company has made in establishing a Cloud EPM Vision and Executing successfully on the project. It is in this final phase of the Cloud EPM project implementation that we define our 'success'. Is this project a one-time triumphant event or will we create a Legacy of ongoing improvements and optimal return on our investments?