Maximo Open Forum

Reopening WO and POs comes up a decent amount and there's not a supported way to do either. There's lots of problems that can occur, such as the WO referenced on the PO is now closed, contract limits are hit, assets are no longer active, the PO has already been invoiced, etc. I wouldn't encourage reopening and if I absolutely needed to do it, I'd make it a manual process that went through a thorough review before updating via the backend. 

I recommend POs/WOs are left open and closed by an automated process once you know they're complete (receipts are complete and no activity in X number of days for example). That helps alleviate the user driven activity causing issues. It's not perfect, but should hopefully minimize how often there's a problem.

Reopening WO and POs comes up a decent amount and there's not a supported way to do either. There's lots of problems that can occur, such as the WO referenced on the PO is now closed, contract limits are hit, assets are no longer active, the PO has already been invoiced, etc. I wouldn't encourage reopening and if I absolutely needed to do it, I'd make it a manual process that went through a thorough review before updating via the backend. 

I recommend POs/WOs are left open and closed by an automated process once you know they're complete (receipts are complete and no activity in X number of days for example). That helps alleviate the user driven activity causing issues. It's not perfect, but should hopefully minimize how often there's a problem.

For me, the concern with reopening is whether the data is in a valid state to work or are you just causing additional issues that you have to "fix" so you can reopen it? For example, item/inventory status on some lines may now be obsolete and you can't revise the PO so now you need to backend update those records (since you can't go back from Obsolete). The asset referenced might have been moved to another site so now you need to trick the system to think the asset still resides in the site or move it back. The WO is closed so you now need to reopen the WO as well. GL Accounts might be expired so you now need to reactivate those GL accounts. The list is pretty long as to what issues you could encounter. 

If you're purely worried about how to reopen a PO (without any concerns about the data issues), you just have the status and historyflag attributes to worry about. If you SQL updated the PO to set those back to status=APPR for status (or whatever the last status was) and historyflag=0 for example, you would have "reopened" the PO. Some people might delete the status entry in POSTATUS but I disagree with that strongly. I think it's important to see that it was closed and I would add an entry to POSTATUS to indicate that it was reopened and why. 

Reopening a WO is similar but depending on organization settings, additional cleanup might be required (such as deleting assethistory & assethierarchy records). WOs we have support for editing after they're closed (adding new labor transactions for example) and that history edit should be utilized whenever possible. Deleting things like ASSETHISTORY and having them recreated has impact on asset cost information if asset hierarchies have changed. 

Reopening WO and POs comes up a decent amount and there's not a supported way to do either. There's lots of problems that can occur, such as the WO referenced on the PO is now closed, contract limits are hit, assets are no longer active, the PO has already been invoiced, etc. I wouldn't encourage reopening and if I absolutely needed to do it, I'd make it a manual process that went through a thorough review before updating via the backend. 

I recommend POs/WOs are left open and closed by an automated process once you know they're complete (receipts are complete and no activity in X number of days for example). That helps alleviate the user driven activity causing issues. It's not perfect, but should hopefully minimize how often there's a problem.