Troubleshooting Hyperion Calc Manager issues with an emphasis on using Calc Manager with Hyperion Planning.
The purpose of calculation manager is to offer one common interface to design calculation rules for different products (i.e. HFM, Planning, Essbase). The graphical flow provides a clearer view of the calculation process. With reusable rules and components and templates it provides ease of maintenance. Rules can also be organized in a custom folder structure.
Calc manager can be used with EPMA and Classic Planning applications while Business Rules is only used with classic applications.
NOTE: You can see business rules if edit_dim_enabled=true is set in “Manage Properties”. For EPMA applications this is useful if you need to migrate old business rules into calculation manager.
Rule set contains a collection of rules
Rule contains a combination of formula components or script components, in addition to conditional (i.e. IF/Then) and loop objects
Formula Component consists of a collection of formula calculation statements.
Script Component consists of a collection of self contained valid VB scripts (for HFM) or calc command/functions(for Essbase and Planning) statements.
Templates are a set of predefined standard calc related to financial Planning, Essbase (i.e. Clear data, Copy Data, Essbase commands, Amount= Rate*Unit, Aggregate, Allocate), and HFM.
I. Tuning considerations
II. Validation / deployment considerations
If you delete the rule within Calc Manager, it will not be automatically be removed from the Planning application To remove the deleted from from the Plannign application, you have to Go in the deployment view in calc mgr. Uncheck the deleted rules from the list of rules to be deployed and run a full deployment, by right clicking on the app name.
III. Migration considerations
In 126.96.36.199 you are no longer able to use HBR so be sure to review the following documentation before an upgrade to that release
IV. Debug / Launch considerations
The calcmgrconfig.properties contains DEBUG_METHODS=true which is similar to the old DEBUG_ENABLED=true as well as HBR.maxconn , HBR.timeout, and DATABASE_CACHE_REFRESHRATE, and quite a few other settings.
The calcmgrlog4j.properties sets the level of logging for JVM OUTPUT . INFO is usually sufficient unless directed by development to request DEBUG, which will write many extra unnecessary records to the logs. You can set any of these components to log more information.
The following are commented out by default:
For debugging purposes you can enable options to copy xml files that are generated during import, migration, validation, or deployment by uncommenting these lines and providing the valid directory (# eg: c:\\temp\\deploy. Double backslash as a separator is required) in the CalcMgrConfig.properties file
#IMPORT_DIR=<import debug directory>
#MIGRATE_DIR=<migrate debug directory>
#VALIDATE_DIR=<validation debug directory>
#DEPLOY_DIR=<deploy debug directory>
Please note, these properties will eventually moved into the Shared services registry