STET - TM1 9.1 SP4

[vaneagle]

Hi Guys,

We are looking at using tm1 in our organisation. Now I am first time user of tm1 and can see great value in it.

Our environment is getting close to whereby we can actually install tm1 and off we go.

I am looking to go best practice from the word go and looking at the stet function, there is not much to go by in the manual.

Given the following:

Code: Select all

['Actual'] = N: Stet;
[{'2007','2008'}] = N: stet;
[{'2009','2010','2011'},'53'] = N: STET;
['85']=N:STET;

Given that there will be many cubes which will have something very similar in them, instead of going through and changing the rules each year in each of the cubes is there a way that it could be done centrally? Perhaps from a control cube or something similar?

At this point in time I have had no training in tm1 and definitely don't know ti process and rules either. But over time i do intend to learn as much as possible.

thanks,

[lotsaram]

"STET" is basically shorthand for "No rule applies" which means leaf cells will be data enterable and higher level cells will consolidate leaf values.

That is a fairly technical question for someone with no training in TM1 rules (very oddly written rules too BTW)

Rest assured that yes by using a combination of control cube values and attributes rules can be made much more generalised and flexible and don't have to be written as specific and case by case. This doesn't eliminate the need for maintenance per say but it makes maintenance and processes such as budget or month rollover much more straightforward as the updating process is then merely to update a cube or attribute value rather than to edit a hard coded value in the rule itself.

[Steve Rowe]

Just to make a couple of more points vaneagle,

Your company should invest in some training for you if they expect to get an ROI in the short term, not training people when you buy a new product is pretty short sighted....
Avoid having element names that are oure numerics, this can cause long term problems referencing TM1 from Excel.
As lotsaram said your rules are odd, not sure why you would want to do that... There is no need to explicitly delcare a area in a cube as open for input by putting stet in the rules. When a cube is built it is all open for input. It's only when you add a rule for an area and need some of that area to be open for input that you need to use Stet.
Using attributes is and control cubes is the standard approach to applying conditionality in a rule. Control cubes are built by the developer so you have a free hand on the dimensionality and attribute cubes built by TM1.

If you can explain why you think you need to use the stet function we may be able to help further.

HTH

[vaneagle]

Thanks guys.

Yes training will be on the agenda.

I copied the code from elsewhere and whilst only reading the manual i was hoping there would be a better method of doing this. I know a little vba and prefer to use variables when possible, which led to my question here about TM1.

As you both have mentioned Control Cubes and attributes seem to be the way to go. I will make sure this happens in our models.

Thanks again guys.

I think i will be visiting here more often once everything is up and running.