Page 1 of 1

Deliberately leaving calculated values unfed

Posted: Fri Aug 06, 2010 1:44 am
by harrytm1
Hi all,

I read in this forum that it is not necessary to feed all calculations. Here are my views and please correct me if i'm wrong. Many thanks!

1) Feeders do not have to be written if the calculated numeric values do not need to be consolidated in a roll-up.
2) One example is a rule that calculates Gross Profit % and it applies to both N and C elements e.g. ['GP%'] = ['GP'] \['Sales Amt'];
3) Since the rule applies in C-element, it does not required TM1's consolidation algorithm, hence no feeder is necessary.
4) If the unfed value is used in another rule, and the values calculated by this rule have to be consolidated, then it needs to be fed.
5) There is generally no need to feed string elements that are calculated.
6) By leaving calculated values unfed deliberately where possible, memory usage will be reduced.

Look forward to your comments!

Re: Deliberately leaving calculated values unfed

Posted: Fri Aug 06, 2010 2:57 am
by Martin Ryan
I'd agree with that (but probably wouldn't recommend it). However you'll still have the problem of a disappearing row/column when you zero suppress the view, regardless of whether you're at N or C level.

Martin

Re: Deliberately leaving calculated values unfed

Posted: Fri Aug 06, 2010 3:08 am
by harrytm1
Martin Ryan wrote:I'd agree with that (but probably wouldn't recommend it). However you'll still have the problem of a disappearing row/column when you zero suppress the view, regardless of whether you're at N or C level.

Martin
Thanks for the reply. Yes, that will be an issue if users are using Cube Viewer. This can be overcome if the suppress zero on column/row is OFF.

Also, if users are mainly using Excel worksheets, then I suppose this will not be a concern.