Calculation in two directions

[Horst]

Hi,

I have a question about calculations in TM1.
In Enterprise Planning we have the possibility to type values in calculated measures, which is not possible in TM1.

e.g. Quantity * Price = Revenue
In EP and TM1 I can change the Quantity and the Price to get a new Revenue - in EP I can change the Revenue as well.

Is there any possibility or workaround to do this in TM1?

Thanks a lot!

[lotsaram]

Well actually for EXACTLY the example you give this should work in TM1 as well. TM1 allows bereakback over a calculation providing that there is only one flex variable. This has been a feature for quite a while, maybe even as far back as 9.1.

In your example assuming that price was looked up with a DB from another cube and quantity was input data in the same cube as revenue then a spread on revenue would automatically flex quantity. Try it!

As soon as you have more than one input variable however then the spread will fail as the engine won't know which input to flex.

[Horst]

Hi,

thanks for your help.
I tried to build a small demo case in the way you described below, but I'm not sure whether I did this in the right way.

I've created a very small cube (Cube_Price) with only two dimensions products (Sum, Prod1, Prod2) and price (Price).
Then I've created a second cube with the two dimensions products (Sum, Prod1, Prod2), Revenue (Quantity, Price, Revenue) and a cube rule with two calculations:

['Price'] = DB('Cube_Price', !products,'Price');
['Revenue'] = N: ['Price'] * ['Quantity'];

In this way I still can't spread data over my revenue.

Where is my fault?

[lotsaram]

I just tried this on a small model running 10.2.204. Didn't work for me either but it did use to work.
Possibly this feature has been broken in the 10.2 release. Disappointing as it was a nice feature. A feature I guess that wasn't implemented that often in practice.

Maybe there's something finicky about how the calculation needs to be set up to make it work, but I don't remember this being the case, it just worked.

[jduplessis]

I just tried this on a small model running 10.2.204. Didn't work for me either but it did use to work.
Possibly this feature has been broken in the 10.2 release. Disappointing as it was a nice feature. A feature I guess that wasn't implemented that often in practice.

Maybe there's something finicky about how the calculation needs to be set up to make it work, but I don't remember this being the case, it just worked.

This will work if you set up a hierarchy with the calculation element being the parent and the inputs being the children. The rule for the calculation element has to be a C level rule in this case. It will allow type in on consolidation which will adjust the variable component. But only one of the inputs can be variable, the other has to be fixed or a DB reference to another cube.

Also, only clients that allow type in on consolidation will allow this behavior. So you have to use cube view in Web, but it wont work in cube viewer in architect or perspectives, this should work in contributor as well but I didn't check it.