Solve Order Property

The concept of solve order applies to query execution. When a cell is evaluated in a multidimensional query, the order in which the calculations should be resolved may be ambiguous. To remove ambiguity, you can use the solve order property to specify the required calculation priority.

Note:

It is good practice to specify the solve order for each member by setting the solve order property at the member level or at the dimension level. Members without formulas that do not have a specified solve order inherit the solve order of their dimension. Members with formulas that do not have a specified solve order have a solve order of zero.

  To specify the solve order for a member or a dimension, use a tool:

Tool

Topic

Location

Administration Services

Specifying the Calculation Order for Members and Dimensions in Aggregate Storage Databases

Oracle Essbase Administration Services Online Help

MaxL

solve_order parameter in the With section of an MDX query

Oracle Essbase Technical Reference (see MDX, Grammar Rules, With Specification)

The value of the solve order property determines the priority with which Essbase calculates the formulas. The formulas on the members that have a specified solve order are calculated in order from the lowest solve order to the highest. (See Example Using the Solve Order Property). You can specify a solve order between 0 and 127. The default is 0.

You can specify the solve order at the member level or at the dimension level. Essbase uses the following information to define calculation precedence:

  1. Member solve order

  2. Dimension solve order (members without formulas for which you do not specify a member solve order inherit the solve order of their dimension. Members with formulas for which you do not specify a member solve order have a solve order of zero.)

    If multiple members have the same solve order, the members are evaluated in the reverse order in which their dimensions occur in the database outline. The member that occurs later in the outline takes precedence.

    The tie situation calculation order is different for calculated members defined in an MDX query for block storage databases. See the Oracle Essbase Technical Reference.

    Note:

    When a member formula is dependant on the value of another member, the member with the formula must have a higher solve order than the member or members on which it depends. For example, in the ASOsamp.Sample database outline in Figure 167, ASOsamp.Sample Database Showing the Measures, Years, and Time Dimensions, Avg Units/Transaction depends on the value of Units and of Transactions. Avg Units/Transaction must have a higher solve order than Units and Transactions.