MAM 7.6.1.2:

In a previous post, we said that "we can change the WO status to CAN when there are no actuals and the status is one of the following:

• WAPPR
• WSCH
• WPCOND
• WMATL
• APPR
• (or a synonym of any of these)"

Edited (was too wordy):
I've been doing some testing, and it looks like it's slightly more complicated than that:
The CAN status is available if the WO doesn't have any approved labor actuals with non-zero hours.

Does that match your experience?


Related post here:
WO status - Only show INVALID [CLOSE] if CANCEL is unavailable

#AssetandFacilitiesManagement
#Maximo

This page hints at the rules I mentioned in the original post:
https://www.ibm.com/docs/en/cdfsp/7.6.0?topic=orders-work-order-statuses

"CAN (Canceled):

• Work orders that are not started are canceled. What does "not started" actually mean?
• Work orders that have no actuals reports are also canceled. Does "no actuals reports" mean "no approved labor actuals?
• Canceled work order become history records."

"You cannot cancel a work order if the work is already in progress or if actuals are already reported."
I suppose that's technically true, but with the UNDOAPPR sigoption, we can change the WO from INPRG to WAPPR, and then cancel the WO from there. So, as long as the WO meets the actuals rules that I mentioned in the original post, than we can cancel INPRG WOs (indirectly).

The analogy I've used in the past is Maximo is a like a lump of clay - sorta nice as is out of the box, but can be molded into something extremely useful by set of skilled hands. 

Out of box, "started" means when a non-zero value of labor hours have been recorded to a work order and processed as actual labor hours - aka lump of clay. Most companies consider "started" once the WO has been set to INPRG, some consider started only when physical work has occurred and incurred actual labor hours, while others state anytime a financial transaction has occurred against the work order (e.g. issued a part or triggered a PO). These are extensions of what IBM provides out of the box and is part of forming that lump of clay into something useful.

Best advice i have is to identify what your company considers when a WO has "started", document those business policies, and then build those policies into functional rules/requirements into Maximo - e.g. conditional requirements on status changes, additional required fields, automation scripts to give feedback to end users, etc.

------------------------------
Jason Verly
Reliability Engineering Manager
Agropur US
Le Sueur MN
------------------------------

Original Message:
Sent: Mon December 06, 2021 03:51 PM
From: User1971
Subject: Rules for cancelling WOs

https://www.ibm.com/docs/en/cdfsp/7.6.0?topic=orders-work-order-statuses
That page hints at the rules I mentioned in the original post.

"CAN (Canceled):

• Work orders that are not started are canceled. What does "not started" actually mean?
• Work orders that have no actuals reports are also canceled. Does "no actuals reports" mean "no approved labor actuals?
• Canceled work order become history records."

"You cannot cancel a work order if the work is already in progress or if actuals are already reported."
When it says "You cannot cancel a work order if the work is already in progress", I suppose that's technically true, but we can change the WO from INPRG to WAPPR, and then cancel the WO from there. So, as long as the WO meets the actuals rules that I mentioned in the original post, than we can cancel INPRG WOs.

It would be good to get some clear/thorough info on this.

One more thing... use IBM's Preview Site to test any out of the box functionality. 

https://www.ibm.com/support/pages/maximo-asset-management-761-preview-site

Generally there are zero configurations for business rules on primary objects like WO, PO, Asset, and Location. So in the case of when a WO is "started", it has to be a non-zero total of a approved actual hours. 




For my company, both transactions triggered our definition of "started" and we have a status restriction that will prevent "Cancelled" from being selected:

not exists(select null from labtrans where labtrans.refwo=:wonum and labtrans.siteid=:siteid and regularhrs is not null)​

Edit: original post had "not" cut off in the SQL example code. 

------------------------------
Jason Verly
Reliability Engineering Manager
Agropur US
Le Sueur MN
------------------------------

Original Message:
Sent: Mon December 06, 2021 03:51 PM
From: User1971
Subject: Rules for cancelling WOs

https://www.ibm.com/docs/en/cdfsp/7.6.0?topic=orders-work-order-statuses
That page hints at the rules I mentioned in the original post.

"CAN (Canceled):

• Work orders that are not started are canceled. What does "not started" actually mean?
• Work orders that have no actuals reports are also canceled. Does "no actuals reports" mean "no approved labor actuals?
• Canceled work order become history records."

"You cannot cancel a work order if the work is already in progress or if actuals are already reported."
I suppose that's technically true, but we can change the WO from INPRG to WAPPR, and then cancel the WO from there. So, as long as the WO meets the actuals rules that I mentioned in the original post, than we can cancel INPRG WOs (indirectly).

For what it's worth:

It looks like I'm able to "cancel out" an approved labor actual with non-zero hours (and non-zero costs) by adding additional actuals...that are "the opposite" .

For example, if there is a approved labor actual with a line cost of $42.79, then I can't cancel the WO. But if I add an approved labor actual with a line cost of $-42.79 (negative), then I can now cancel the WO.







That could be a handy technique for cancelling WOs that have actuals. 
Of course, it wouldn’t help us with COMP or CLOSE WOs, since COMP and CLOSE WOs can’t ever be cancelled.
#Maximo
#AssetandFacilitiesManagement