Inter-cube Feeders
In my previous month’s article on “Managing the Art of Feeders”, we reviewed the concept of using Skipcheck and Feeder functionality in standard TM1 rules. In this month’s article, we will discuss further enhancing a developer’s capability around writing rules within TM1 and review the concept of inter-cube feeders. While much of the functionality and capability found within TM1 rules is necessary to provide the desired end user result set, that does not mean that a developer should simple assume that all functionality is created equal. Inter-cube feeders, while often necessary, can have a significant impact on overall performance which should be taken into consideration before inclusion in a rule. Read more
When you first begin to use TM1, especially if you came from the EP world as I did, you can quickly become enamored with how well TM1 can handle large cubes with ease. You can create multiple hierarchies within a cube and within those hierarchies TM1’s sparse consolidation algorithm aggregates values at light speed. You can reach out to virtually any data source with a Turbo Integrator (TI) process and create a dimension, create and populate a cube with data, or a myriad of other tasks only limited by the developer’s imagination. The challenge comes when you need to write rules governing more complex calculations or movement of data between cubes. No intuitive D-Links or BiF’s here. Everything must be coded, and getting the calculations to work properly requires mastering the art of feeders. 