Converting a classic planning application to EPMA is simple these days with the transformation wizard. Doing the opposite is not as straight forward. With Oracle’s long-term strategy shifting away from EPMA, this will become more useful over the next few years as people want to convert their EPMA environments to classic.  This post will provide a high-level walkthrough for transforming an EPMA application to classic.

Step 1: Enable Classic Capabilities for the EPMA Application

  1. In Workspace, open the application to the classic Dimension Manager.
    • Navigate > Applications > Planning > Appname
  2. Take a look at the Dimension Manager. For an EPMA application, only viewing capabilities (no tools for editing) should be accessible.
    • Administration > Manage > Dimensions
(click to enlarge)

(click to enlarge)

  1. Navigate to the Application Properties Editor.
    • Administration > Application > Properties
  2. Add the following property (if it does not already exist) and save.  If the property is already present, simply change the value.
    • Property Name: EDIT_DIM_ENABLED 
    • Property Value: true
(click to enlarge)

(click to enlarge)

  1. Log out of Workspace.

Step 2: Restart Environment Services

  1. Log into the environment server and stop services.
  2. Start all of the environment services.

Step 3: Prepare the Application

  1. Return to Workspace and verify the application can now be edited in classic.
    • Administration > Manage > Dimensions
(click to enlarge)

(click to enlarge)

  1. Export planning artifacts to the file system using LCM (Shared Services).  Exclude Essbase Data artifacts, though you may choose not to import them later.
(click to enlarge)

(click to enlarge)

  1. Verify the artifacts exported properly by examining the new file in the Shared Services file system.
  2. Return to the classic Application Properties editor and change the property value EDIT_DIM_ENABLED back to “false” and save.
(click to enlarge)

(click to enlarge)

  1. Log out of Workspace.

Step 4: Restart Environment Services Again

  1. Log into the environment server and stop services.
  2. Start all of the environment services.

Step 5: Complete Conversion

  1. In Workspace, delete the application from the Application Library (EPMA).
(click to enlarge)

(click to enlarge)

  1. Verify that the application was removed from the App Library, Shared Services planning app group, classic app list (Navigate > Applications), and EAS.
  2. Import the application artifacts in Shared Services from the exported backup file.
(click to enlarge)

(click to enlarge)

  1. Verify the application was imported correctly in the planning app list, Dimension Manager, and EAS.

Congratulations. This application has been converted from EPMA to Classic.  Questions? Need help? Feel free to reach out to us at:

Jay Adler, jadler@ecapitaladvisors.com

David Grande, dgrande@ecapitaladvisors.com

Jon Harvey, jharvey@ecapitaladvisors.com

Jon Harvey

Jon has been a part of the Oracle team at eCapital Advisors since 2009 and is passionate about educating and teaching clients and team members how to apply the technology to drive business value within organizations. An Oracle Certified Expert in both Hyperion Planning and Essbase, Jon oversees the technical aspects of EPM project delivery and managed services. In addition, he’s responsible for ensuring the continued growth of the practice’s technical capabilities and serves as the primary interface between eCapital and the Oracle user community.

Comments are closed.