1 person found this helpful
Unfortunately, there is NO out of box way to migrate the Calc rules to a different application. According to to the LCM Calculation Manager Migration Prerequisites - Planning, Financial Management, and Essbase applications must be created with the same name as the name in the source before importing their artifacts into Calculation Manager.
change the application name in all xml file with "Find and replace" then try to import...Take backup of calc repository of dev before doing so.
Dayalan Punniyamoorthy wrote:
Unfortunately, there is NO out of box way to migrate the Calc rules to a different application.
That is a bold statement, let us take an example to export rules from an app called PLANTEST to PLANNEW
In Calc Manager., export the rules from the application.
This could be done at rule level or full application level.
Save the export to a file.
Select your target application and import
Rule has been imported.
No out of the box way?
i was going the document way for on-premise - https://docs.oracle.com/cd/E57185_01/EPMLU/EPMLU.pdf
As always you are there to correct the wrong info, i take my statement back and never trust doc unless it's tested
It is also possible through LCM with find and replace but much easier through the Calc Manager UI.
This is definitely working. Though I was looking to achieve this from LCM as my purpose is to automate it.
Still not able to work through how do I mention application name for CalcManager in the import file.
Easiest way for you to import is.
login in to calc manager instance where PLANBCK is available.
Then expand PLANBCK, now try import from right click menu. This should set Application to PLANBCK automatically.
This is only possible when Dimension names and plan types are same in both apps
I have already provided an example through Calculation Manager moving across applications and a different plan type name, the poster said they wanted to automate through LCM
If the solution has to be through usage of LCM , i dont think it is possible unless somebody goes and modifies each rule file in the LCm export. LCM exports each rule in a separate file same thing applies for template as well. So in each file these things have to be modified.
Using a find/replace which has already been discussed