Treatments of an element in Feeders

[dharav]

Hello All

I have a question on the treatment of an element in the Feeders calculations as following:

Suppose, There is a cube called ABC and XYZ

Cube: ABC Cube: XYZ

dim1: ! Regions dim1: ! Regions

dim2: ! Month dim2: ! Years

Dim3: ! Scenario dim3: ! Scenario


The Strucrure of dim2: ! Months

Month (Consolidation)

Week1 (Child)

Week2 (Child)

Week3 (Child)

Week4 (Child)

The Feeders in the XYZ Cube:

['Actual']=>DB('ABC',!Regions,'Month','Actual-Current Year');

Suppose dimension structured changed to: dim2! Months

Month (leaf)

Week1(leaf)

Week2 (leaf)

Week3 (leaf)

Week4 (leaf)

Rule: Month = week1+week2+week3+week4

Does this"['Actual']=>DB('ABC',!Regions,'Month','Actual-Current Year');" Feeder would work in same manner as it was with prior structure of dim2 !Months


Thanks

Dharav

[EvgenyT]

Hi,

Let me get it clear

Cube XYZ dim structure: Regions, Years, Scenario

Cube ABC dim structure: Regions, Month, Scenario

Correct?

Whats is the dim structure of !Years?

In case of the rule change, weeks would feed Month and Cube XYZ would feed weeks.

[dan.kelleher]

hi dharav,

Feeding to a consolidation is the same as feeding to each ultimate n-level leaf underneath the consolidation separately.

So in your first case

['Actual']=>DB('ABC',!Regions,'Month','Actual-Current Year');

equivalent to

['Actual']=>
DB('ABC',!Regions,'Week1','Actual-Current Year'),
DB('ABC',!Regions,'Week2','Actual-Current Year'),
DB('ABC',!Regions,'Week3','Actual-Current Year'),
DB('ABC',!Regions,'Week4','Actual-Current Year');

If you make your 'Month' element a leaf, you will need to write the feeder in longhand as above.

[dharav]

Thank you all for prompt response.

I had the same thought dan. In practical scenario i have more than 4200 elements without having any consolidation and i can not use dummy consolidation here to feed due to some strange business requirements. It would be better to transfer the data through TI instead of Rules.


Thanks Again you all

Dharav

[dan.kelleher]

i can not use dummy consolidation here to feed due to some strange business requirements

Why can't you create a consolidation and hide it from the end user using element security?