TM1 Forum

Hi,

I have a usual requirement in an OPEX cube when a user selects a Cost Center from the title dimension, only the relevant Expense lines should appear on the rows. We have done this many times in Web an Perspectives, worked fine. There is a small parameter cube with Cost Centers and Expenses, put a 1 to the relevant combinations, then use a subset like this in the planning cube, while having CCs on title, Expenses on rows:

{FILTER(TM1FILTERBYLEVEL(TM1SUBSETALL([Accounts_OPEX_PLAN]) , 0) , [PLAN_Param_CCToGL].([CostCenters_OPEX].CURRENTMEMBER,[StrNum].[nValue]) = 1)}

It seems CAFE ignores the "[CostCenters_OPEX].CURRENTMEMBER" part of the subset, and returns those Expenses of which Sum is 1 in the parameter cube => so those expenses that are assigned to one and only one Cost center, independently from the Cost center selection on the title.

Any idea of a quick workaround? Same results but different mdx code?

Thank you!
Matyas

HI

I would suggest creating a dimension from your cube with consolidations for each Cost Centre and base level elements of the relevant Expense codes. Then you don't even need MDX. You can use a simple list with ELCOMP.

Regards

Paul Simon

Thanks Paul!
Actually, that is one of my main points to consider if I want to use one merged, or two dimensions, found some pros/cons for both. If I understand correctly your suggestion means the one dimension approach.

Hi

No I am not suggesting that you need to convert your cube to a single combined dimension. I was suggesting that you create a dimension that is not used in any cubes and that you just use this to drive the dependency between the two dimensions for your second drop down box.

Regards

Paul Simon

Since the CostCenters_OPEX is a title dimension, the [CostCenters_OPEX].CURRENTMEMBER is not needed for a cube view. It will automatically filter it for the context of the title dimension, the cost center selected.

Hi

It will automatically filter it for the context of the title dimension, the cost center selected.

Not in CAFE unfortunately

Ah. My apologies.

Hi
Seems to be a bug, if I open the subset editor in CAFE, click on the MDX icon, and amend the subset by just adding a simple space, it starts working.
So I think it won't be related to CurrentMember, much more how CAFE renders the dynamic subset, although not sure yet what kind of mdx expressions/formulas are impacted, if it is not only CurrentMember

Ticket opened, I will post the APAR nr here.