TM1 Rules and Feeders

[jcr55]

Question: What is the best way to write Feeders when you want to feed a subset of elements in a dimension?
TM1 Version: 9.5.2 FP2.

The main issue is you cannot put multiple single elements into the right side of a Feeder statement using the { element1, element2, element3 } syntax. That only works on the left side of the feeder.

We have a cube with many dimensions.
Two of them are Scenario and Account.
I want to feed data from 3 scenarios from 1 account to a different account.
In the Scenario dimension, there are 7 N-level elements:
Actuals
Estimate
Estimate Reported
Forecast
Forecast High
Forecast Low
OpPlan

The feeder needs to feed from Forecast, Forecast High, and Forecast Low from on account to another, like Account BS130100 to Account 130100.
There are many accounts to feed and be fed, but for this example, only one account pair is shown.
The scenario data is a 1:1 coorespondence, meaning I really want to feed Forecast to Forecast, Forecast High to itself, etc.

I have written the feeder as 3 separate feeders:
['Forecast', 'BS130100'] => ['Forecast', '130100']
['Forecast High', 'BS130100'] => ['Forecast High', '130100']
['Forecast Low', 'BS130100'] => ['Forecast Low', '130100']

I would like to reduce the number of Feeders by coding:
[{'Forecast', 'Forecast High', 'Forecast Low'}, 'BS130100'] => [{'Forecast', 'Forecast High', 'Forecast Low'}, '130100']
But as stated above, this is not a valid syntax.

So, what really happens if the feeders looks like this, where the target is silent on what Scenarios should be fed to:
[{'Forecast', 'Forecast High', 'Forecast Low'}, 'BS130100'] => ['130100']

Do the amounts in the 3 scenarios on the left get fed to all 7 N-level scenarios?
Do the amounts in the 3 scenarios only get fed to the same 3 scenarios? As 1:1 or 1:3?

Thanks in advance!

[Duncan P]

3 scenarios to the same three scenarios as 1 => 1. If the dimension is not mentioned in the reference on the right it uses the corresponding item from the cell it is feeding from on the left.

[tomok]

So, what really happens if the feeders looks like this, where the target is silent on what Scenarios should be fed to:
[{'Forecast', 'Forecast High', 'Forecast Low'}, 'BS130100'] => ['130100']

Do the amounts in the 3 scenarios on the left get fed to all 7 N-level scenarios?
Do the amounts in the 3 scenarios only get fed to the same 3 scenarios? As 1:1 or 1:3?

When you specify elements on the left and don't specify a specific element on the right then TM1 assumes you are targeting the same elements on the right. So, in your example Forescast feeds Forecast, Forecast High feeds Forecast High, etc. BTW, there is no need to hard code all the accounts. Just set up an attribute to hold the relationship and use that to feed. Of course, by doing this you will need to use the full DB reference on the right but no bother. Something like this:

Code: Select all

[{'Forecast', 'Forecast High', 'Forecast Low'}] => DB(CubeName,!Dim1, !Dim2....ATTRS('Account',!Account,'AccountRef'));

[jcr55]

OK - That answers my question. I am safe indluding all 3 Scenarios on the left side in 1 feeder where nothing is specified for Scenario on the right side.

And I understand the idea for using attributes to define the 'receiving' account instead of hard-coding it in the rule. Allows for changes in the future by just changing the attribute value instead of updating the rule iself.

Thank you!

[tomok]

And I understand the idea for using attributes to define the 'receiving' account instead of hard-coding it in the rule. Allows for changes in the future by just changing the attribute value instead of updating the rule itself.

More importantly, it let's you have one line of code for all accounts instead of one for each account.

[Steve Rowe]

And I understand the idea for using attributes to define the 'receiving' account instead of hard-coding it in the rule. Allows for changes in the future by just changing the attribute value instead of updating the rule iself.

Just in case, feeders are not dynamic in this way, if you change the attribute the feeder won't start firing to a different location without a resave of the rules.

To clear out feeders to the old location you will need a re-start (or unload the cube but not recommended for those new to TM1).