Difference in writing feeders
-
- Regular Participant
- Posts: 152
- Joined: Sat May 25, 2013 10:32 am
- OLAP Product: TM1
- Version: 9.5.2; 10.2.2
- Excel Version: 2007
Difference in writing feeders
Hi All,
Feeder1: [A] => [B,'Dollar'];
Feeder2: [A,'Dollar']=>;
What is the difference between both the feeders? Does it impact memory?
Which is the most preferred way to be followed?
Regards,
Deepak Jain
Feeder1: [A] => [B,'Dollar'];
Feeder2: [A,'Dollar']=>;
What is the difference between both the feeders? Does it impact memory?
Which is the most preferred way to be followed?
Regards,
Deepak Jain
-
- Community Contributor
- Posts: 128
- Joined: Wed Oct 14, 2009 7:46 am
- OLAP Product: TM1
- Version: 9.4
- Excel Version: 11
- Location: London
Re: Difference in writing feeders
Hi Deepak,
Let's call your dimension with values 'A' and 'B' your measures dimension, and the one with 'Dollar' your currency dimension.
Feeder1 is explicit as to which area it is feeding (right-hand side of feeder). This means that if you have values in any currency for measure 'A', this will feed ['B', 'Dollar'].
Feeder2 is explicit on the currency dimension from where you are feeding from (left-hand side of feeder). Because you are only feeding from ['A', 'Dollar'], and not the other currencies, you don't need to be explicit on the right-hand side of the feeder, but it is effectively the same as:
['A', 'Dollar']=>['B', 'Dollar'];
I am assuming your rule is performing a currency calculation based on a dollar value being present in the cube. If this is the case you will want to feed from 'Dollar' to all other currencies. There are 2 ways in which you can do this. Either feed individually to each currency, or write 1 feeder which feeds to a consolidation ('All Currencies') which has the calculated currencies as children. Feeding to a consolidation is the same as feeding each n-level node in that consolidation individually.
There's a good intro to feeders in the IBM documentation and here. Plus there are countless threads in this forum which will help you to understand feeders.
Let's call your dimension with values 'A' and 'B' your measures dimension, and the one with 'Dollar' your currency dimension.
Feeder1 is explicit as to which area it is feeding (right-hand side of feeder). This means that if you have values in any currency for measure 'A', this will feed ['B', 'Dollar'].
Feeder2 is explicit on the currency dimension from where you are feeding from (left-hand side of feeder). Because you are only feeding from ['A', 'Dollar'], and not the other currencies, you don't need to be explicit on the right-hand side of the feeder, but it is effectively the same as:
['A', 'Dollar']=>['B', 'Dollar'];
I am assuming your rule is performing a currency calculation based on a dollar value being present in the cube. If this is the case you will want to feed from 'Dollar' to all other currencies. There are 2 ways in which you can do this. Either feed individually to each currency, or write 1 feeder which feeds to a consolidation ('All Currencies') which has the calculated currencies as children. Feeding to a consolidation is the same as feeding each n-level node in that consolidation individually.
There's a good intro to feeders in the IBM documentation and here. Plus there are countless threads in this forum which will help you to understand feeders.
-
- Regular Participant
- Posts: 152
- Joined: Sat May 25, 2013 10:32 am
- OLAP Product: TM1
- Version: 9.5.2; 10.2.2
- Excel Version: 2007
Re: Difference in writing feeders
Hi Dan,
Good description from your end, thanks for that.
Can you please let me know about how the impact will be on memory of feeders?
Feeder1: [A] => [B,'Dollar'];
Feeder2: [A,'Dollar']=>;
Will the memory consumed by feeders will be same in both the cases?
Regards,
Deepak Jain
Good description from your end, thanks for that.
Can you please let me know about how the impact will be on memory of feeders?
Feeder1: [A] => [B,'Dollar'];
Feeder2: [A,'Dollar']=>;
Will the memory consumed by feeders will be same in both the cases?
Regards,
Deepak Jain
- Michel Zijlema
- Site Admin
- Posts: 712
- Joined: Wed May 14, 2008 5:22 am
- OLAP Product: TM1, PALO
- Version: both 2.5 and higher
- Excel Version: 2003-2007-2010
- Location: Netherlands
- Contact:
Re: Difference in writing feeders
deepakjain2020 wrote:Hi Dan,
Good description from your end, thanks for that.
Can you please let me know about how the impact will be on memory of feeders?
Feeder1: [A] => [B,'Dollar'];
Feeder2: [A,'Dollar']=>;
Will the memory consumed by feeders will be same in both the cases?
Regards,
Deepak Jain
Hi,
I don't expect there will be a difference in memory used for the feeders between the two, as they're both feeding the exact same area.
Of course if you have a non-zero value on f.i. ['A', 'Euro'] and no value on ['A', 'Dollar'], then Feeder1 will trigger and place a feeder, while Feeder2 won't. In that case there is a difference in memory consumption. Feeder1 potential leads to more feeder triggering (overhead) than Feeder2, so Feeder2 is the more efficient one.
But in the end it depends on what you need - if the rule you're feeding is calculating Dollars based on other currency values, it could be that Feeder1 is the only valid one...
Michel
-
- Posts: 63
- Joined: Wed Sep 14, 2011 3:10 am
- OLAP Product: TM1
- Version: PA 2.0
- Excel Version: Office 365
Re: Difference in writing feeders
Hi there,
I'm facing a similar situation here. Assuming below is my rule & feeders, any idea which way of putting the feeders would be more efficient ?
A=B+C;
D=A+E;
FEEDERS;
B=>A;
C=>A;
A=>D;
E=>D;
OR
B=>A,D;
C=>A,D;
E=>D;
I'm facing a similar situation here. Assuming below is my rule & feeders, any idea which way of putting the feeders would be more efficient ?
A=B+C;
D=A+E;
FEEDERS;
B=>A;
C=>A;
A=>D;
E=>D;
OR
B=>A,D;
C=>A,D;
E=>D;
-
- MVP
- Posts: 3223
- Joined: Mon Dec 29, 2008 6:26 pm
- OLAP Product: TM1, Jedox
- Version: PAL 2.1.5
- Excel Version: Microsoft 365
- Location: Brussels, Belgium
- Contact:
Re: Difference in writing feeders
beek
I would try to solve this with consolidation structures, since you have sums...
If not, set 2 seems more appropriate. Try to feed from values instead of feeding from cells fed by other cells.
I would try to solve this with consolidation structures, since you have sums...
If not, set 2 seems more appropriate. Try to feed from values instead of feeding from cells fed by other cells.
Best regards,
Wim Gielis
IBM Champion 2024-2025
Excel Most Valuable Professional, 2011-2014
https://www.wimgielis.com ==> 121 TM1 articles and a lot of custom code
Newest blog article: Deleting elements quickly
Wim Gielis
IBM Champion 2024-2025
Excel Most Valuable Professional, 2011-2014
https://www.wimgielis.com ==> 121 TM1 articles and a lot of custom code
Newest blog article: Deleting elements quickly
-
- Posts: 63
- Joined: Wed Sep 14, 2011 3:10 am
- OLAP Product: TM1
- Version: PA 2.0
- Excel Version: Office 365
Re: Difference in writing feeders
Hi Wim Gielis,
Thanks for your reply.
Thanks for your reply.
Refering to the above, can I assume you are refering to the 1st set of FEEDERS?beek wrote:I would try to solve this with consolidation structures, since you have sums...
-
- Posts: 33
- Joined: Mon Sep 23, 2013 3:24 pm
- OLAP Product: TM1
- Version: 10.2
- Excel Version: Excel 2010
Re: Difference in writing feeders
beek,
Wim Gielis was suggesting that you re-do the structure of your measures dimension so that it looks somewhat like this
D
|- E
|- A
|- B
|- C
Assuming you give each child element a weight of 1, this structure takes care of the calculations without the requirement for feeding.
If you have simple addition / subtraction to do, using weights and a hierarchy in is cheaper (memory consumption-wise) and faster (performance-wise) than rules and feeders.
~Java_to_tm1
Wim Gielis was suggesting that you re-do the structure of your measures dimension so that it looks somewhat like this
D
|- E
|- A
|- B
|- C
Assuming you give each child element a weight of 1, this structure takes care of the calculations without the requirement for feeding.
If you have simple addition / subtraction to do, using weights and a hierarchy in is cheaper (memory consumption-wise) and faster (performance-wise) than rules and feeders.
~Java_to_tm1
- Attachments
-
- Screenshot with sample hierarchy for the measure dim
- Measure dim Hierarchy.png (3.84 KiB) Viewed 7399 times
The Java_to_TM1 Convert
TM1 Version 10.1, 10.2, Cognos Insight 10.1, 10.2
Local: Windows 7 Professional, Excel 2007
Server: Windows Server 2008 64-bit
p.s. I have a healthy disregard for Performance Muddler.
TM1 Version 10.1, 10.2, Cognos Insight 10.1, 10.2
Local: Windows 7 Professional, Excel 2007
Server: Windows Server 2008 64-bit
p.s. I have a healthy disregard for Performance Muddler.
-
- Posts: 63
- Joined: Wed Sep 14, 2011 3:10 am
- OLAP Product: TM1
- Version: PA 2.0
- Excel Version: Office 365
Re: Difference in writing feeders
I see. Got it. Thank you Wim & Java 

-
- MVP
- Posts: 3223
- Joined: Mon Dec 29, 2008 6:26 pm
- OLAP Product: TM1, Jedox
- Version: PAL 2.1.5
- Excel Version: Microsoft 365
- Location: Brussels, Belgium
- Contact:
Re: Difference in writing feeders
That's what I meant, java_to_tm1 

Best regards,
Wim Gielis
IBM Champion 2024-2025
Excel Most Valuable Professional, 2011-2014
https://www.wimgielis.com ==> 121 TM1 articles and a lot of custom code
Newest blog article: Deleting elements quickly
Wim Gielis
IBM Champion 2024-2025
Excel Most Valuable Professional, 2011-2014
https://www.wimgielis.com ==> 121 TM1 articles and a lot of custom code
Newest blog article: Deleting elements quickly