Last updated on JULY 28, 2016
Applies to:Hyperion Planning - Version 220.127.116.11.00 and later
Hyperion Essbase - Version 18.104.22.168.00 and later
Hyperion Financial Management - Version 22.214.171.124.00 and later
Information in this document applies to any platform.
How to Migrating Essbase Substitution Variables, which are managed in Calculation Manager, to another environment.
As of Oracle EPM 126.96.36.199, it's not possible to migrate Essbase Substitution Variables from/ to Calculation Manager via LCM separately.
However, it's possible to migrate rules from/ to Calculation Manager via LCM. During this process all corresponding variables (of any type) are migrated alongside the rule. This makes sense since variables are eventually used by a rule.
However the situation is different for Essbase Substitution Variables since they are not necessarily part of any rule but are still required for Planning and Essbase to function.
As of Oracle EPM 188.8.131.52, Essbase Substitution Variables can be migrated as part of the Planning LCM, BUT this means that those Essbase Substitution Variables will only be exported/ imported directly to/ from Essbase during such Planning LCM. It will not create the Essbase Substitution Variable records within Calculation Manager. To clarify, Planning, Essbase and HFM (Oracle EPM product) are naturally not aware of the Calculation Manager (CM). CM is a separate Oracle EPM system component which allows to centrally manage rules and its variables. Only after deploying a rule or variable, they become known to the corresponding Oracle EPM product. It's a one way communication and thus it's not possible to "upgrade" an Essbase Substitution Variable from Essbase to Calculation Manager by using EAS etc.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms