9.5.1: Relative Proportional Spread Error

Post Reply
harrytm1
Regular Participant
Posts: 226
Joined: Thu Apr 02, 2009 2:51 pm
OLAP Product: IBM Planning Analytics
Version: Latest version
Excel Version: 2003 to 2019

9.5.1: Relative Proportional Spread Error

Post by harrytm1 »

hi all,

I have a Profit Loss cube with data populated into Year 2010 under Actual version. Actual Version is STET in the first line of the cube rules.

I tried to perform a Relative Proportional Spread from Year 2010 to 2011 for Actual version only. Hence, in the cube view, i right-clicked on Net Profit/Loss element at Full Year to spread. However, an error message appeared suggesting that there is a conflict with rule and nothing was spread in the end.

I scanned through all n-elements in the PL Account dimension and nothing is rule-calculated, which is due to the STET statement. To troubleshoot further, I even deleted the rule and spread again. The same error appeared again.

Anyone experienced such issue with spreading in 9.5.1? i don't recall having such issues in 9.4.1 as the same model was used in 9.4.1 and spreading was odne successfully.

Many thanks!
Planning Analytics latest version, including Cloud
User avatar
qml
MVP
Posts: 1097
Joined: Mon Feb 01, 2010 1:01 pm
OLAP Product: TM1 / Planning Analytics
Version: 2.0.9 and all previous
Excel Version: 2007 - 2016
Location: London, UK, Europe

Re: 9.5.1: Relative Proportional Spread Error

Post by qml »

Just a stab in the dark here, but maybe you are facing the problem of circular reference? TM1 would display the same error message (which does not help much!) if you tried to spread, say, a value from a parent to its child. Check if your reference element is not a parent of your target element.
Kamil Arendt
AlastairFM
Posts: 10
Joined: Mon Feb 28, 2011 12:13 pm
OLAP Product: TM1 / Cognos Express
Version: PAL 2.0.9.1
Excel Version: 2016

Re: 9.5.1: Relative Proportional Spread Error

Post by AlastairFM »

Is the error message "Spreading failed due to conflicts with rules" ?

If this is the case the following IBM article may be the solution:

http://www-01.ibm.com/support/docview.w ... wg21474015
Post Reply