Microsoft KB Archive/942556

= When to use different implementation types for a business rule in Planning Business Modeler in PerformancePoint Server 2007 =

Article ID: 942556

Article Last Modified on 10/5/2007

-

APPLIES TO


 * Microsoft Office PerformancePoint Server 2007, 32 Bit Edition
 * Microsoft Office PerformancePoint Server 2007, 64 Bit Edition

-



INTRODUCTION
When you create a business rule in PerformancePoint Planning Business Modeler in Microsoft Office PerformancePoint Server 2007, you must specify an implementation type. The implementation types are SQL implementation and Multidimensional Expression (MDX) implementation. MDX implementation contains MDXQuery implementation and MDXScript implementation.

This article describes when to use each of these implementation types.



Scenario 1
In a business rule, you do not use any value that is calculated by other definition rules in the model cube. In other words, a business rule that is created by using SQL implementation can only handle fact data that is in the underlying relational database.

For example, assume that you want to copy a value that represents the net profit for a member from one model to another model. The value is already calculated and stored as fact data in the underlying relational database. In this case, you use SQL implementation to create a business rule.

However, if the value is calculated by a definition rule, the business rule will generate incorrect results if you create a business rule by using SQL implementation. For example, the value that represents the net profit is calculated by using two other values in the following formula:

Net Profit = Net Income - Net Expenses

Scenario 2
Assume that you want to populate data into the leaf members for a specific slice. You populate the data based on the value of the leaf members for a different slice.

For example, you want to populate the forecast number for a leaf member for all products. The forecast number is calculated based on the actual value of the leaf member for a different slice. The different slice represents the same time last year. In this situation, you create a business rule by using SQL implementation.

Scenario 3
Assume that you want to create a rule that writes data to a large scope. The scope contains more than 4,294,967,296 member cells. In this scenario, you have to use SQL implementation to create the business rule.

Business rules that are created by using MDX implementation can only write data to less than 4,294,967,296 member cells.

Scenario 1
In a business rule, you use values that are calculated by other definition rules in the model cube.

For example, assume that you want to copy a value that represents the net profit for a member from one model to another model. In a definition rule, the value is calculated by using two other values in the following formula:

Net Profit = Net Income - Net Expenses

In this scenario, create a business rule by using the MDX implementation. If you create a business rule by using SQL implementation, the business rule will generate incorrect results.

Scenario 2
Assume that you want to populate data into the leaf members for a specific slice. You populate the data based on the value of the members that are not at the leaf level for a different slice.

For example, you want to evenly populate data that represents the budgeted cost to all leaf members for a slice that represents the current year. The data is calculated based on the following requirements:
 * The data is calculated based on the value of the parent members of the leaf members at a monthly time granularity.
 * The parent members of the leaf members are for a different slice that represents last year.

In this scenario, you create a business rule by using MDX implementation.

Keywords: kbhowto kbinfo kbexpertiseadvanced KB942556

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.