TAGS

Recent Posts

Archives

An Introduction to Business Rules in Oracle Hyperion Planning
Posted on August 22, 2018
Author: Connor Capece, Performance Architects

Business rules are essential for any Oracle Hyperion Planning application. They provide a way for planners to derive metrics and projections from existing data using business logic. When writing a business rule, calculation commands and functions will always be a part of the scripts themselves.

Click here to see a full list of calculation commands. Some frequently used commands include:

  • AGG
  • FIX…ENDFIX
  • DATACOPY
  • CLEARBLOCK

Click here to see a full list of functions. Some frequently used functions include:

  • @RELATIVE
  • @VAR
  • @VARPER
  • @CREATEBLOCK
  • @LIST

To create a business rule, the administrator should follow these steps:

Navigate -> Calculation Manager -> expand application -> expand plan type -> right click on “rules” -> click “new”.

After you click “New,” you’ll be presented with a “New Rule” screen. This is where the administrator names the business rule and makes sure that its application and plan type is set to the correct settings. Ideally, the name of the business rule should describe what it does, for example, “Actuals to Forecast”.

After naming the business rule and clicking “OK,” the administrator should change the mode of this form from “Designer” to “Edit Script”:

The most frequently used command is “FIX/ENDFIX,” which is what I’m using for this example.  This command allows the administrator to define which members to include in the calculation. This means that whatever is in the “FIX” statement will be the data that is affected by the business rule script. Below is an example of a “FIX/ENDFIX” script.

The purpose of this script is to copy all actual data in FY16 to the forecast scenario of the same year in FY16. The key word here is “all.” This is because the “FIX” statement that I created is fixing on all possible intersections in the application that I want in the “Actuals” scenario. The “@RELATIVE” means that I want all level 0 (or leaf) members in that certain dimension. As you can see, I made “Account,” “Entity,” “Period,” and “Products” “@RELATIVE” because all the members in these dimensions have data associated with them. The second “FIX” statement is used to aggregate the values for remaining sparse dimensions.

After the business rule is written, then it is time to validate the business rule. The business rule can be validated by clicking the icon highlighted in light blue, then by deploying the business rule to the application by clicking the icon highlighted in red.

To execute the business rule, the administrator should navigate to “Tools -> Business Rules.” Here you will see all the business rules created for this application. Click on the launch button (highlighted in green) for the business rule and this will execute the calculation that is in the rule.

These before and after screenshots demonstrate what the solution looks like when the business rule runs:

BEFORE (Actuals-Final)

AFTER (Forecast-Working)

In addition, a business rule can also be attached to data entry forms to perform calculations on the dataset entered by planners. This second method of executing business rules will be covered in a future article.

 

 

Share
This post was posted in Technical and tagged Business Rules , Hyperion , Oracle , Oracle Hyperion Planning .
© Performance Architects, Inc. and Performance Architects Blog, 2006 - present. Unauthorized use and/or duplication of this material without express and written permission from this blog's author and/or owner is strictly prohibited. Excerpts and links may be used, provided that full and clear credit is given to Performance Architects, Inc. and Performance Architects Blog with appropriate and specific direction to the original content.

Leave a Reply

Your email address will not be published. Required fields are marked *