A problem that affects the ordering of OLAP data was introduced in SAS
9.1.3 Service Pack 2 (9.1.3 SP2). When calculated members are referenced
in an OLAP report, certain MDX ordering functions may return incorrect
data.

Some of the MDX functions that could display this behavior include the
ORDER function with parameters BASC or BDESC, TOPCOUNT, TOPPERCENT,
BOTTOMPERCENT, and BOTTOMSUM. For example, the syntax for the ORDER
function is:

   Order(<Set>, <Numeric Expression>[, ASC | DESC | BASC | BDESC])

The problem occurs with the ORDER function when there is one measure in
the set and a different measure in the numeric expression. Here is a
query that shows the problem:

   with
     member measures.[&1sales_N] as '[Measures].[SALES_N]'

   select
     ORDER (CROSSJOIN({[CARS].[All CARS].[Chrysler],
            [CARS].[All CARS].[Ford]},
            CROSSJOIN({[DEALERS].[All DEALERS].[Finch]},
            {[Measures].[&1SALES_N]} )),[Measures].[SALES_n], BASC)
     on 0 from mddbcars

Notice that the query is using the calculated measure,
[Measures].[&1SALES_N] in the set and the standard measure,
[Measures].[SALES_n] in the numeric expression.


A fix for SAS 9.1.3 (9.1 TS1M3) for this issue is available at:

http://www.sas.com/techsup/download/hotfix/e9_sbcs_prod_list.html#014756

For customers running SAS with Asian Language Support (DBCS), this
fix should be downloaded from:

http://www.sas.com/techsup/download/hotfix/e9_dbcs_prod_list.html#014756

Operating System and Release Information

A fix for SAS 9.1.3 (9.1 TS1M3) for this issue is available at:

A fix for SAS 9.1.3 (9.1 TS1M3) with Asian Language Support (DBCS) for this issue is available at :