HFM

EPM CLOUD Migration Accelerator Overview

EPM CLOUD Migration Accelerator Overview

EPM Cloud Migration Accelerator (ECMA) is an Oracle utility to assist you migrating an On-Premise HFM (Hyperion Financial Management) application to FCCS (Financial Consolidation and Close Cloud Services), a new tool dedicated to consolidation in Oracle EPM Cloud.

ECMA tool was released end of August 2018 and updated September 21, 2018.

The current release is 1.00.018.

The utility is available on Oracle support under the id 28352563 or on Oracle Cloud MarketPlace with the name EPM Cloud Migration Accelerator.

The zip file contains:

  • ECMA Tool
  • Readme.txt
  • White Paper
  • Sample Applications (4 HFM applications)
  • A Power Point explaining the migration process
  • A 7-minute recording of how to use the tool
  • User Guide Documentation

ECMA is only compliant with HFM 11.1.2.3 and 11.1.2.4.

We tried it with lot of expectations and had some surprises.

We share our first experience with this new tool.

Package preparation

As prerequisite you need to export your HFM application using LCM.

First tip: you will have to modify the LCM package manually.

If you have a look to the LCM package,  you can see that:

ECMA does not consider this file as a valid LCM file:

After deep analysis you will have to put your LCM package in a subfolder as follows.

The simple way it is to unzip the LCM and zip again with the folder to have this:

Now we can start:

  • Migration of Oracle sample application
  • Migration a more complex application (french application)

Blocking issues

At the beginning of the migration process, it is mandatory to define if the application is Multi GAAP or not.

If you choose the Multi GAAP support (manual or calculated) you can have only 3 custom dimensions (movement, multigaap and customX).

If you choose to not support Multi GAAP, you also have only 3 custom dimensions (movement, customX and customY).

HFM applications are built with a minimum of 4 custom dimensions, so to migrate, it is necessary to rethink and rebuild the application with only 3 custom dimensions.
Therefore, in the current situation, it is not possible to migrate with ECMA.

Despite this, we wanted to go through the migration process and here is our report.

Migration with Oracle application

A migration with COMMA or any HFM sample application work fine without any error.

All sample application are designed in unicode and in US standard, therefore without any special characters.

All steps working fine

  • Create migration project

Keep in mind that Multi-GAAP option can’t not be activated if you need 2 custom dimensions.

  • Mapping Dimension

There are some tips to know to make the mapping of dimensions:

Dimensions as Period, Year or View can be mapped with Auto map function.

For others there are 2 choices either by adding as for currency or by correspondence as for Scenario.

WARNING: in the current version, we are not able to have shared members hierarchy. FCCS accepts shared members, this issue is related to the tool.

  • Validate

Will show all error or information as “Unmigrated Dimensions” or “Duplicate Descriptions”. For Duplicate Description, ECMA handles it if you have selected the “Auto-correct duplicate descriptions …” during the Create migration project step.

  • Deploy

This step will create your FCCS application according output metadata from ECMA.

  • View

This is an option which allow you to compare Dimensions and members between input metadata (On Premise) and output metadata (FCCS)

  • Export

Allow you to replace the metadata in output.

After these steps you will have your application skeleton in FCCS.

Everything works fine and quickly for sample applications.

Migration with complex application (french application for example)

On the other hand, when using a complex application, things are much more complicated:

  • HFM complex application have Multi GAAP custom.
  • Accented characters can not be handled in ECMA.

When LCM file is loaded to map dimensions lots we faced a lot of errors about invalid characters.

if you try to ignore these messages, the result will not be better because all dimensions that have accented characters will not appear in the drop down menu for mapping.

In this test, Account and Custom3 are missing as mapping source:

After few calls with Oracle support, they advice us to convert the HFM metadata to unicode without any accented characters before using ECMA.

In spite of all the modifications made, we always encounter errors during the process of migration of a complex application.
We are still working on our migration tests, in relation with Oracle support.

We will keep you informed as soon as we have good news from Oracle support on how to manage a complex application.

See you soon!

Next article Oracle EPM last patches
Previous article EAS jnlp Console doesn't work in SSL

0 Comments

No Comments Yet!

You can be first to comment this post!

Leave a Comment

Your data will be safe! Your e-mail address will not be published. Also other data will not be shared with third person. Required fields marked as *

13 + 19 =