Rules - matching elements in different dimensions

[chewza]

Hi there

Can you "match" elements up when you are using different dimensions, but the element values correspond..????

I have 2 sales budget cubes – one at a detail customer level, and one at a summary branch level.
Without going into unnecessary detail, I am trying to achieve the following in my rule:
• Take customer in detail cube (ie n element)
• Determine the branch – did this with ELPAR
• Look up the value in the branch cube

The summary cube has a branch dimension, and the detail cube has a customer dimension.
The customer dimension has customers rolling up into branches.
The branch codes in the customer dim, correspond to the branch codes in the branch dim.

Problem is that when I use the DB function in my rule, and need to specify the element in the branch dim, I can’t “pass” the branch code from my customer dim as the reference to use in my branch dim…

Any ideas?

[mce]

You should not have any problem if the branches in both dimensions are spelled same way as they exist in both dimension. Do you use Branch code as alies or original element names?
If you can paste your rule code here, it might help to identify the problem.

[chewza]

thanks - sorted - branch code works fine

[mithun.mistry11]

Hello there

Would it be possible if I can have some assistence in solving the issue I am coming across.

The issue is:

I am using 3 cubes - CUBE-1, CUBE-2 & Control
CUBE-1 is an input cube ... uses DIM1
CUBE-2 is a reporting cube OF CUBE-1.. uses DIM1 with added element
Control Cube is used for the string in that cube. I have created an attribute in DIM1 to pull data from control cube. That works!
Now where I am having an issue is, I need to create a rule that will allow me to use the string (M01) which is in the attribute (DIM1), match it with one of CUBE-2.DIM1 elements (M01, M02, M03 or M04) and then the number values in CUBE-2.DIM1 element (M01) , put them into CUBE-2.DIM1 element (M-1)

Hope that makes sense.

Thank you

[BariAbdul]

[quote][Hope that makes sense/quote]

Unfortunately not,need your cubes dimensionality and complete rules.Thanks

[mithun.mistry11]

Ok, I have a attribute called Prev which has got M01(driven by a control cube) in the M-01 node in a dimension used in both CUBE-1 and CUBE-2.

I need to use that attribute to allow tm1 to pick M01 and say to the dimension in CUBE-2, "IS THERE AN ELEMENT CALLED M01 IN YOUR LIST OF ELEMENTS?"

IF YES, all the data from M01 in CUBE-2 should be copied into a new element called M-01


So if the MONTH is 01 - the string M01 will be in the control cube - 'Prev' atribute will collect that string and save it. That string is then used to match with one of the elements in the CUBE-2 dimension...

That make more sense?

[mithun.mistry11]

I've solved it now..thank you for help