You're better off tracking sales and volume in teh cube and compute (what
will be a volume weighted) "prijs" (price) if you need it. Otherwise, you
need to use a calculated member using Descendants() to access the leaf data
from the current level. This can be quite time consuming if you have many
dimensions that you need to descend into to get the raw data. By design,
OLAP generally does its computations using values at the current level for
each dimension.

Jim
"Christiaan" <christiaan.vanapeldoorn (AT) astrazeneca (DOT) com> wrote

"Christiaan" <christiaan.vanapeldoorn (AT) astrazeneca (DOT) com> wrote

It's very easy -- do the calculation during the data load into the cube. You
can do in-line SQL calculations to create additional data members which are
calculated as the cube is built and the calculations are then stored as data
in the cube. They are then consolidated in the usual way and there's no hit
on the query performance.