Saturday, July 12, 2014

Decision Package Creation falls due to “An error occurred while running the specified calc script”

Author:-Sanjay Purohit
 Audience:-Hyperion Solution Architect, Functional Lead and Hyperion Business User.
The Hyperion Public Sector Planning and Budgeting (PSPB) out of box Decision Packages (DP) and Budget Request (BR) functionality is not straight forward. The word “Out of Box” really confuses customers. Customers assume no configuration and setups are required to use this functionality. However the assumption is completely wrong. The setup of DP requires functional understanding of business with Hyperion Planning technical knowledge. The first and most import step of DP setup is modification of pre-built business rule “BIUpdateXXXXXXX”. DP enabled application creates BIUpdate(name of plan type) rule for each plan type. Creation and modification of DP runs this rule on planning server. This rule updates values on Essbase to track recurring and non-recurring budget request.  I was not aware about this fact and try to create a baseline decision packet and got the below given error.



Objective
The purpose of this article is to provide you an understanding of BIUpdateXXXX rule and modification requirement before to create decision packages. If decision package option is enabled during the application creation process; it will create BIupdateXXXXXX rule for each plan type (Where XXXX denotes the plan type name).  Since custom dimension are added after the application creation. The application creation process does not know what member to add in the rule. However this theory does not apply on HCP plan type because HCP comes with Out of box dimension and no modification is required at most of the time.  The modification of BIupdateXXX rule is only required on custom plan types where you have to add custom dimension. The default rule creates a fix statement with “FIX ("Period", "Year", "Entity",{Scenario}, {Version})”member combination. This combination is perfect if we don’t add any custom dimension but most of the time we have to add custom dimension to meet requirements.

how To

I will take an example from one of my application where I had few custom dimensions. The default rule does not have all the members and will not work for below given outline. Let say, if we have to update BIUpdateXXX rule as per the below given dimension. I will go ahead and add (UnspecifiedActivity,Unspecified CIPProject,Totalnd,UnspecifiedLocation, and so on  to each dimensions). These unspecified members will be used to tack data in BIUpdateXXX rule.  


 After updating the rule should look like:-


After modification save/validate/deploy the business rule in calculation manager. You would need to modify BIUpdate business rule in all custom plan types. HCP plan type can be ignored. 

Now try creating a DP. You should not see any error. Please read the Oracle document  for more information

No comments:

Post a Comment