Specify the implementation type

Rule implementation specifies how Planning Business Modeler implements a rule. By implication, this includes how Planning Business Modeler translates the rule into code, and how the rule interacts with underlying data. The options available for implementation depend on the type of rule that you select. For information about types of rules, see About business rules.

We encourage you to write rules in PerformancePoint Expression Language (PEL). When a rule is written in PEL, you can compare the performance or results of the same rule under different implementations. For example, you might first use SQL implementation, and then MdxQuery implementation. Alternatively, you can code a rule in native SQL, native MDX Script, or native MDX Query. Planning Business Modeler passes the code with a native implementation type, such as NativeSql or NativeMdxQuery, to the underlying system without a change.

Planning Business Modeler can process business rules with any one of the available implementation options. During processing, the system creates an intermediate form of the business rule, based on the implementation type. Then, by using an intelligent subsystem that recognizes the rule type and implementation, Planning Server passes the intermediate form of the rule to its destination component so that it can be run.

In This Section

SQL implementation

The destination subsystem generates a SQL stored procedure from the rule. The rule is deployed directly over the underlying data tables.

MdxQuery implementation

The destination subsystem generates cube queries in MDX language that are run at rule runtime. The rule is deployed to the underlying cube.

MdxScript implementation

The destination subsystem generates cube script in the MDX script language from the rule.

This implementation is limited to Definition rules.

Specialized implementations

Rule will be generated to an intermediate form that is best suited for the destination component. The following rule types have specialized implementations:

Native code implementation

Planning Business Modeler supports three native code implementations.

  • NativeSql - Rule must be written in SQL code. It will be passed to the underlying data tables.

  • NativeMDXQuery - Rule must be written in MDX Query code. It will be passed to the underlying data tables.

  • NativeMDXScript - Rule must be written as MDX Script code. It will be passed to the underlying cube.

Related Sections