Maximo Open Forum

It is possible if you change the status of these work orders from the list screen. Or maybe that the user used MXLoader.

You can restore these work orders by using SQL DB Update:

• Update the status back to WAPPR and set the HISTORYFLAG to 0
  • UPDATE workorder SET status = 'WAPPR', HISTORYFLAG = 0 WHERE status = 'CAN' AND changedate between <startdate> and <enddate> AND changeby = <userid>;
• If possible, delete the WOSTATUS record too
  • DELETE wostatus WHERE status = 'CAN' AND changedate between <startdate> and <enddate> AND changeby = <userid>;

Hi @Tedi Kacerja!

You can close 800 WO because you change the status in the list view. But Maximo will warn you (you will get a message like the one below)

Thanks @Viet Tran and @Martin Fabra for your answer it really helped me. I was missing the HISTORYFLAG.

Now I have another issue even after rollbacking to previous status from 'CAN' , updating history flag to 0, updating the statusdate record from work order the following error appears:
We also deleted the CAN record from WOSTATUS, but the error still  occurs.
As per my checks there were no duplicates for this WO.

Can you try deleting the record in the AssetHierarchy table which is linked to this work order to see if it helps?

DELETE assethierarchy WHERE assetnum = '3038026' AND wonum = 'UP1003852' AND siteid = 'OSHEE';

I tried deleting the record in the AssetHierarchy table, but still the same error occurs. Maybe we should also delete the record from AssetHistory table ? Thank you

Ah, yes, that's another one you'll have to clean up too.

Hi @Tedi Kacerja!

If you have already updated WORKORDER with historyflag = 0 and status = WAPPR.

If you have already deleted the last WOSTATUS record.

You would need to do the following:

-update workview set historyflag = 0, status = 'WAPPR' where recordkey = 'UP1003852'
- delete assethierarchy where wonum = 'UP1003852'

I've tested it locally and it worked for me. In case that doesn't work for you, it's likely that when canceling each WO, Maximo is saving information somewhere else. You'll have to activate DEBUG and check what it's doing.

Regards!