TM1 Forum

I found nothing about the following in a thread or the internet at all
I'm facing the following issue with cross-cube-feeders in TM1 10.2.2 (FP3)

I've one Cube with detailed data on a monthly base (called "Cube A") - dimensions:
- PlanDatenartUmsatz
- PlanVersion
- PlanNiederlassung
- PlanKostenstelle
- PlanPeriode (monthly Base, aggregating to quarters)
- Kennzahlen_Personalplanung
- inPersonalaufwand_m

A 2nd cube is on quarterly period (Cube B) - dimensions:
- PlanDatenartUmsatz
- PlanVersion
- PlanNiederlassung
- PlanPeriodeUmsatz (quarterly base)
- Kennzahlen_Kostenplanung
- inKostenplanung_m

The data in cube B is retrieved by the following rule (the formula is in a IF-condition depending on an attribute of dimension 'Kennzahlen_Kostenplanung' - running well):
IF(ATTRS('Kennzahlen_Kostenplanung',!Kennzahlen_Kostenplanung,'Referenz') @='Cube A',
DB('Cube A','Import',!PlanVersion,!PlanNiederlassung,'Alle',!PlanPeriodeUmsatz, !Kennzahlen_Kostenplanung,'Wert')
...

The Feeder in Cube A is als follows:
['Import','Wert'] => DB(IF(ATTRS('Kennzahlen_Kostenplanung',!Kennzahlen_Personalplanung,'Referenz') @='Cube A','Cube B',''),'Eingabe',!PlanVersion,!PlanNiederlassung,!PlanPeriode,!Kennzahlen_Personalplanung,'Wert');

The Feeder is not working

1. I removed the condition
['Import','Wert'] => DB('Cube B','Eingabe',!PlanVersion,!PlanNiederlassung,!PlanPeriode,!Kennzahlen_Personalplanung,'Wert');

The Feeder is not working

2. I took a specific Quarter:
['Import','Wert','Q3.2015'] => DB('Cube B','Eingabe',!PlanVersion,!PlanNiederlassung,!PlanPeriode,!Kennzahlen_Personalplanung,'Wert');

The Feeder is not working

3. I took the identically Target Quarter:
['Import','Wert','Q3.2015'] => DB('Cube B','Eingabe',!PlanVersion,!PlanNiederlassung,'Q3.2015',!Kennzahlen_Personalplanung,'Wert');

Now the Feeder is working!

Am I fool or is there a serious bug in the cross cube feeders?
Why is it no longer possible to feed from a c-element to an identically named n-element?
I'm running crazy...

Additional info:
'Import" and 'Eingabe' are elements of dimension "PlanDatenartUmsatz"
'Wert' is an element in "inKostenplanung_m" and "inPersonalaufwand_m"

Parameters:
PersistantFeeder=T
ParallelInteraction=T
AllowSeparateNandCRules=T

any help is appreciated

hju

There is no bug. Just the feeder is incorrect. Feeders are from DATA. In TM1 data is only at LEAF. Always remember this and it will save you frustration.

You can't feed to !PlanPeriode because the LEAF periods don't exist in the summary cube as the N elements in PlanPeriodeUmsatz are different. The Quarter must be fed. If you don't already have one create attribute in period dimension for quarter and the feeder would be
DB('Cube B','Eingabe',!PlanVersion,!PlanNiederlassung,AttrS('PlanPeriode',!PlanPeriode,'Quartal'),!Kennzahlen_Personalplanung,'Wert')

hju wrote:Am I fool or is there a serious bug in the cross cube feeders?
Why is it no longer possible to feed from a c-element to an identically named n-element?
I'm running crazy...

Best no one answers that question directly. Suffice to say there is no bug and you have never been able to feed from a C element to a same named N element. Feeders simply don't work that way and never have. The feeder always comes from a LEAF cell. If there is dimension asymmetry to the target cube then you have to lookup the target element via an attribute or lookup cube. This is how it is.

Also I wouldn't use conditional feeder. There is no point since the rule in the target checks the attribute and sets cell to zero. The target cube is not big so any performance hit of overfeeding would be negligible. Better to not use conditional feeders unless absolutely necessary.

Best no one answers that question directly

Thank you very much.

Maybe I'm fool...
But Feeder like
['Import','Wert','4122000','Q3.2015'] => DB('inKostenplanung','Eingabe',!PlanVersion,!PlanNiederlassung,'Q3.2015','4122000','Wert');
Q3.2015 (is the consolidation of the leaf elements 07.2015, 08.2015 and 09.2015)

or even
['Import','Wert','2015'] => DB('inKostenplanung','Eingabe',!PlanVersion,!PlanNiederlassung,'2015',!Kennzahlen_Personalplanung,'Wert');
from consolidation '2015' are running well!

I'm, quiete shure I was able to feed from consolidated elements as mentioned in my initial post in ealier versions...

Nevertheless I'm changing my Feeder and try out your approach .

hju

What you do here is you feed from all leaves within 2015 in the source cube to all leaves of 2015 in the target cube. So for example if Q3.2015 is a leaf in the source, Q3 will feed all months in the target cube if you have months in the target cube.
Or the way around, if months are leaves in the feeder source cube, then each month will feed all 4 Qs in the target cube if Qs are leaves in the target cube
This is an overfeeding, and yes it works but is logically incorrect and results in unnecessary overfeeding

Or the way around, if months are leaves in the feeder source cube, then each month will feed all 4 Qs in the target cube if Qs are leaves in the target cube
This is an overfeeding, and yes it works but is logically incorrect and results in unnecessary overfeeding

There is indeed an overfeeding. The example was just to illustrate my question.

But I think I got the point:
Feeding
[... 'Wert' , 'Q3.2015'] => DB(...,'Q3.2015','Wert') (the target 'Q3.2015' is a leaf-element)
will trigger all children of Q3.2015 in the source-cube to feed Q3.2015 in the target cube

using
[... 'Wert'] => DB(... !PlanPeriode,'Wert')
completely ignores 'Q3.2015' in source-cube because it is at c-level and there is no feeding from its children...

never observed this before, but thanks for pointing out this.

hju

completely ignores 'Q3.2015' in source-cube because it is at c-level and there is no feeding from its children...

actually in this case you feed from all months and not only from the months of Q3 2015, and so "and there is no feeding from its children..." this is not fully true