How to Use FDMEE Data Sync to Copy Plan Data from HP to HFM

So, you need to copy data from one EPM application to another, specifically plan data from Hyperion Planning (HP) to Hyperion Financial Management (HFM). In a pre-Oracle Hyperion 11.1.2.4 world this could involve a few moving parts:

• An Essbase report script to export Plan data to a flat file,
• FDM Classic to transform and load Plan data to HFM, and
• Technology X, Y, and Z for end-to-end automation

With Oracle Hyperion Enterprise Performance Management Release 11.1.2.4 all you need is FDMEE Data Synchronization.

Note: Before getting started, make sure your Planning and HFM applications are registered as target applications in FDMEE.

Step 1 – Create your EPM to EPM import format.

Important: To ensure the data is loaded as periodic vs. year-to-date (YTD), you may need to hardcode “Periodic” Value dimension in the import format.

Step 2 – Create a location and associate it with your new import format.

Step 3 – Create a data load rule to stipulate data extract parameters.

Step 4 – Define the source to target application mappings.

Unit test, fine-tune as necessary, and you’re done!

Need to copy Actuals to Planning? See How to Use FDMEE Data Sync to Copy HFM Actuals to Planning.