How to Use FDMEE Data Sync to Copy HFM Actuals to Planning

Okay, first off, when it comes to the data synchronization feature in FDMEE, we’re not a fan of the name.  Being techies, when we hear “synchronization” we think true two-way synchronization. That is, data is compared between two systems and reconciled with the latest changes in System A copied to System B and the updates in System B replicated in System A. That’s not how this works.

You use this new FDMEE functionality to copy data from one EPM application to another EPM application. Consider it a one-way sync. So, the name might be a little misleading but this is still one killer feature.  In fact, we think it’s the most significant new feature introduced in FDMEE Release 11.1.2.4.  Why, you ask?

Many of our clients have multi-product EPM environments with both HFM and Planning. And one of the most common monthly tasks is to copy Actuals from HFM to Planning for variance reporting.  FDMEE Data Synchronization, more commonly known as “Data Sync”, makes this really easy.

Data Synchronization isn’t a component with its own a menu item. Instead, Oracle has baked this functionality into the import format and data load rule components. Here’s a rundown of how to set up.

Step 1 – Create your import format.

The import format is used to instruct FDM how to interpret the incoming data from HFM.  For the source application, pick your HFM application.  For the target application, select your Planning application.  From there, map the dimensions accordingly.

Step 2 – Assign your import format to a new location.

Next, create a new location to associate with your new import format.

Step 3 – Create a data load rule.

With your location defined, now it’s time to set up a data load rule. The data load rule is used to specify data extract parameters for pulling data from the source EPM application, i.e. HFM.  On the data load rule, define necessary source filters to refine the incoming data.

Step 4 – Define Data Load Mappings.

Lastly, define your data load mappings. For each dimension, you will use member mappings to derive Planning target system members based on incoming source values from HFM.

That’s it!  You’re now ready to test your copy of HFM Actuals to Planning.  See?  It couldn’t be simpler.

The FDMEE Data Sync feature debuted in 11.1.2.4.  As FDMEE continues to evolve as the hub for all EPM data integrations (on-premises, cloud, and hybrid integrations), Data Sync will strive to put other EPM products and application features out of the data copy, er, synchronization, business.  (Psst!  Essbase Analytics Link for HFM (EAL) and EPMA Data Synchronization: this means you!)

FDMEE Data Sync – It makes copying data from one EPM app to another easier than ever.

See also: How to Use FDMEE Data Sync to Copy Plan Data from HP to HFM