Hyperion Business Rule Overview concepts part

Hyperion Business Rule Overview

In budgeting, the business logic requirement is not easy to achieve through the Planning outline design. We employ Business rules to implement complicated calculations. We are not going to code in any complicated programming language for a Business rule; rather, it will be all graphical in nature. Graphical interfaces ease Business rule creation, even for users with a business (non-technical) background. Nevertheless, Business rules can also be created by coding in all the calculations. In fact, the graphical interface also generates code behind the scenes and the user developing a rule using the graphical interface can switch to the source section for viewing the generated code. Business rules make use of the predefined functions and formulas of Essbase. Business rules are not created within the Planning web, unlike the outline structure or member formulas. We create Business rules through the EAS console. Nevertheless, we can create rules using the Calculation manager (which is a part of EPM architecture).

Some of the Advantages of Business rule are:

Easy to Create

1. Macros simplify the creation of business rules and sequences, and save business rule designers time by enabling them to reuse pieces of business rules in other business rules or macros.
2. Variables of the saved selection type can be used at run time and during design time to make business rules easier to design.
3. Predefined and reusable formulas that define cost and revenue calculations save business rule designers time during the design process. The following formulas are provided:

• Pro-Rata Ratio
• Units-Rates
• Variable
• Custom

The graphical depiction of components, formulas, and processes makes it easy to construct business rules in a multidimensional application.

Easy to Use

1. Business rules can be launched by business users from within Oracle Essbase Administration Services, the Business Rules Web Launcher, the Business Rules Command Line Launcher, and the Oracle Hyperion Planning, Fusion Edition Web Client.
2. Business rules can be launched in all Essbase server environments.
3. Business rules can be stored and run on a server across a wide area network (WAN).
4. Business rules with run time prompts ensure valid inputs from budget prepares.
5. Entry of run time prompt values during launching makes a single, centrally created business rule reusable by several users.

Easy to Maintain

1. The Business Rules architecture supports enterprise-wide maintenance and methods of use that can be successfully managed and deployed to multiple business users.
2. Business rules, sequences, macros, variables, and projects can be stored in any of these repositories: Microsoft Access, Microsoft SQL Server, Oracle, or DB2 for shared, enterprise wide access.
3. Use of a central repository makes administration and maintenance of business rules easy, because the repository stores information for applications in one database.
4. The logical organization of business rules, sequences, macros, and variables into projects makes them easier to find and maintain.

There are 4 main options in Hyperion Business Rule. They are

1. Rules – A rule typically runs a specific calculation/allocation on a single Essbase Database. It can be extended quite extensively to include advanced calculation scripts.
2. Sequence – A sequence basically helps in sequencing a list of rules based on business requirements. It basically provides an order to the Rules execution.
3. Macros – Macros are like mini rules which can be reused across multiple rules.
4. Global Variables – Global Variables are nothing but a set of variables that provide a global context to the variable values.

Since Hyperion Business rule comes along with EAS, its security is derived from Shared Services. Each rule/sequence execution/validation by a user can be controlled through the shared services console. HBR is relevant only to BSO cubes as ASO cubes do not support calculation scripts.