To migrate Planning business rules and other objects from a previous release of Oracle's Hyperion® Business Rules to Calculation Manager, you use the Migrate feature. When you migrate Business Rules objects to Calculation Manager, business rules are migrated as business rules, sequences are migrated as business rulesets, variables are migrated as variables, and macros are migrated as templates.
Note: | If you have Business Rules projects, they are migrated directly to Planning when you migrate security. |
Following are some considerations for migrating business rules from Business Rules to Calculation Manager:
You migrate business rules from Business Rules to Calculation Manager by migrating the application to which they belong. You can migrate one application at a time.
You can migrate a business rule only once, even if you modify it after you migrate it. However, you can use the migration feature iteratively to migrate new business rules from Business Rules to Calculation Manager.
To migrate business rules, they must meet these criteria:
They must not have been migrated.
They must have an outline that belongs to the application you are migrating.
They must be launchable for all locations in the application in Business Rules or be launchable for at least one of the plan types in the application in Calculation Manager.
When you migrate business rules that are launchable for all locations in the application being migrated, this is what happens:
If an outline is selected in Business Rules, and the outline belongs to the application you are migrating, the business rules are migrated to the application and plan type specified in the outline. If no outline is selected in Business Rules, the business rules are migrated to a default application and plan type, which is specified by the user who is performing the migration in the Calculation Manager Migrate dialog.
The deployment status of the business rules is not migrated.
If business rules are migrated to the default application and plan type, no shortcuts are created in the migrated application.
When you migrate business rules that are launchable for one or more locations in the application being migrated, this is what happens:
If an outline is selected in Business Rules, but it does not belong to the application you are migrating, the business rules are migrated to a default application and plan type, which is specified by the user performing the migration in the Calculation Manager Migrate dialog.
If an outline is selected in Business Rules, and it belongs to the application you are migrating, the business rules are migrated to the application and plan type specified in the outline. If no outline is specified, the business rules are migrated to the first plan type in the Calculation Manager application.
The deployment status of the business rule is set to “Deployed” in the Deployment View of Calculation Manager.
If a business rule has more then one launch location defined for the application in Business Rules, a shortcut is created only for one plan type in the Calculation Manager application, because rule names must be unique across all plan types in Calculation Manager.
Following are some considerations for migrating Capital Asset Planning, Workforce Planning, and Human Capital Planning business rules to Calculation Manager:
Oracle Hyperion Capital Asset Planning, Fusion Edition, Oracle Hyperion Workforce Planning, Fusion Edition, and Human Capital Planning business rules are migrated to the Capital Asset, Workforce, and Human Capital plan types respectively, if the application you are migrating has Capital Asset, Workforce, and Human Capital plan types enabled.
The deployment status is set to “Deployed” in the Deployment View of Calculation Manager.
A shortcut is created in the Capital Asset, Workforce, and Human Capital plan types in the application in Calculation Manager only if the business rule was migrated previously.
Following are some considerations for migrating Business Rules sequences to Calculation Manager:
You can migrate a sequence only once, even if you modify it after you migrate it.
In Business Rules, a sequence can contain rules that can be launched across different applications. Calculation Manager also supports launching rulesets across different applications.
In Business Rules, a business rule within a sequence can have multiple launch locations for the same application. In Calculation Manager, a business rule within a business ruleset can have only one launch location for the same application.
In Business Rules, sequences do not have an outline.
A sequence can be migrated if the following conditions are met:
All rules within the sequence (and within each of the nested sequences) have been migrated successfully.
For all rules in the sequence, if there is a launch location defined for the rule when it is launched as part of the sequence, the launch location should be one of the launch locations defined for the rule when it is launched by itself, and the rule should have been migrated to that location successfully. If both of these conditions are met, the sequence can be migrated.
Each rule within the sequence should have at least one launch location defined in Business Rules to which the rule has been migrated in Calculation Manager. If the launch location for a rule in the sequence is not one of the launch locations defined for the rule itself, the sequence cannot be migrated, because the launch location for the rule is unknown. Also, if a business rule in a sequence has All Locations set as its launch location in Business Rules, the sequence cannot be migrated.
If a sequence is eligible for migration, it is migrated to the application and is displayed in the System View of Calculation Manager, in the Rulesets node at the application level.
When you migrate a sequence, its status in the Deployment View is set to “Deployed.”
If one or more of its rules fails to migrate, the sequence is migrated partially.
Following are some considerations for migrating variables from Business Rules to Calculation Manager:
When you migrate a business rule with variables, the variables are automatically migrated. In Business Rules, variables are either global or local. In Calculation Manager, variables are global (for use in any application), application specific (for use in one application only), plan type specific (Planning users only; for use in one plan type only), or rule specific (Planning users only; for use in one business rule only). When global variables are migrated, they are global variables in Calculation Manager; when local variables are migrated, they are business rule variables in Calculation Manager.
Note:
When you migrate a Business Rules global variable that already exists in Calculation Manager, you can change it from a global to an application variable.
You can migrate a variable only once, even if you modify it after you migrate it.
Variable information that is set at rule level is also migrated.
Launch values assigned to variables at the sequence level are migrated to their equivalents in Calculation Manager.
Following are some considerations for migrating macros from Business Rules to Calculation Manager:
You can migrate a macro only once, even if you modify it after you migrate it.
A macro is migrated to a template in Calculation Manager.
Parameters are migrated to design time prompts in Calculation Manager. Design time prompts are named parm1, parm2, parm3, and so on, and are of the String type.
The macro core is migrated to a graphical script component.
When macros are migrated to templates, the templates are placed in the first plan type of the migrated application.
Macros with nested macros are not migrated.
Following are some considerations for migrating Essbase substitution variables:
Essbase substitution variables at the application and plan type level are migrated the first time an application containing them is migrated. If the application is migrated again, the Essbase substitution variables are not migrated.
Essbase substitution variables at the global level are not migrated.
Note: | The Calculation Manager migration functionality migrates business rules and other objects; it does not migrate projects or launch security for any objects. To migrate projects and launch security to Planning, you must use a utility installed with Planning. (See the Oracle Hyperion Planning Administrator’s Guide.) |
To migrate business rules from Business Rules to Calculation Manager:
In the System View, select Actions, Migrate.
Note:
You can also migrate business rules from the List View and the Custom View. To open one of these views, select View, List View or View, Custom View.
In the Migrate dialog, select an application to migrate from Business Rules.
Note:
The application must be deployed.
In Application, select the default application to which to migrate business rules. You must specify a default application for business rules that are launchable for the application being migrated, but for which no outline was selected in Business Rules or the selected outline does not belong to the current application.
In Migrate Options, select Migrate global variables into an application if you want Business Rules global variables that have the same name as global variables in Calculation Manager to be migrated as application variables.
Select Overwrite existing objects if you want the objects you migrate to overwrite the objects that already exist in the application and plan type.
Select Skip existing objects if you want the objects you migrate to be added to the objects that already exist in the application and plan type.
Select Error out for duplicates if you want to stop the migration process if the objects you migrate duplicate objects that already exist in the application and plan type.