Converting EPMAThe release of Oracle Hyperion On-Premise EPM 11.2 comes with the discontinuation of EPMA metadata management. Anyone who is currently using EPMA to manage their planning applications will have two options to enable their applications in 11.2. The first option is to port existing EPMA-managed planning applications from older environments into classic planning applications in 11.2. The other option for EPMA users is to utilize DRM for metadata management in 11.2. This post will focus on the high-level process for standing up your EPMA app in 11.2 using classic planning.

Converting your EPMA application into a classic planning application requires the creation of a new classic app and building dimensionality using CSV files exported from the current Planning environment. Artifacts for Planning, Calculation Manager, and Reporting can be migrated from and into your 11.2 environment using LCM packages. To get a better understanding of how this is accomplished, a step by step breakdown of migration to 11.2 is provided below.

To begin the migration process to 11.2, you must create a new classic planning application. In your toolbar, go to Navigate->Administer->Planning Administration. Make sure you click on Manage Applications in the left menu, then select the green cross to create a new application. To make the import process as easy as possible, name this new application the same as your previous EPMA application. Also, make sure the Shared Services Project drop down menu is set to Planning to make this a classic planning application. Walk through Application setup to prep your shell application.

The next page will ask you to set up your application Calendar. Make sure you specify your starting year and number of years from your previous application. On the Currencies page, determine if USD will be your default currency and if you will be using multiple currencies. The Plan Types page will help you create the different Plan Types in your application. You will have the option to select 3 Standard Plan Types, 1 ASO Plan Type, a Workforce Planning and a Capital Asset Planning plan type. Make sure you rename one of the Standard Plan Types to match your previous EPMA application you will be migrating from. This will make importing your objects much easier and help avoid unnecessary work later.

Note: Workforce and CapEx plan types will deploy as empty plan types. Pre-built functionality was removed in the 11.2 release.

Navigate to the Finish tab to see an overview of your application settings and click Create. The shell of your classic planning application is now in place.

Next, create shell dimensions as needed until each dimension in the application exists in the target application. In the toolbar, click Navigate->Applications->Refresh. You should now see your newly created application under Planning.

Open the Dimension tab and check the Dimension drop down menu. If any dimension name needs to be changed, click the small pencil to Edit the dimension.

Add dimensions to Planning if necessary so dimensions from each cube match the existing application. Hit the green cross next to the pencil to add a new custom dimension.

Next, create Planning CSV exports of each source dimension from the existing environment. Go back to your old environment and navigate to the Planning application you will be migrating. In the upper toolbar, go to Administration->Import and Export->Export Metadata to File.

In the Dimension drop down menu, select your first dimension and then hit Run. Your export will now begin. Save these CSV’s on your local machine and open your export to make sure everything exported correctly. Complete this step for ALL dimensions.

Navigate to your new classic planning application in 11.2. In the upper toolbar go to Administration->Import and Export->Import Metadata from File. In the Dimension to Import drop-down menu, select your first dimension and browse your machine for the corresponding CSV and hit Run. If you receive an import error, double check that your Import CSV headers are correct and your properties are in the correct column. You may experience a shift in some columns if you have member formulas containing a comma, in which case you will have to manually correct the formula and shift the columns back to their correct positions. You may also need to manually set up the Period dimension for the base ‘YearTotal’ hierarchy if you are experiencing issues with importing a custom Period dimension.

If your Import is successful, you will see a window showing how many records were read and processed. Now go into the newly imported dimension and confirm that all properties and roll up structures look correct.

Now that all dimensionality metadata has been imported successfully, deploy the application outline from Planning to Essbase.

With the outline created, you are now able to import your planning and reporting objects. Using LCM imports will allow you to migrate all forms, business rules, Essbase objects, FR Reports, Task lists, Substitution Variables (etc.) to your 11.2 application.

Check the Migration Status Report to see the status of your LCM Import. You should expect your status to be Completed and have your objects in your new classic planning application.

If the Import Status is Failed, click Failed to see further details on why the import failed so you can make any necessary changes.

Your previous EPMA application should now be successfully recreated in 11.2 as a classic planning application. Be sure to manually check all objects that you imported and test thoroughly.

As a quick review, a brief break-down of the steps needed to enable your new app in 11.2 is below:

  1. Create a shell in 11.2 for your Classic Planning Application
  2. Create a shell of dimensions in Planning
  3. Import CSV metadata files from the existing application into 11.2 to build out dimensionality
  4. Deploy application
  5. Set up application configuration for outline order, dimension processing, and Essbase caches where necessary
  6. Import LCM’s of your planning and reporting objects from your previous application
  7. Manual check of imported objects and test