Moving from On-Premise Oracle Hyperion Planning to Oracle Planning and Budgeting Cloud Service (PBCS): Administrative Utilities

April 12, 2017

Author: Andy Tauro, Performance Architects

As with any move to a new solution and process, the transition from Oracle Hyperion Planning to Oracle Planning and Budgeting Cloud Service (PBCS) presents some new (and sometimes improved) implementation and administration approaches.  In this first installment of a two-part series, I explain the differences between administrative utilities in the solutions.  In short, Hyperion Planning offers multiple utilities to perform specific administrative functions, while PBCS provides one utility.

Some of the key utilities in Hyperion Planning include:

  • Executes business rules defined in the application
  • Refreshes the outline and security filters in the underlying Essbase database
  • OutlineLoad Utility (OLU). Imports dimensional information into the application, and updates the “outline;” also allows for the extract of dimensional data from the application
  • Executes a predefined data map between two “Plan Types”

These utilities can be incorporated into lights-out maintenance schedules in creative ways, and are critical to the functioning of a Hyperion Planning solution as a well-oiled machine. The one downside to this is that each of these utilities have their own syntax of execution parameters, that are similar but make a world of difference in what they do.

In contrast, PBCS has just one – the “EPM Automate” utility (not to be confused with EPMA!). Just like the Hyperion Planning utilities, this utility runs in a Windows or a Linux environment, and comes with a lot of flags that define what task it will run. For instance, equivalents to the above will be:

  • runbusinessrule
  • refreshcube
  • importmetadata / exportmetadata / importdata / exportdata
  • runplantypemap

These and many more options that the “EPM Automate” utility comes with make life simpler on the scripting front, mainly because there are much fewer commands to remember. However, a lot of these commands require a task to be predefined as a “job” in the PBCS application. This shouldn’t really be a hindrance, since most such tasks are defined once and then re-executed many times, especially during lights-out maintenance.

If you need help with this or other aspects of your move to PBCS, or aren’t sure where to start, drop us a line at sales@performancearchitects.com, and we would be happy to help.


© Performance Architects, Inc. and Performance Architects Blog, 2006 - present. Unauthorized use and/or duplication of this material without express and written permission from this blog's author and/or owner is strictly prohibited. Excerpts and links may be used, provided that full and clear credit is given to Performance Architects, Inc. and Performance Architects Blog with appropriate and specific direction to the original content.

Leave a Reply