Feeders not working when new time periods added

[Tony]

We’re doing a two year forecast and I just recently added the 2015 month/quarters time periods. I’m having trouble with the feeders and it’s not doing the aggregation in the calculation cube for the newly added time periods.

I have two headcount cubes, one is the input and the other is the calculation. In the calculation cube the individual employees’ salary, taxes, bonuses get calculated for 2015 but the total employee line did not. This total is the one that is linked to the salary account in the opex cube. It looks odd that you’ll see that there’s total until Dec/14 then zero afterwards.

I’ve run CubeProcessFeeders, reloaded the rules to refire the feeders, checked the cube rules and checked dimension attributes but nothing seemed to be working. I’m running out of ideas and I’m getting very frustrated.

Thanks in advance for your input.
TV

[EvgenyT]

Hello there,

Can you please post the rules / feeders to review

Thank you

Evgeny

[Wim Gielis]

Hi

Did you investigate Check feeders (at the consolidated level) and Trace feeders (at the lowest level) ?

[Tony]

I am attaching the rules file copied paste in word for both the headcount input (i_hcinput) and calculation (c_hccalc). But I also want to point out that it's also happening in the other cubes that are doing calculation like the depreciation of asset where the expense stops on Dec 14 and nothing afterwards,

Thanks
Tony

[David Usherwood]

Looks like these feeders are the ones to follow up.

Code: Select all

HCINPUT
['Annual Salary' ] => ['FeederFlag'];
['Hourly Rate' ] => ['FeederFlag']; (Doubt you need this, BTW)
['FeederFlag' ]  => DB('c_hccalc', !v_generic, 'All Time', !h_hc_list, !h_cost_center, 'FeederFlag');

HCCALC
['FeederFlag' ]  => ['Headcount' ];
(headcount then feeds lots of lines)

However your rules look stranger:

Code: Select all

HCINPUT
['FeederFlag' ] = N: IF((['Annual Salary' ] + ['Hourly Rate' ]) = 0, 0, CONTINUE);
['FeederFlag' ] = N: IF(ATTRS('h_hc_list', !h_hc_list, 'EmployeeType') @= 'New' &
				DB('i_hcinput', !v_generic, !h_hc_list, !h_cost_center, 'Hire Month') @= '', 0, CONTINUE);
['FeederFlag' ] = N: IF(['Quantity'] > 0, ['Quantity'], 1);

Follow through FeederFlag to see whether it is present for the new time periods. When you get it to work, refire the feeders by resaving the rules, first for HCINPUT, then for HCCALC.
But, myself, I would simplify the feeder logic significantly - feed from Annual Salary, then (depending on your time structures) over to HCCALC from years to months.
HTH

[Tony]

The feederflag is present to the employee level (lowest level) in the the new time periods. All the calculations seem to be working but when they get aggregated to the Total Employees that is when everything is blank.

I'm doing some testing by adding an additional feeder by feeding the annual salary directly from the input to the base salary in the calculation just in case there's something wrong with the feederflag. But noting happened either.

I'll look at your suggestion and will focus on the feederflag again.

Thanks

[tomok]

Your feeder logic is a prime example of how "not" to do feeders. You should never feed from a rule-calculated cell (one which itself must be fed) and definitely never have multi-level feeding. Just because your Feeder_Flag cell has a value does not mean it will successfully feed something else. It has to have a value and itself have been fed in order to be able to use it as a feeder for something else. Just looking at the Feeder_Flag value will not tell if it has been fed. You have to trace it to make sure. When you have muti-tiered feeding like this it can be almost impossible to diagnose when a problem occurs. ALWAY feed from an actual value, not a rule calculated value. In your case this would be Annual Salary I think, and do what David suggested.