It’s that time of the year when between office holiday parties, everyone’s getting their budgets finalized and making project plans for the upcoming year.

This season, I’ve decided to create a “HyperionBarbie Holiday Wishlist” based off of the Oracle EPM Roadmap for features and functionality I’m hoping for, and looking forward to, in 2016 and beyond.

The main theme of my list? Hybrid environment support for master data, metadata, and data integration tools. As Oracle keeps placing SKUs in to the cloud, they have to give developers options to implement the final solution.

Remember, Oracle’s Safe harbor statement always applies. Even if I hope my hardest, only Oracle knows when the features and enhancements will be released (if at all). Try not to get your hopes up, just in case Oracle Santa doesn’t pull through!

 Screen Shot 2015-12-09 at 5.00.29 PM.png

DRM Analytics

Tentatively scheduled for the January DRM PSU, I got a demo of the new DRM Analytics interface at OOW15, and I was blown away. This interface essentially taps into your DRM transaction history and provides analysis and feedback on your master data management process. The interface is easy to use, and has pre-built dashboards, graphs, and charts to analyze activity, like:

  • Most Active Users / Least Active Users
  • Most Common Property Updates
  • Node Counts by Node Type (!!!)
  • DRG Workflow Commits

One of the features I found particularly value-added was a graph on node additions and updates, with two lines: one for DRG workflow commits/updates, and one for tasks from a DRM data steward. This graph essentially showed the crossover point to where you DRG workflows are becoming the true master data governance process for your organization. When is the DRG implementation worth the investment? Now you know.

Moreover, the interface is utilizing the new Oracle Simplified Interface format – making it easy for users to navigate and of course, looks very clean. If I remember correctly, it will require a light Java install on your DRM server.

 

FDMEE On-Prem to PBCS Integration

FDMEE is the go-forward tool of choice for metadata and data integration in the EPM space, and since EPM is going cloud, so is FDMEE. On-Prem FDMEE has been increasing in functionality to become the common hub between all applications, and should be able to integration with PBCS in the near future.
What does this mean? No more custom scripting solutions to run EPM Automate out of FDMEE to load data to the cloud; or convoluted data export .bat’s to run PBCS exports to get back to On-Premise.

Also supposedly on the way is FDMEE Integration to the new Financial Close cloud applications, including Financial Consolidation Cloud Service (FCCS), Account Reconciliation Cloud Service (ARCS), and the freshly released Enterprise Performance Reporting Cloud Service (EPRCS) and Supplemental Data Manager (SDM).

Click here to read more about the Oracle EPM Cloud Roadmap from summer 2015.

 

FDMEE & DRM Integration

Bringing two great things together at last (officially)! On the Oracle roadmap for an upcoming FDMEE release is the ability to pull DRM mapping tables directly into FDMEE – this is a far cry from the custom database solutions to import mappings into FDMEE from DRM exports, that many had been doing in the past. The direct integration will be so much cleaner; and perhaps encourage more organizations to maintain mappings within DRM for audit and visibility purposes.

Additional streamlining is on the roadmap in terms of metadata. Currently, downstream applications are refreshed with DRM master data (metadata) using different integration options, ranging from EPMA, Outline Load Utility, ODI, Classic administration, etc. which makes things inconsistent and a little confusing for administrators, and is a little clunky from a design perspective.

The thing is, FDMEE has metadata load capabilities to the EPM suite, so if there is new integration capabilities to pull mappings from DRM, why not metadata too? This will create a unified and consistent methodology of updating downstream applications with both metadata and data, FDMEE orchestrating the entire process.

 

FDMEE-Cloud Enhancements

As another part of investing in the cloud, the FDMEE offering on the cloud is supposedly getting more face lifts. If you are familiar with FDMEE in the cloud for PBCS, you’ll notice that there is a lot of functionality lacking from the cloud offering vs. its on premise counterpart, including no absolutely no scripting, integration adapters (flat file only), or integration to anything other than the single PBCS application for that pod.

For the FDMEE cloud version that comes with PBCS, I’m hoping to see these potential enhancements:

  • PBCS to PBCS data movements
  • Cloud version of Adapters to applications, both On-Prem and Cloud (like EBS, or cloud ERP options),
  • Scripting capabilities (supposedly using Groovy)
  • Metadata loading options

 

PBCS Enterprise

Supposedly also on the way is PBCS Enterprise, which includes Financials, Capex, Project, and Workforce modules (similar to the modules that can be purchased for on-prem Planning) to then be configured for the business. It will likely have the same financial/reporting/ASO PlanTypes available, like its predecessor PBCS.

Supposedly this module will have more functionality around approvals, as well as more graphics and OOTB reports, driven by content. However, will also contain some non-modifiable dimensions.

 

Other EPM Stocking Stuffers:

  • DRM to PBCS direct integration -> without a jump server… could it happen?
  • HFM Web-based metadata editor (bye bye fat client and EPMA!) (coming this year!)
  • More EPM Mobile compatible apps
  • Essbase Cloud Service!
  • DRM Integration to FCCS and BICS (12+ months out)
  • Planning Sandboxing

 

What’s on your Hyperion Christmas List for 2016?

For a debriefing of the Oracle roadmap, published just a few weeks ago, view here (check out slide 41!)