Page 1 of 1

Scenario Monitoring

Posted: Tue Jan 13, 2015 11:08 am
by kkmk
We have occasionally encountered situations where the actuals, or some other locked scenario changed for one reason or another. Sometimes an account was duplicated in the hierarchy, or somebody with admin privileges had a template issue, or other reasons undetermined.

I need your guidance to create a daily chore that could alert us by email if anything changed in an important scenario, like actuals, or current strategic plan. It wouldn’t need to provide a detailed account, unless that would be simple to incorporate. We should be able to specify a list of scenarios that we want monitored, and if values change from day to day at one of the top level account hierarchies, for any year, get an email. The process would also have to ignore current period for actuals, as that is expected to change.

We have recently moved to cloud and my earlier email notification programs are not working, I need help on this also.

TM1 10.2

Thanks in advance
KKMK

Re: Scenario Monitoring

Posted: Tue Jan 13, 2015 12:27 pm
by cgaunt
Hi KKMK

The Version may be locked, but if you change your account dimension then all data in all versions will be skewed if that account is used. There is no 'silver bullet' approach here that will cure all your problems. You need to analyse all the scenarios that have caused your data to appear corrupt and then trap for them. Lets take the case of the account being duplicated in the financial measures dimension, you could trap for that by using a control sheet with ELPARN on it. Any account that returns a value more than one will be a duplicate. You could write a rule to populate the value onto an attribute on the account dimension and then use an MDX filter to dynamically create a subset based on that value. The subset would then be created automatically and could be set up on a control sheet.

Happy to discuss other scenarios, but I hope that gives you a starter for one scenario.

cgaunt

Re: Scenario Monitoring

Posted: Tue Jan 13, 2015 12:39 pm
by declanr
Stick everything out to SQL every night with a datestamp and then have a sql view that does the value for one datestamp less the other and suppress anywhere that values are zero. You are left with a list of all cube intersections that have moved.

Re: Scenario Monitoring

Posted: Wed Jan 14, 2015 9:25 am
by rmackenzie
kkmk wrote:We have recently moved to cloud and my earlier email notification programs are not working, I need help on this also.
For a quick and dirty solution, try GMail or something similar so you don't need to rely on an SMTP server on your LAN - this looks the part.

Re: Scenario Monitoring

Posted: Wed Jan 14, 2015 9:31 am
by declanr
rmackenzie wrote:
kkmk wrote:We have recently moved to cloud and my earlier email notification programs are not working, I need help on this also.
For a quick and dirty solution, try GMail or something similar so you don't need to rely on an SMTP server on your LAN - this looks the part.
Most company emails will have 2 servers set up though; one for in house and one that allows you to send & receive emails from a phone etc when you are out and about so just changing your existing email process to use the latter server details should do the trick.