Hi,
using Cognos TM1 9.5.2 on Windows. I have a cube with some products in combination of organization unit that should NOT sum into total. I have created very simple cube to demonstrate a problem. Please see attachment.
Is there a way I can force TM1 to execute one dimension consolidation before another, for instance consolidate product dimension before organization unit?
Is there any other way I can solve this problem?
Please see attached sample bellow.
Regards
Some members/dimension combination should not consolidate
-
- Posts: 133
- Joined: Thu Mar 25, 2010 8:34 am
- OLAP Product: Cognos TM1
- Version: 9.5.2
- Excel Version: 0
Some members/dimension combination should not consolidate
- Attachments
-
- consolidation.png (40.2 KiB) Viewed 3794 times
- jim wood
- Site Admin
- Posts: 3960
- Joined: Wed May 14, 2008 1:51 pm
- OLAP Product: TM1
- Version: PA 2.0.7
- Excel Version: Office 365
- Location: 37 East 18th Street New York
- Contact:
Re: Some members/dimension combination should not consolidat
The whole point of OLAP is it is multi dimensional object. There is no consolidation order. The only way around that I know of is the way you have done it, via rules.
Struggling through the quagmire of life to reach the other side of who knows where.
Go Build a PC
Jimbo PC Builds on YouTube
OS: Mac OS 11 PA Version: 2.0.7
Go Build a PC
Jimbo PC Builds on YouTube
OS: Mac OS 11 PA Version: 2.0.7
- ioscat
- Regular Participant
- Posts: 209
- Joined: Tue Jul 10, 2012 8:26 am
- OLAP Product: Contributor
- Version: 9.5.2 10.1.1 10.2
- Excel Version: 07+10+13
- Contact:
Re: Some members/dimension combination should not consolidat
as i suppose parent does not aggregate simply its direct children, but all its leaf children. so order of accumulation is no matter.
-
- Posts: 32
- Joined: Mon Oct 18, 2010 8:45 pm
- OLAP Product: Cognos TM1
- Version: 10.2.2
- Excel Version: 365
Re: Some members/dimension combination should not consolidat
You may want to look at the Rule Function ConsolidateChildren
http://pic.dhe.ibm.com/infocenter/ctm1/ ... ldren.html
http://pic.dhe.ibm.com/infocenter/ctm1/ ... ldren.html
-
- Posts: 133
- Joined: Thu Mar 25, 2010 8:34 am
- OLAP Product: Cognos TM1
- Version: 9.5.2
- Excel Version: 0
Re: Some members/dimension combination should not consolidat
@jim wood, what I have done in rules is just part of the solution. But TM1 has decided to consolidate test_unit dimension before test_product dimension which leads to result I don't like.
@ioscat, yes, I have read in manual of aggregating upper levels directly from leaf children. There is also an info of not having a real influence on consolidation order. I just thought someone has some trick...
@aking, I know about ConsolidateChildren function, but having really bad experience with it, big performance drop in production cube size. So I try to avoid ConsolidateChildren function as much as possible.
As I can think of the only really good solution is to add additional dimension to the cube and name it something like "product type" and then for each leaf dimension combination define the product type. In this case consolidation should work correctly... I just thought there is some other simple to implement solution without adding new dimension.
@ioscat, yes, I have read in manual of aggregating upper levels directly from leaf children. There is also an info of not having a real influence on consolidation order. I just thought someone has some trick...
@aking, I know about ConsolidateChildren function, but having really bad experience with it, big performance drop in production cube size. So I try to avoid ConsolidateChildren function as much as possible.
As I can think of the only really good solution is to add additional dimension to the cube and name it something like "product type" and then for each leaf dimension combination define the product type. In this case consolidation should work correctly... I just thought there is some other simple to implement solution without adding new dimension.