TI - Version Rollover: Current to Prior Fcst within cube

Post Reply
jasonsacco
Posts: 6
Joined: Fri Jan 28, 2011 1:45 am
OLAP Product: tm1
Version: 9.5
Excel Version: 2007

TI - Version Rollover: Current to Prior Fcst within cube

Post by jasonsacco »

TI (Turbo Integrator) based question:


I'm looking to utilize turbo integrator as a tool to roll data from one version to the next within the same dimension, and within the same cube. The dimension elements are: Current Forecast, and Prior Forecast. I'm not sure how the TI should be structured for this. I want to do this for multiple cubes.


Version 9.5, 64 Bit, Windows 2003 Advanced Server SP2,

Thank you all,

Regards,
Alan Kirk
Site Admin
Posts: 6667
Joined: Sun May 11, 2008 2:30 am
OLAP Product: TM1
Version: PA2.0.9.18 Classic NO PAW!
Excel Version: 2013 and Office 365
Location: Sydney, Australia
Contact:

Re: TI - Version Rollover: Current to Prior Fcst within cube

Post by Alan Kirk »

jasonsacco wrote:TI (Turbo Integrator) based question:

I'm looking to utilize turbo integrator as a tool to roll data from one version to the next within the same dimension, and within the same cube. The dimension elements are: Current Forecast, and Prior Forecast. I'm not sure how the TI should be structured for this. I want to do this for multiple cubes.

Version 9.5, 64 Bit, Windows 2003 Advanced Server SP2,
One way is as follows. This assumes that there is nothing already in the target version.
  • Create a subset consisting only of the Version element that you want to move data from, assuming that you don't need to limit this movement by any other dimension. (Your period dimension comes to mind.) If you do, you'll need subsets for those too. (SubsetCreate and SubsetElementInsert functions.)
  • Create views in each cube using that subset / those subsets. (ViewCreate, ViewSubsetAssign and ViewExtractSkipZeroesSet functions, and possibly the CubeSetLogChanges function if you don't want to log the movement. Remember to set logging back on at the end if you need to.)
  • Those views will become your data source for your movement processes, most likely one for each cube.
  • In each cube's process:
    1. In the Prolog, specify the target version. (This could also be read from a control cube using CellGetS if you want to avoid hard coding it.)
    2. In the Data tab, use CellPutN to write the value sourced from your old version into your new version. The CellPutN function will use the version that you specified in your Prolog.
  • Most likely, you'll want to zero out the values in the old version. You can use the views that you created as your data source for this along with the ViewZeroOut function.
  • Destroy the views using ViewDestroy, and the subsets using SubsetDestroy.
That's it in a nutshell.
"To them, equipment failure is terrifying. To me, it’s 'Tuesday.' "
-----------
Before posting, please check the documentation, the FAQ, the Search function and FOR THE LOVE OF GLUB the Request Guidelines.
Post Reply