COGNOiSe.com - The IBM Cognos Community

Planning & Consolidation => COGNOS Planning => Topic started by: scotth750 on 16 Oct 2008 04:20:31 PM

Title: Parent Node in a cube
Post by: scotth750 on 16 Oct 2008 04:20:31 PM
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.
Title: Re: Parent Node in a cube
Post by: noraneko on 17 Oct 2008 07:11:31 AM
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.

Title: Re: Parent Node in a cube
Post by: scotth750 on 17 Oct 2008 08:32:41 AM
thanks a lot mate. I will try this one out..
Title: Re: Parent Node in a cube
Post by: scotth750 on 17 Oct 2008 04:26:33 PM
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
Title: Re: Parent Node in a cube
Post by: sascha on 20 Oct 2008 03:56:43 AM
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.