MAM 7.6.1.2:

I have an approved WO that has a task. The task has:

• An approved labor actual with non-zero hours
• Inherit Status Changes=Yes

I can go ahead and cancel the WO, since the WO doesn't have any approved labor actuals with non-zero hours:




However, when I look at the cancelled WO, I'm surprised to see that the task is still APPR.



If anything, I would have thought one of the following would have happened:

1. Maximo would prevent me from cancelling the WO, because the task has an approved labor actual with non-zero hours.
2. Or, Maximo would cancel the task too, despite the fact that it has an approved labor actual with non-zero hours.

It's unintuitive to me that Maximo cancelled the WO but left the task as APPR. Especially since the task is set to Inherit Status Changes=Yes.
I know there are rules about cancelling WOs (tasks are technically WOs), but I can't imagine why we'd want an approved task while the main WO is cancelled.

Is that expected behavior?

Thanks.
#AssetandFacilitiesManagement
#Maximo

This sounds like a bug.  Have you opened a case?  There is no plausible business construct from a cost accounting perspective that should allow the tool to provide this kind of situation.  What other parameters do you have in place that might account for this?  Do you have any customizations or even automation scrips that play with status at all?  If you do then I would disable them and test this again.  If you can duplicate this is a Maxdemo test environment then this is not right..

------------------------------
Bradley K. Downing , MBA
Solutions Engineer
IBM
Bakersfield CA
------------------------------

Original Message:
Sent: Thu December 09, 2021 06:37 PM
From: User1971
Subject: Cancelling WO doesn't cancel task (with approved labor actual; non-zero hours)

MAM 7.6.1.2:

I have an approved WO that has a task. The task has:

• An approved labor actual with non-zero hours
• Inherit Status Changes=Yes

I can go ahead and cancel the WO, since the WO doesn't have any approved labor actuals with non-zero hours:




However, when I look at the cancelled WO, I'm surprised to see that the task is still APPR.



If anything, I would have thought one of the following would have happened:

1. Maximo would prevent me from cancelling the WO, because the task has an approved labor actual with non-zero hours.
2. Or, Maximo would cancel the task too, despite the fact that it has an approved labor actual with non-zero hours.

It's unintuitive to me that Maximo cancelled the WO but left the task as APPR. Especially since the task is set to Inherit Status Changes=Yes.
I know there are rules about cancelling WOs (tasks are technically WOs), but I can't imagine why we'd want an approved task while the main WO is cancelled.

Is that expected behavior?

Thanks.
#AssetandFacilitiesManagement
#Maximo

Hi Bradley,

Thanks for your input. Good point...I did some more testing, and I was able to reproduce the issue in the Maximo Preview Site:



So unless I'm having a brain fart (entirely possible) I believe this is an issue with Maximo.
I'd submitted a IBM Support case, and got this response this morning:

TS007779764
"If the parent work order has been cancelled and in your case the task work order has labor associated Maximo will allow the parent work order to be cancelled. The connection to the parent and task work order is still there. If there are any actuals reported against a work order if you click on Change status you will not be presented with the cancel option."

It sounds like they're confirming the behavior I've observed. But I agree with you...from my perspective, that's not how it should work.

Any thoughts on how to proceed?
Original Message:
Sent: Fri December 10, 2021 10:39 AM
From: Bradley Downing
Subject: Cancelling WO doesn't cancel task (with approved labor actual; non-zero hours)

This sounds like a bug.  Have you opened a case?  There is no plausible business construct from a cost accounting perspective that should allow the tool to provide this kind of situation.  What other parameters do you have in place that might account for this?  Do you have any customizations or even automation scrips that play with status at all?  If you do then I would disable them and test this again.  If you can duplicate this is a Maxdemo test environment then this is not right..

------------------------------
Bradley K. Downing , MBA
Solutions Engineer
IBM
Bakersfield CA

Original Message:
Sent: Thu December 09, 2021 06:37 PM
From: User1971
Subject: Cancelling WO doesn't cancel task (with approved labor actual; non-zero hours)

MAM 7.6.1.2:

I have an approved WO that has a task. The task has:

• An approved labor actual with non-zero hours
• Inherit Status Changes=Yes

I can go ahead and cancel the WO, since the WO doesn't have any approved labor actuals with non-zero hours:




However, when I look at the cancelled WO, I'm surprised to see that the task is still APPR.



If anything, I would have thought one of the following would have happened:

1. Maximo would prevent me from cancelling the WO, because the task has an approved labor actual with non-zero hours.
2. Or, Maximo would cancel the task too, despite the fact that it has an approved labor actual with non-zero hours.

It's unintuitive to me that Maximo cancelled the WO but left the task as APPR. Especially since the task is set to Inherit Status Changes=Yes.
I know there are rules about cancelling WOs (tasks are technically WOs), but I can't imagine why we'd want an approved task while the main WO is cancelled.

Is that expected behavior?

Thanks.
#Maximo
#AssetandFacilitiesManagement

Interesting......  That sounds to me like a change has been made.  I will have to look into this.  I have always held that a work order should not be cancelled if it had costs but rather it should be closed.  The idea being that BECAUSE it had costs it should be closed.  Cancelling work implies the work never occurred to begin with.  Closing indicates the work effort was ended (whether completed or not.)  I would venture to say that perhaps IBM introduced flexibility into this so as to allow different organizations to interpret this view differently (???) I did take a look at the AssetCostRollup report.  That report indeed does allow for transactions that are associated to work in a CAN status.  I never knew that.  So this a) may have always been that way and I am just ignorant, or b) there was a change on this to again allow different organizations to behave differently.  I have always thought that you CANNOT cancel work with associated costs.  I am wrong, but I believe Maximo used to not allow this at all.  Again, I could be wrong on this point as well.

------------------------------
Bradley K. Downing , MBA
Solutions Engineer
IBM
Bakersfield CA
------------------------------

Original Message:
Sent: Fri December 10, 2021 11:29 AM
From: User1971
Subject: Cancelling WO doesn't cancel task (with approved labor actual; non-zero hours)

Hi Bradley,

Thanks for your input. Good point...I did some more testing, and I was able to reproduce the issue in the Maximo Preview Site:



So unless I'm having a brain fart (entirely possible) I believe this is an issue with Maximo.
I'd submitted a IBM Support case, and got this response this morning:

TS007779764
"If the parent work order has been cancelled and in your case the task work order has labor associated Maximo will allow the parent work order to be cancelled. The connection to the parent and task work order is still there. If there are any actuals reported against a work order if you click on Change status you will not be presented with the cancel option."

It sounds like they're confirming the behavior I've observed. But I agree with you...from my perspective, that's not how it should work.

Any thoughts on how to proceed?
Original Message:
Sent: Fri December 10, 2021 10:39 AM
From: Bradley Downing
Subject: Cancelling WO doesn't cancel task (with approved labor actual; non-zero hours)

This sounds like a bug.  Have you opened a case?  There is no plausible business construct from a cost accounting perspective that should allow the tool to provide this kind of situation.  What other parameters do you have in place that might account for this?  Do you have any customizations or even automation scrips that play with status at all?  If you do then I would disable them and test this again.  If you can duplicate this is a Maxdemo test environment then this is not right..

------------------------------
Bradley K. Downing , MBA
Solutions Engineer
IBM
Bakersfield CA

Original Message:
Sent: Thu December 09, 2021 06:37 PM
From: User1971
Subject: Cancelling WO doesn't cancel task (with approved labor actual; non-zero hours)

MAM 7.6.1.2:

I have an approved WO that has a task. The task has:

• An approved labor actual with non-zero hours
• Inherit Status Changes=Yes

I can go ahead and cancel the WO, since the WO doesn't have any approved labor actuals with non-zero hours:




However, when I look at the cancelled WO, I'm surprised to see that the task is still APPR.



If anything, I would have thought one of the following would have happened:

1. Maximo would prevent me from cancelling the WO, because the task has an approved labor actual with non-zero hours.
2. Or, Maximo would cancel the task too, despite the fact that it has an approved labor actual with non-zero hours.

It's unintuitive to me that Maximo cancelled the WO but left the task as APPR. Especially since the task is set to Inherit Status Changes=Yes.
I know there are rules about cancelling WOs (tasks are technically WOs), but I can't imagine why we'd want an approved task while the main WO is cancelled.

Is that expected behavior?

Thanks.
#Maximo
#AssetandFacilitiesManagement