Specialized implementations in Planning Business Modeler

Some rule implementations are highly specialized. A specialized implementation applies only to a single specific rule type. Each rule type that has a specialized implementation requires unique processing. Sometimes, in fact, a highly specialized rule is processed by a unique and dedicated program component. For example, Consolidation rules must be processed by a component called the Consolidation Engine.

The following table shows the rule types that have highly specialized implementation.

Rule Type

Imp lementation







Intercompany Reconciliation

Intercompany Reconciliation





When PerformancePoint Planning Business Modeler encounters one of these specialized rules, it identifies the associated rule type. Based on that rule type, Planning Business Modeler selects the destination component that will process the rule. Next, the Microsoft Office PerformancePoint Expression Language compiler translates the rule into an intermediate result that is customized for the destination component. For example, a Consolidation rule is translated into a form that the Consolidation Engine component can process.

When to consider specialized implementations

When you create a rule that requires specialized implementation, Planning Business Modeler selects the required implementation type by default.

Top of Page

Share Facebook Facebook Twitter Twitter Email Email

Was this information helpful?

Great! Any other feedback?

How can we improve it?

Thank you for your feedback!