If you are unable to create a new account, please email support@bspsoftware.com

 

News:

MetaManager - Administrative Tools for IBM Cognos
Pricing starting at $2,100
Download Now    Learn More

Main Menu

Parent Node in a cube

Started by scotth750, 16 Oct 2008 04:20:31 PM

Previous topic - Next topic

scotth750

Hello there,

I am having a big issue with a parent node in one of my budget cubes. In the elist node ( the detail department level), all the facts Forecast, Budget, Variance, % of sales, actuals etc. looks good. One level up on the elist is Parent 1..

Parent 1 which is a location level the data looks good as well.

Parent 2 which is region level, most of the data looks good except for the % of sales. Here the % of sales instead of doing the calculation of a percentage is summing up the % of sales of all the items in the Parent 1 node.

The dimensions are accounts, time period, and department elist.

Please let me know if you can throw any light on this problem.

noraneko

Review always see all summed data.
You have to w.average this % positions.

I usually add additional position in d list with calculations, and make all % positions w. Average to this. Than publish, hide this position from all elist users, send for this position number 1 for all elist items â€" and the % positions will appear correct for reviewer.


scotth750

thanks a lot mate. I will try this one out..

scotth750

Hi there,

The w.average did not really work. Is there any possibility for me to modify the way the calculations look on Parent 1 or Parent 2..In this way I can go to the hierarchy where the percentages are getting added and modify it for that level..

Thank You

sascha

It' really strange that the behaviour is correct on L1 but not on L2. I agree with noraneko to use weighted averaged. In addition you can check the order of your dLists in the Cube. eLists should be placed first in the category-2-lists. Not nothing else help you can try use a different priority within the calculation (in the dLists element) even if a standard percentage calc should not require that.