Migration of HFM application from 11.1.2.2 to 11.1.2.4

Migrating HFM application from 11.1.2.2 to 11.1.2.4 involves several steps -

- Copy application from HFM copy utility
   a. Ensure UDL files of the source and the target app are created correctly. (preferable to run copy utility from the target HFM server.)
   b. When copy, select converting from EPMA to Classic, this ensures copy successfully. You would have to convert it back to EPMA later.


-  Run install configuration from HFM server, and check upgrade from previous release.

- Manual update Hyperion table from the back end. (Oracle is yet to provide patch on this).
Without this step, you won't be able to see the app from Consolidation Administration / Application.
  HSX_DATASOURCES table needs to be manually updated in order to add the application in
  Consolidation Administration.Without this, the HFM app will not show up as an application
  a. To add a new record, open the HSX_DATASOURCES table and insert a new line.
  b. For the new record, enter the following values in the column fields:
      Product = Financial Management
     AppName = <Name of the target application>
     Description = <Description> (optional)
     DSN = unused (should be left blank)

- Right click and select Register to Register the application
   a. Set as "disable" in admin mode by toggle clicking admin mode.

- Provision yourself as the admin of this HFM app, or you will not be able to transform the app.

- Transform from classic to EPMA by Navigate/Administer/transform classic to EPMA. After this is done, the app will show up in Application library.

- Some says you have to export EPMA from source and import it to target. But I don't see you need it.

Comments

Popular posts from this blog

ESSBASE: When to Use FIX vs. IF

Essbase Currently Not Accepting Connections

HFM: Performance Tuning on Application