Analyzing Business Rules

When you analyze a business rule, you run the business rule and capture statistical information such as how long a component took to execute, how many times it was run, and the values of a member intersection before and after the component was run. The amount of time the analysis takes depends on the memory of your system.

Note:

The Analyze feature is not available for Member Range, Member Block, Fixed Loop, or Condition components.

To analyze a business rule:

  1. Open a business rule.
  2. In the Rule Designer, select Actions, and then Analyze.
  3. In the Enter Analysis Criteria dialog box:

    • Enter the number entries to display in the analysis, or select Show All to display entries.

      The number entered here is the number of member intersections to calculate and display. For example, assume you have these dimensions in the application:

      • Year = 12 members

      • Measures = 50, 525 members

      • Product = 450 members

      • Market = 2000 members

      • Scenario = 4 members

      In this example, the number of member intersections to calculate is: 2, 182, 680, 000 (12 x 50,525 x 450 x 2,000 x 4 or Year x Measures x Product x Market x Scenario)

    • For each dimension, select the members to analyze.

      The following options are available to select members:

      • Click Member Selector button to access the Member Selector dialog box.

      • Select a dimension, and then click Select button.

      • Type in the member.

      You can only select one member per dimension.

  4. Click OK to start the analysis.
  5. When the analysis is complete, click a component in the business rule flow chart, and then select the Analysis Information tab.

Tip:

To export the analysis information, right-click in the grid in the Analysis Information tab, and then select Export.

Note:

The analysis may not show the correct begin and end values because of Oracle Essbase optimizations. If the analysis does not show a begin and end value for at least one intersection, the count and the elapsed time might not be correct.