Hello LinusH, thanks for your reply! You are right that that would be a solution but in that case we have 2 cubes which is not very convenient for end users. I agree in principle that it is something that does not belong together maybe, however there is a similar situation which is tipical in cubes - Scenario dimension which holds e.g ACTUAL, PLAN, FORECAST values which are not to be summarized. Another thing, this might happen possibly not only for the whole dimension, maybe just some members are not to be aggregated... Also if this stays in cube as it is, it will happen sooner or later that users will look at summarized results which should not be summarized. It would be good to aviod that. It is a rather specific situation, but Essbase does it with no problems. Is there really no such option? Nevertheless, I'll think about 2 cubes with shared dimensions and each having it's specific dimension part (of the one where the difference is).
... View more