Hello,
I have a Reporting Cube ( 10-dimension cube), and I have String Measure that I want to populate with Rules. (I have 3-dimensional Cube with following Dimensions: Cost_Center, Account, Product, Measures, and all three dimensions have a hierarchy. The user enters a String Measure, and there is an action button that cascades the input value all the way down to the hierarchy (or until it finds a cell with a different value, and this works perfect)
I want to display this String measure in the Reporting Cube, so I added a rule, and yes I can add FEEDERS but since I need to FEED all Consolidated Nodes in this cube, it causes some overfeeding. I am currently FEEDING from the 3 Dimensional Cube to 10-Dimensional Cube. But I was hoping I can avoid that. I have other measures in the Reporting cube, which are populated exactly where I need to display my String Measure, but it does not FEED the Consolidation String Cells.
Thank you
FEEDING String Rules on Consolidation Cells
-
ardi
- Community Contributor
- Posts: 167
- Joined: Tue Apr 02, 2013 1:41 pm
- OLAP Product: tm1, cognos bi
- Version: from TM1 9.4 to PA 2.0.9.6
- Excel Version: 2010
- Location: Toronto, ON
FEEDING String Rules on Consolidation Cells
Ardian Alikaj
-
MarenC
- Regular Participant
- Posts: 457
- Joined: Sat Jun 08, 2019 9:55 am
- OLAP Product: Planning Analytics
- Version: Planning Analytics 2.0
- Excel Version: Excel 2016
Re: FEEDING String Rules on Consolidation Cells
Hi,
any reason you can't do this via a process and incorporate it into your existing action button?
Maren
any reason you can't do this via a process and incorporate it into your existing action button?
Maren
- jim wood
- Site Admin
- Posts: 3964
- 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: FEEDING String Rules on Consolidation Cells
Agreed, you should ad it to the button. Trying to feed from a 3 (although I counted 4 including measures) to 10 dimensional cube is always going to result in over feeding unless you have specfic elements witin the non common dimensions to feed too.
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
- Steve Rowe
- Site Admin
- Posts: 2465
- Joined: Wed May 14, 2008 4:25 pm
- OLAP Product: TM1
- Version: TM1 v6,v7,v8,v9,v10,v11+PAW
- Excel Version: Nearly all of them
Re: FEEDING String Rules on Consolidation Cells
The comments about populating with a TI are probably the most right
If you want to do this with rules then the feeder needs to be in the 10d cube and needs to start from a leaf cell that is populated at the right level, as you suggest in your post.
but
1. You need to put the Feedstrings statement in your rule sheet in order to be able to feed a string cell.
2. Remember feeders only do work at the N / Leaf level of a cube, you can't feed a consolidated cell. A consolidation will only return a ruled value if one of the cells below it is feed and populated, even for stings. (Assuming a zero-suppressed view)
So your rule sheet would be something like this.
Skipcheck;
Feedstrings;
#if statement stops value being populated at all the unfed locations.
['String Value']=S: If (['Source Value']=0 , '' , DB('Other 3d Cube' ,!Dim1, !DIm2, !Dim3));
Feeders;
['Source Value']=> ['String Value'];
This would mean that the string value is populated at both the N and C level though
If you want to do this with rules then the feeder needs to be in the 10d cube and needs to start from a leaf cell that is populated at the right level, as you suggest in your post.
but
1. You need to put the Feedstrings statement in your rule sheet in order to be able to feed a string cell.
2. Remember feeders only do work at the N / Leaf level of a cube, you can't feed a consolidated cell. A consolidation will only return a ruled value if one of the cells below it is feed and populated, even for stings. (Assuming a zero-suppressed view)
So your rule sheet would be something like this.
Skipcheck;
Feedstrings;
#if statement stops value being populated at all the unfed locations.
['String Value']=S: If (['Source Value']=0 , '' , DB('Other 3d Cube' ,!Dim1, !DIm2, !Dim3));
Feeders;
['Source Value']=> ['String Value'];
This would mean that the string value is populated at both the N and C level though
Technical Director
www.infocat.co.uk
www.infocat.co.uk
