TM1 Forum

I have a cube (employee by period) that contains data at a leaf level for product lines and market segments for employees. I need to move the totals at the consolidtions point to the Expense plan cube. In the formulas I can get the proper amounts to come over, but can't get them to feed correctly.

I have tried changing the N: to a C: or leaving it out in the rule and just can't get it to work.

I'm doing a similar move with the product line by moving just the rollup points over to the Expense cube,.

(In a previous version of my system the expense cube had the same market segment and product line dimensions and it fed fine. I'm running into trouble trying to only bring over the rollup levels)

Thanks,

Hi,

you're problem is unlikely to be on the rule side if the numbers are coming through, but not feeding properly.

Feeders are only ever evaluated at N level, so if you are feeding from a detailed dimension to a summarized dimension, you will need to feed to the parent of the source dimension to get the match needed for the feeder to be created.


Source Cube dimension:

Total
|__Element A
| |_Child 1
| |
| |_Child 2
|
|__Element B
| |_Child 3
| |
| |_Child 4



Target Cube Dimension:

Total
|__Element A
|
|
|
|
|__Element B


For the above situation, your rule in the Target cube would read:

['Value'] = N: DB('Source Cube', !Target Dimension, 'Value');

And the feeder in the Source cube:

['Value'] => DB('Target Cube', ELPAR('Target Dimension', !Target Dimension, 1), 'Value');


This will create the feeding relationship from the more detailed N level source elements to their Parent level equivalents in the target dimension.

so in your case, the feeder should read:

['Headcount'] => DB('Expense Plan', '2013 Working Budget', 'input', !Year, !Entity-Dept, 'Base Compensation', !Product Line_S, ELPAR('Market Segment', !Market Segment, 1), '0000', '1', 'Value', !Period), .............

Assuming you only have one hierarchy in the Market Segment dimension, this would work. You may want to consider setting up the parent of Market Segment as an attribrute though as using ELPARs are prone to breaking if multiple hierarchies are present and some reindexes the dimension.

If the numbers you're pulling through are values, then keep the N: in the rule. If they're ratios, then you can leave the N: out. I don't think it'll work if you use C: as it'll miss off the N level in the target. ( The N: C: apply to the cells in the target cube, not the source cube)

Excellent. I have the same situation with the product line, but will use the same method. Thanks,

It works great. Thanks for the help.