Why Consolidated Elements Include in my Subset?

Post Reply
bunchukokoy
Regular Participant
Posts: 197
Joined: Thu Dec 03, 2009 8:47 am
OLAP Product: IBM Cognos TM1
Version: 10.2.2.x
Excel Version: 2010
Location: Singapore

Why Consolidated Elements Include in my Subset?

Post by bunchukokoy »

Hi! Again,

I wonder why this does happen, I have a dynamic subset which means it has an expression recorded in it. My intention for this subset is to display all leaf elements (n elements/ zero level) only and I also intend not the consolidated elements with no child/ren to be dispalyed. But they just remain on my subset. Is there any way I can retrieve only the leaf elements excluding the consolidated elements without child/ren? I think it's on my MDX, but don't know how.

Advance Thanks for your help!

bunchukokoy :D
lotsaram
MVP
Posts: 3706
Joined: Fri Mar 13, 2009 11:14 am
OLAP Product: TableManager1
Version: PA 2.0.x
Excel Version: Office 365
Location: Switzerland

Re: Why Consolidated Elements Include in my Subset?

Post by lotsaram »

Orphan consolidations are level 0 elements which is why they are returned in the subset (presumably you are filtering on level 0).

A consolidation with no children has no reason to exist. Usually you would run a TI script to remove orphan consolidations.
jstrygner
MVP
Posts: 195
Joined: Wed Jul 22, 2009 10:35 pm
OLAP Product: TM1
Version: 9.5.2 FP3
Excel Version: 2010

Re: Why Consolidated Elements Include in my Subset?

Post by jstrygner »

First, my simple workaround proposal:
1. Define a text attribute (e.g. Type) for the dim you want to filter on.
2. Create a rule in Control Object Cube that stores those attributes values where you calculate element type (C or N).
3. Expand your filter by level = 0 MDX with filter by attribute where 'Type' = 'N'.

Second, with my whole respect, I dare to disagree with lotsaram's statement :-)

I used consolidations with no children in one project and found it very useful.
It was a dimension where every department had potentially two types of projects it could budget.
Sometimes departments had no projects of one or both types, so it looked like this:

Code: Select all

- All projects
  - Dep A
    - Dep A Projects X
      Project 1
      Project 2
    - Dep A Projects Y
      Project 3
  - Dep B
    + Dep B Projects X
    - Dep B Projects Y
      Project 4
In the above example Dep B had no projects of type X, but still it was very helpful that such an element (Dep B Projects X) existed (we could use it in many reports, TI, dynamic subsets, parallel hierarchies and technical consolidations). It was also very useful, that no one could write into it, because it was a consolidation.

Regards,
Post Reply