FDMEE Will Bring Some Major Features You’ve Been Waiting For

Building a Better Goldfish

Many of my long standing clients have been using FDM Classic for years.  For the most part, they’re very happy with their goldfish, a la the guided workflow.  So, you can imagine they’re a little leery of this new thing called “FDMEE“.  I get it.  FDM Classic is easy-to-use, has internal controls baked-in the product, and it’s been around for years.

But when it comes to a data transformation tool for Oracle EPM applications, I tell my clients that Oracle has built a better goldfish.  And with the forthcoming release of FDMEE there’s even more reasons to make the switch.

With FDMEE, you go from this guy…


To this guy…


So, What’s Coming in

In the last three months, I’ve had the opportunity to attend KScope14, take part in Oracle’s FDMEE Summit, and I presented a FDMEE customer success story at OpenWorld.  I’ve got the scoop on what’s coming in  Among the variety of enhancements and parity features, here’s a quick list of what my FDM clients will care the most about in

At this point I should point out Oracle’s standard “”Safe Harbor Agreement”.  The Safe Harbor Agreement simply states that some of these features may never see the light of day.  That’s right, no guarantees here (wink, wink).  With that out of the way, here’s what to expect with FDMEE


New Stuff in

Here’s a list of four major enhancements coming to

1) EPM to EPM Data Sync

Learn More

FDMEE will allow you to import data directly from a source EPM application (e.g. HFM) and load to a target EPM application (e.g. Planning) right in the user interface. You will no longer need to generate a data file from the EPM source app.  You will simply identify the source and target EPM applications, map the data, and presto, you’re done!

2) True Integration with FCM

Learn More

A) FCM will be able to launch FDMEE at the Data Load Workbench page for a specific point of view. B) FCM will be able to issue location level locking for a specific point of view.

3) Enhanced Metadata Integration

Learn More

That’s right, FDMEE supports metadata loads. You may not have known that. With, you can load metadata from ERP systems like Oracle eBS and PeopleSoft to EPM target applications, like HFM and Planning. With, FDMEE takes it to the next level. You will be able to load file-based metadata loads.

4) DRM to FDM Map Integration

Learn More

A number of my clients have been using DRM to manage FDM maps for years. Yeah, it’s a custom solution but it’s fairly straight forward. Well, with FDMEE this will be natively supported.

Remaining FDM Classic Features Coming in

With FDMEE Release, most of the worthwhile FDM Classic features have been incorporated in FDMEE.  Here’s a list of remaining parity items that will be rolled out in in

  • Fix Mapping Errors Inside of Data Load Workbench – In FDMEE users can only resolve data load mapping errors on the Data Load Mapping screen.  With users will be able to fix mapping errors right where they’re encountered – on the Data Load Workbench > Validation screen.
  • Location Level POV Locking – Release introduced POV locking to FDMEE, but it only works for all locations.  In, users will be able to lock the POV for individual locations.
  • Export to Excel Option on More Screens – Like FDM Classic, this feature will allow end users to easily export metadata items from just about any screen.
  • Copy Maps Option – Using this feature users can easily copy mapping tables from source location to a target location.
  • Graphical Import Format Builder – Instead of creating import formats for from scratch, users can use this wizard to map source fields to target dimension members.
  • Location Hierarchy Groups – FDMEE has a flat structure for locations, that is it’s simply a listing of locations with no groupings.  With, location groupings (e.g. control review locations) are back!

So, When Do We Get

Oracle hasn’t given an official release date for but we’re hearing Santa may have it in your stocking by end of year.

Important – In this post you will notice a number of references to the “.x” release of, e.g  Why?  Because some features may not be available in the .0 release of  Instead they will be rolled out in a patch release to


  1. Great article

    Thanks for sharing.


    • My pleasure. Thanks for stopping by.


Submit a Comment

Your email address will not be published. Required fields are marked *