Forum Stats

  • 3,817,362 Users
  • 2,259,322 Discussions
  • 7,893,760 Comments

Discussions

Steps for upgrade an EPMA enabled HFM Application from 11.1.2.1 to 11.1.2.4?

Taco
Taco Member Posts: 49 Blue Ribbon
edited Sep 14, 2018 1:54PM in Financial Consolidation

Hello experts,

I'm going to upgrade an EPMA enabled HFM application from 11.1.2.1 to 11.1.2.4, but my past experience was all related to classic HFM applications, and after searching for information on internet, I believe the steps I got used to: [1. copy the app to target env., 2. Manually enter the app info. into Hsx_Datasources and register, 3. run EPM configurator to upgrade from previous release] will not work, but not sure what are the correct high-level steps to take.

From what I've acknowledged, I have to migrate and upgrade EPMA dimensions and rules first. So I plan to :

1. Use EPMA file generator to get the .ads file from previous environment and import it to new environment.

2. Migrate rules using LCM. (Or simply import rules via CM interface)

But after above steps I'm not sure what goes next. Should I create and deploy a new application and try to migrate HFM artifacts into it using LCM from previous version? Or should I still copy the applications to target database and run upgrade wizard and transform it to an EPMA application?

Both way seems not correct but I can't figure out the correct steps. So please help. Many thanks.

Taco.

Tagged:

Answers

  • Aravind_L
    Aravind_L Member Posts: 413 Blue Ribbon
    edited Sep 4, 2018 3:30PM
  • Taco
    Taco Member Posts: 49 Blue Ribbon
    edited Sep 4, 2018 10:42PM

    Hi,

    Thanks for reply. I had checked this document before, I know it's what officially recommended.

    But in my case, I can't go with maintenance release since it's too risky.

    Can you suggest a way I can do migration and upgrade on a new environment?

    Thanks.

    Taco

  • Aravind_L
    Aravind_L Member Posts: 413 Blue Ribbon
    edited Sep 5, 2018 12:04PM

    You can try this :-

    1) Export the application from lower version.

    2) Create a shell application in the upgraded version.

    3) Import the artifacts 

  • Taco
    Taco Member Posts: 49 Blue Ribbon
    edited Sep 7, 2018 11:33PM

    I'm not sure if artifacts can be exported/imported across different versions, but I will try this.

  • SureshM-Oracle
    SureshM-Oracle Member Posts: 407 Employee
    edited Sep 7, 2018 11:58PM

    See if this helps:

  • Taco
    Taco Member Posts: 49 Blue Ribbon
    edited Sep 8, 2018 1:07AM

    Hi SureshM,

    Thanks for providing this link so I can check it as well as hfm admin guide 11.1.2.3. (Surprisingly I found the information I need here which I couldn't find in 11.1.2.4's documentation).

    This approach was actually the first idea comes to my head.

    Migrate and upgrade EPMA library and hfm application separately and redeploy dimensions and rules after everything is done.

    I still has concern that I'm not only migrating applications across servers, but also includes an upgrade from 11.1.2.1 to 11.1.2.4. The copied table schema (by using copy application utility provide with Patch 22323578)  will need to be upgraded by HFM schema upgrade tool. I hope no problem will cause.

    OR, I'm wondering if I can copy the EPMA application to Classic (as mentioned in hfm admin guide 11.1.2.3), run the upgrade, and later transform it into EPMA again, so I can get an EPMA application upgraded without losing data.

    If you have any recommendation, please let me know, thanks.

    Taco

  • Aravind_L
    Aravind_L Member Posts: 413 Blue Ribbon
    edited Sep 14, 2018 1:54PM

    Just out of experience- it can be done , but converting EPMA to classic and then back to EPMA can be cumbersome.

This discussion has been closed.