Identify TIs inside Chores

[bunchukokoy]

Hi Guys,

Is there an easy way to identify what processes are included in a chore, easier than looking at them one by one?

Thanks.

[Alan Kirk]

Hi Guys,

Is there an easy way to identify what processes are included in a chore, easier than looking at them one by one?

Thanks.

Not sure what you mean. If you have the Properties Window open in Server Explorer, and select the chore in the left pane, all of the processes are shown in the right hand pane. Doesn't that give you what you need?

[bunchukokoy]

Hi Alan,

Thanks! (hayzz. it's just so simple and I didn't know.)

Thanks a lot Sir!

[lotsaram]

If you want something that's embedded and reportable within TM1 it is not difficult to create a cube to capture this data. (Much like a cube to capture cube dimensionality except we can't reference TI functions because we don't have any, but we can examine the .cho files themselves pretty easily by assigning them as a datasource and thus exposing the processes names and order of execution within which are just held as text in the .cho file).

The attached processes will create a new cube and dimension on your server SYS_ChoreProcesses and SYS_ChoreProcesses_M. The measure dimension contains a single numeric element "Position".

ChoreProcCube.JPG (15.42 KiB) Viewed 2532 times

Instructions:
There are 2 processes, SYS.Chore.Process.Docu.Caller this process has no data source but loops through all chores via a prolog while loop and calls a the 2nd process SYS.Chore.Process.Docu with a parameter of the current chore in the loop. The 2nd process assigns the .cho file as its datasource and writes the position of each process in the chore to the cube.
Note: i) As in some (certainly the latest) versions there are issues with trying use newly created meta data in the same process that created it, the "caller" process requires 2 runs to initialize, 1 to create the measure dimension, 2 to create the cube. Thereafter only 1 run is required to completely update the cube.
ii) The .cho file is set as a data source with no path. TM1 should assume the path is the data directory of the server. This works 99% of the time but in rare cases the code might need editing to supply the path of the data directory.

Then just create a default view for the cube with chores on title, processes on rows and measure on columns with auto recalc and zero suppression. Add a filter in ascending order on the Position column and you have yourself a good way of reporting on which chores use which processes that is transportable to any server.

ChoreProcVue.JPG (31.59 KiB) Viewed 2532 times

And obviously it is accessible through an active form in Excel and able to be formatted any which wax you want it.

[bunchukokoy]

Thanks so much Sir Lotsaram.