This is an archive of the Maximo Yahoo Community. The content of this pages may be a sometimes obsolete so please check post dates.
Thanks to the community owner Christopher Wanko for providing the content.
Looking for what would be the best system/solution to have something run once every fiscal year. I was thinking escalation would be the way to go although I can't get it to work as I thought it might with the escalation points.
For instance at the end of our fiscal year I want to set ALL Labor reportedhrs, ytdothrs, ytdhrsrefused back to 0 (zero) for EVERY Labor record (no filter). So technically it's a simple SQL UPDATE statement and I have the actions added and when I tested it the first time, worked great. When I made a modification and ran it again, it wouldn't run.
Here's my setup Maximo 7.1.0.
* Escalation applies to Labor
* Set to run (every 2 hours on the 30min (for testing)
* Created an escalation point that is empty with the exception of checking the Repeat box. (which I know this area is the problem)
* Created 3 new actions to upate the Labor records
As you said, having the Repeat box unchecked is the problem. If it's not checked, it will run, but it will think it has already run against all the records so nothing will get updated as you wish. So either:
--check the Repeat box; or
--find these (and make sure you find ONLY these) records in the ESCREPEATTRACK table in the database and delete them
Travis Herron
--- In MAXIMO@yahoogroups.com, "b471code3" <bkehren@...> wrote:
>
> Looking for what would be the best system/solution to have something run once every fiscal year. I was thinking escalation would be the way to go although I can't get it to work as I thought it might with the escalation points.
>
> For instance at the end of our fiscal year I want to set ALL Labor reportedhrs, ytdothrs, ytdhrsrefused back to 0 (zero) for EVERY Labor record (no filter). So technically it's a simple SQL UPDATE statement and I have the actions added and when I tested it the first time, worked great. When I made a modification and ran it again, it wouldn't run.
>
> Here's my setup Maximo 7.1.0.
> * Escalation applies to Labor
> * Set to run (every 2 hours on the 30min (for testing)
> * Created an escalation point that is empty with the exception of checking the Repeat box. (which I know this area is the problem)
> * Created 3 new actions to upate the Labor records
>
Try Cron Task.
--- In MAXIMO@yahoogroups.com, "b471code3" <bkehren@...> wrote:
>
> Looking for what would be the best system/solution to have something run once every fiscal year. I was thinking escalation would be the way to go although I can't get it to work as I thought it might with the escalation points.
>
> For instance at the end of our fiscal year I want to set ALL Labor reportedhrs, ytdothrs, ytdhrsrefused back to 0 (zero) for EVERY Labor record (no filter). So technically it's a simple SQL UPDATE statement and I have the actions added and when I tested it the first time, worked great. When I made a modification and ran it again, it wouldn't run.
>
> Here's my setup Maximo 7.1.0.
> * Escalation applies to Labor
> * Set to run (every 2 hours on the 30min (for testing)
> * Created an escalation point that is empty with the exception of checking the Repeat box. (which I know this area is the problem)
> * Created 3 new actions to upate the Labor records
>
I always put 1=1 in the escalation point condition when there isn't a "true" escalation point.
-----Original Message-----
From: MAXIMO@yahoogroups.com [mailto:MAXIMO@yahoogroups.com] On Behalf Of b471code3
Sent: Thursday, October 04, 2012 10:59 AM
To: MAXIMO@yahoogroups.com
Subject: [MAXIMO List] A process to run every fiscal year
Looking for what would be the best system/solution to have something run once every fiscal year. I was thinking escalation would be the way to go although I can't get it to work as I thought it might with the escalation points.
For instance at the end of our fiscal year I want to set ALL Labor reportedhrs, ytdothrs, ytdhrsrefused back to 0 (zero) for EVERY Labor record (no filter). So technically it's a simple SQL UPDATE statement and I have the actions added and when I tested it the first time, worked great. When I made a modification and ran it again, it wouldn't run.
Here's my setup Maximo 7.1.0.
* Escalation applies to Labor
* Set to run (every 2 hours on the 30min (for testing)
* Created an escalation point that is empty with the exception of checking the Repeat box. (which I know this area is the problem)
* Created 3 new actions to upate the Labor records
If I'm not mistaken doesn't a cron task instance get created and ran under the Escalations cron task? Why create a new one when its already there?
--- In MAXIMO@yahoogroups.com, "June" <june_jun_chen@...> wrote:
>
> Try Cron Task.
>
> --- In MAXIMO@yahoogroups.com, "b471code3" <bkehren@> wrote:
> >
> > Looking for what would be the best system/solution to have something run once every fiscal year. I was thinking escalation would be the way to go although I can't get it to work as I thought it might with the escalation points.
> >
> > For instance at the end of our fiscal year I want to set ALL Labor reportedhrs, ytdothrs, ytdhrsrefused back to 0 (zero) for EVERY Labor record (no filter). So technically it's a simple SQL UPDATE statement and I have the actions added and when I tested it the first time, worked great. When I made a modification and ran it again, it wouldn't run.
> >
> > Here's my setup Maximo 7.1.0.
> > * Escalation applies to Labor
> > * Set to run (every 2 hours on the 30min (for testing)
> > * Created an escalation point that is empty with the exception of checking the Repeat box. (which I know this area is the problem)
> > * Created 3 new actions to upate the Labor records
> >
>
That appeared to be the ticket, thank you Christopher!
--- In MAXIMO@yahoogroups.com, "Hanna, Christopher CTR" <christopher.a.hanna@...> wrote:
>
> I always put 1=1 in the escalation point condition when there isn't a "true" escalation point.
>
> -----Original Message-----
> From: MAXIMO@yahoogroups.com [mailto:MAXIMO@yahoogroups.com] On Behalf Of b471code3
> Sent: Thursday, October 04, 2012 10:59 AM
> To: MAXIMO@yahoogroups.com
> Subject: [MAXIMO List] A process to run every fiscal year
>
>
>
> Looking for what would be the best system/solution to have something run once every fiscal year. I was thinking escalation would be the way to go although I can't get it to work as I thought it might with the escalation points.
>
> For instance at the end of our fiscal year I want to set ALL Labor reportedhrs, ytdothrs, ytdhrsrefused back to 0 (zero) for EVERY Labor record (no filter). So technically it's a simple SQL UPDATE statement and I have the actions added and when I tested it the first time, worked great. When I made a modification and ran it again, it wouldn't run.
>
> Here's my setup Maximo 7.1.0.
> * Escalation applies to Labor
> * Set to run (every 2 hours on the 30min (for testing)
> * Created an escalation point that is empty with the exception of checking the Repeat box. (which I know this area is the problem)
> * Created 3 new actions to upate the Labor records
>
Yes, you are correct. Directly creating a cron task, if I'm not mistaken, would force you to put ALL of your logic in a custom class. An escalation can use a simple action so often no coding is required at all.
-----Original Message-----
From: MAXIMO@yahoogroups.com [mailto:MAXIMO@yahoogroups.com] On Behalf Of b471code3
Sent: Wednesday, October 10, 2012 2:05 PM
To: MAXIMO@yahoogroups.com
Subject: [MAXIMO List] Re: A process to run every fiscal year
If I'm not mistaken doesn't a cron task instance get created and ran under the Escalations cron task? Why create a new one when its already there?
--- In MAXIMO@yahoogroups.com <mailto:MAXIMO%40yahoogroups.com> , "June" <june_jun_chen@...> wrote:
>
> Try Cron Task.
>
> --- In MAXIMO@yahoogroups.com <mailto:MAXIMO%40yahoogroups.com> , "b471code3" <bkehren@> wrote:
> >
> > Looking for what would be the best system/solution to have something run once every fiscal year. I was thinking escalation would be the way to go although I can't get it to work as I thought it might with the escalation points.
> >
> > For instance at the end of our fiscal year I want to set ALL Labor reportedhrs, ytdothrs, ytdhrsrefused back to 0 (zero) for EVERY Labor record (no filter). So technically it's a simple SQL UPDATE statement and I have the actions added and when I tested it the first time, worked great. When I made a modification and ran it again, it wouldn't run.
> >
> > Here's my setup Maximo 7.1.0.
> > * Escalation applies to Labor
> > * Set to run (every 2 hours on the 30min (for testing)
> > * Created an escalation point that is empty with the exception of
> > checking the Repeat box. (which I know this area is the problem)
> > * Created 3 new actions to upate the Labor records
> >
>
All:
please could you help me by telling me the name of the table or tables where is stored the data related with the option Report Down Time in Workorder module.
thank you
ASSETSTATUS
From: MAXIMO@yahoogroups.com [mailto:MAXIMO@yahoogroups.com] On Behalf Of hernán rincón
Sent: 22 January 2014 15:05
To: MAXIMO@yahoogroups.com
Subject: Re: [MAXIMO List] Report Down Time
All:
please could you help me by telling me the name of the table or tables where is stored the data related with the option Report Down Time in Workorder module.
thank you
GDF SUEZ E&P UK Ltd (Company Number 3386464), registered in England and Wales with a registered office address at: 40 Holborn Viaduct, London, EC1N 2PB.
**************************************************************************************************************
This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed.
If you have received this email in error please notify the system manager.
**************************************************************************************************************