TM1 TurboIntegrator (or TI) is the programming or scripting tool that allows you to automate data importation, metadata management, and many other tasks.
In my recent book:
IBM Cognos TM1 Developers Certification Guide- (http://www.amazon.com/IBM-Cognos-Developers-Certification-Guide/dp/1849684901), I discussed advanced techniques for TurboIntegrator (TI) scripting in regards to the current IBM Cognos TM1 Developer (Test COG-310) certification exam.
Specifically, my book reviews the advanced tabs in a TI script (and techniques to best exploit them), the difference between the “four TI scripts”, identifies where to apply custom scripting (as opposed to TM1 auto generated code), and finally provides some excellent “tips and tricks” you can use when creating your TI.
The Future of Big Data
With some guidance, you can craft a data platform that is right for your organization’s needs and gets the most return from your data capital.
Here is a short exert:
Order of operations within a TurboIntegrator process
As we have mentioned in Chapter 4, Rules, it is extremely important to be aware of and understand the following information about the sub-tabs of the Advanced tab:
• When you run a TI process, the procedures are executed in the following sequence (basically left to right as they are displayed):
• Prolog is executed one time only.
• If the data source for the process is None, Metadata and Data are disabled and do not execute.
If the data source for the process is None, Epilog executes one time immediately after Prolog finishes processing.
• If the data source for the process is not None, Metadata and Data will execute for each record in the data source.
• Code to build or modify a TM1 dimension resides in the Metadata tab.
• The Metadata tab is used to build TM1 subsets.
• All lines of code in the metadata procedure are sequentially executed for each record in the data source.
• All lines of code in the data procedure are sequentially executed for each record in the data source.
• Because the data procedure is executed for each row or record in the data source, an error is generated in the procedure for multiple times.
• The data procedure is the procedure used to write/edit code used to load data into a cube.
• The data source is closed after the data procedure is completed.
• The epilog procedure is always the last procedure to be executed.
• Not all TM1 functions will work as expected in every procedure.
Aliases in TurboIntegrator functions
In Chapter 4, Rules we learned that you can use aliases to reference a dimension element in your TI process. Let us look at a practical example. Let us suppose that a company does forecasting on a monthly basis. Each month a new version of the working forecast is created. For example, in January the forecast consists of 12 months of forecasted sales (January through December). In February, the working forecast consists of one month (January) of actual sales data and 11 months of forecasted sales (February through December). In March, the working forecast consists of two months (January and February) of actual sales and 10 months of forecasted sales—and so on. In this example, you can define an alias attribute on the version dimension and use it to refer to whatever version of the forecast is currently running (or is the working version).
Then, TI processes can refer to a version as the working forecast (the alias) and always connect to the correct version.
I truly enjoyed researching, writing and publishing this book and hope that you find it useful in pursuing your TM1 certification. I am currently working on my next book project, so all feedback is welcomed.
Feel free to join my twitter group: @JamesDMiller.