Home > Working with Planning Projects > Building an Application > Building Application Models > Building A Cube Model > Measure Settings > Cross Referencing Measures > Cross Referencing Within The Same Model
Cross Referencing Within The Same Model
Last Updated 8/26/2008 12:59 PM
To access a measure in another section, Cascade Planning will use the dimensions in ascending order, so for example, Version would be first, followed by Product, followed by Country, followed by Measure. Therefore, if we know the section we want to access (in other words, we know the member names, we can cross reference them in the measure logic).
The format for this would be:
'dim_1 member'. 'dim_2 member'. 'dim_3 member'. 'measure_name'
As an example, if we wanted to reference the Measure 'Revenue' for 'Total Products' and 'All Countries', we could do this with the following measure logic:-
'Total Products'.'All Countries'.'Revenue'
Note that we do not need to specify the Version dimension (in our example this is internally assigned as the first dimension), because we are referring to the same Version. You can drop any dimension which occurs to the left of the reference provided you want to accept the current combination (note if names are the same). To refer to a member from a different Version, you would need to specifically reference that member of Version.
As an additional example, let's suggest that you wanted to refer to 'All Countries' for the current product we are calculating, we could simply drop off the reference to 'Total Products' as follows:-
'All Countries'.'Revenue'
In this example, because we have not specified the Product, it will match product for the current Product section, but will retrieve the 'All Countries' member. We could have actually have specified the same expression as follows:
dimension2.'All Countries'.'Revenue'
The variable dimension 2 will hold the value of the second dimension member name for the section currently being calculated, and in our case, the second dimension is Product.
So as each product is calculated, the variable dimension2 will hold the name for the Product currently being calculated.
However it is not necessary for us to specify dimension2, since we can discard any dimensions to the left of the reference if we are referring to the current member for that dimension.
This becomes more problematic however if we wish to reference the current Country for a specific Product. In such a case, we want to use the value of dimension3 (the Country dimension) for the section we are calculating. So in this case we need to specify dimension3 in the reference since it is not to the left of the reference (as Product comes before it in the order).
'Total Products'.dimension3.'Revenue'
The above example would retrieve the 'Revenue' value for 'Total Products' for the Product dimension member currently being calculated.
See also
| 
Page URL: