Hi Guys,
I'm new to TM1 and I was testing around in TM1 9.5 Contributor. I've created a small cube and deployed it successfully to Contributor. Then I've tried to enter some data sets and wanted to use the Break-Back / Data-Spread Function on the Time Dimension. So I've tried to enter some data on the Year Level (Consolidated Element) and TM1 returned the message: "Spread Failed - No updateable Cell" or "Spread total zero"
-Year
--Jan
--Feb
--Mar
How is a break-back possible?
I appreciate any help ...
many thanks and kind regards
Chris
TM1 9.5 Contributor Break-back
-
rkaif
- Community Contributor
- Posts: 328
- Joined: Fri Sep 05, 2008 6:58 pm
- OLAP Product: IBM Cognos TM1
- Version: 9.1 or later
- Excel Version: 2003 or later
Re: TM1 9.5 Contributor Break-back
There are variety of Data spread available in TM1. Which Data spread type you are tying to do?
You can read about spreading options in the Manual itself. See the topic End User Manual - Using Data Spreading.
You can read about spreading options in the Manual itself. See the topic End User Manual - Using Data Spreading.
Cheers!
Rizwan Kaif
Rizwan Kaif
-
kelso
- Posts: 15
- Joined: Mon Jul 05, 2010 10:43 pm
- OLAP Product: TM1
- Version: 9.1.4
- Excel Version: 2003
Re: TM1 9.5 Contributor Break-back
breakback like "Cognos Planning" is different in TM1, you can´t dataspread a value in cells that have a rule. What you can do is use Relative Proportional Spread (the most powerful data spread function) to copy values into a new versions and play in scenarios with proportions.
-
lotsaram
- MVP
- Posts: 3702
- Joined: Fri Mar 13, 2009 11:14 am
- OLAP Product: TableManager1
- Version: PA 2.0.x
- Excel Version: Office 365
- Location: Switzerland
Re: TM1 9.5 Contributor Break-back
The main feature differences between break-back and spreading is that the default behaviour in Contributor versus TM1 are:
- behaviour where no prior input data exists (null or zero intersection)
- behaviour when a calculation rule or BiF exists
When doing a break-back over a null intersection Contributor evenly divides the top level number over all the leaves. In TM1 you can't top-down proportional spread over a null value as some data is required to actually spread on. This is the reason for your error. Personally I don't see this as a significant issue, it is just a feature difference as it is easy enough to pre-populate in TM1 with a repeat leaves or relative proportional spread. Although if enough former Planning users request it this feature might get changed (it wouldn't be a bad thing ...)
The other issue would be much more difficult to solve in TM1. Virtually by definition in TM1 a rule over a cube area supersedes and prohibits data entry or spreading in that area (as the rule defines what the value should be). To change a rule derived number you have to go back and change the upstream drivers. The one exception is that they did change the spreading engine a few years back to allow spreading over a simple calculation internal to a single cube with a single data input driver and single dependent value (such as a weighted average). It is possible to spread over such a calculation and change the underlying driver values. However where there are multiple drivers or any inter-cube dependency a spread will fail. To long term TM1 users this is expected behaviour. I can see that coming from planning this is a feature you would be used to and want to have but I think it would be very difficult to make this happen in TM1 (they might do it but it's going to take time!) It can be solved with some workarounds in application design which would be the best approach for now.
- behaviour where no prior input data exists (null or zero intersection)
- behaviour when a calculation rule or BiF exists
When doing a break-back over a null intersection Contributor evenly divides the top level number over all the leaves. In TM1 you can't top-down proportional spread over a null value as some data is required to actually spread on. This is the reason for your error. Personally I don't see this as a significant issue, it is just a feature difference as it is easy enough to pre-populate in TM1 with a repeat leaves or relative proportional spread. Although if enough former Planning users request it this feature might get changed (it wouldn't be a bad thing ...)
The other issue would be much more difficult to solve in TM1. Virtually by definition in TM1 a rule over a cube area supersedes and prohibits data entry or spreading in that area (as the rule defines what the value should be). To change a rule derived number you have to go back and change the upstream drivers. The one exception is that they did change the spreading engine a few years back to allow spreading over a simple calculation internal to a single cube with a single data input driver and single dependent value (such as a weighted average). It is possible to spread over such a calculation and change the underlying driver values. However where there are multiple drivers or any inter-cube dependency a spread will fail. To long term TM1 users this is expected behaviour. I can see that coming from planning this is a feature you would be used to and want to have but I think it would be very difficult to make this happen in TM1 (they might do it but it's going to take time!) It can be solved with some workarounds in application design which would be the best approach for now.