To migrate Financial Management business rules from a previous release of Financial Management to Calculation Manager, you use the Import feature of Calculation Manager.
When you import Financial Management business rules, they are imported as Visual Basic script rule files (.rle files) with SUB statements. Each SUB statement in the rule file is converted into a Calculation Manager script component for the rule and rule set of the SUB statement's calculation type.
Following is a list of the valid SUB statement types:
SUB Calculate
SUB Consolidate
SUB Translate
SUB Allocate
SUB Input
SUB NoInput
SUB Dynamic
SUB Transactions
SUB EquityPickUp
SUB Global
For each SUB statement of a valid calculation type, a ruleset containing one business rule with one script component is created. If there is a SUB statement in the rule file that is not one of the valid calculation types, or if there are functions, they are converted into the Generic calculation type. For example, if there is a SUB statement, Write_To_File(), in the rule file, it is converted to the Generic calculation type, because it is not one of the defined calculation types.
Following are the possible rulesets, rules, and script components that may be created during migration from Financial Management to Calculation Manager:
Sub Calculate
Ruleset
Name: Calculate_Ruleset
Calc type: Calculate
Contains a rule named Calculate_Rule
Rule
Name: Calculate_Rule
Calc type: Calculate
Contains a script component named Calculate_Component
Script component
Name: Calculate_Component
Calc type: Calculate
Contains the corresponding Visual Basic script statement in the script component
Sub Translate
Ruleset
Name: Translate_Ruleset
Calc type: Translate
Contains a rule named Translate_Rule
Rule
Name: Translate_Rule
Calc type: Translate
Contains a script component named Translate_Component
Script component
Name: Translate_Component
Calc type: Translate
Contains the corresponding Visual Basic script statement in the script component
Sub Consolidate
Ruleset
Name: Consolidate_Ruleset
Calc type: Consolidate
Contains a rule called Consolidate_Rule
Rule
Name: Consolidate_Rule
Calc Type: Consolidate
Contains a script component called Consolidate_Component
Script component
Name: Consolidate_Component
Calc Type: Consolidate
Contains the corresponding Visual Basic script statement in the script component
Sub Dynamic
Ruleset
Name: Dynamic_Ruleset
Calc type: Dynamic
Contains a rule called Dynamic_Rule
Rule
Name: Dynamic_Rule
Calc Type: Dynamic
Contains a script component called Dynamic_Component
Script Component
Name: Dynamic_Component
Calc Type: Dynamic
Contains the corresponding Visual Basic script statement in the script component
Sub Input
Ruleset
Name: Input_Ruleset
Calc type: Input
Contains a rule called Input_Rule
Rule
Name: Input_Rule
Calc Type: Input
Contains a script component called Input_Component
Script Component
Name: Input_Component
Calc Type: Input
Contains the corresponding Visual Basic script statement in the script component
Sub NoInput
Ruleset
Name: NoInput_Ruleset
Calc type: NoInput
Contains a rule called NoInput_Rule
Rule
Name: NoInput_Rule
Calc Type: NoInput
Contains a script component called NoInput_Component
Script Component
Name: NoInput_Component
Calc Type: NoInput
Contains the corresponding Visual Basic script statement in the script component
Sub Transactions
Ruleset
Name: Transactions_Ruleset
Calc type: Transactions
Contains a rule called Transactions_Rule
Rule
Name: Transactions_Rule
Calc Type: Transactions
Contains a script component called Transactions_Component
Script Component
Name: Transactions_Component
Calc Type: Transactions
Contains the corresponding Visual Basic script statement in the script component
Sub EquityPickUp
Ruleset
Name: EquityPickUp_Ruleset
Calc type: EquityPickUp
Contains a rule called EquityPickUp_Rule
Rule
Name: EquityPickUp_Rule
Calc Type: EquityPickUp
Contains a script component called EquityPickUp_Component
Script Component
Name: EquityPickUp_Component
Calc Type: EquityPickUp
Contains the corresponding Visual Basic script statement in the script component
Sub Allocate
Ruleset
Name: Allocate_Ruleset
Calc type: Allocate
Contains a rule called Allocate_Rule
Rule
Name: Allocate_Rule
Calc Type: Allocate
Contains a script component called Allocate_Component
Script Component
Name: Allocate_Component
Calc Type: Allocate
Contains the corresponding Visual Basic script statement in the script component
Sub Generic
Ruleset
Name: Generic_Ruleset
Calc type: Generic
Contains one or more rules named <name of non-major sub>_Rule
Rule
Name: <name of non-major sub>_Rule
Calc type: Generic
Contains a script component named <name of non-major sub>_Component
Script component
Name: <name of non-major sub>_Component
Calc type: Generic
Contains the corresponding Visual Basic script statement in the script component
SUB Global
Ruleset
Name: Global_Ruleset
Calc type: Global
Contains one or more rules named Global_Rule
Rule
Name: Global_Rule
Calc Type: Global
Contains a script component called Global_Component
Script component
Name: Global_Component
Calc Type: Global
Contains the corresponding Visual Basic script statement in the script component
To migrate business rules from Financial Management to Calculation Manager:
To migrate Financial Management objects from a prior release into Calculation Manager, you must import them in a file. See Importing Business Rules, Business Rulesets, Templates, and Formula and Script Components.
After all of the SUB statements in the file are converted to rulesets, rules, and script components, and migrated, you can view the calculation objects in Calculation Manager.
If you want to convert the script components to graphical objects, you can create new business rules and formula components in the Rule Designer. You can have a combination of graphical rules and script components. If you do not convert the script components to graphical objects, you can deploy them after you migrate them.