Hi All,
We found that our Maximo PO automatic closure with invoices approved/received against all PO lines (the cost matched perfectly) is not consistent.
Since day one, we have the Organization - PO Option "Enable Option to Automatically Close PO's on Invoice Approval?" checked. Most of the time, POs will get closed when invoices against all the PO lines were integrated from PeopleSoft to Maximo. However, intermittently some POs will skip that automatic closure.
For example, below PO has 5 PO lines. And all the PO lines "Receipts Complete?" are checked (we checked that all the 5 receipts were integrated into Maximo with perfect match of cost against eatch PO line). And all the Invoices also got integrated into Maximo with APPR status and perfect cost match. Normally, the PO should turn to "CLOSE" status at the moment the invoices were integrated to create in Maximo, but the PO now still remains "DISPATCHED".
We checked and compared many of both good and bad cases. No matter the PO has 1 PO line or multiple PO lines, no matter what time the invoice integration happens, we can always observe both good and bad results. And when we manually change any one of the Invoices status from APPR to PAID to trigger PO closure, it will always succeed to close the "DISPATCHED" PO with no error. So we are now in a dead end.
To address what we did more comprehensive, I will list the items we've checked below:
- PO status: The PO is in a good open status "DISPACHTED", not pending revision.
- Quantity Mismatch: The total quantity and cost perfectly matched between the PO line and the Invoice.
- Unprocessed Receipts: All receipts against all PO lines have been fully processed, the PO lines all have a checked "Receipts Complete?".
- Configuration Issues: The Organization PO option is always enabled to automatic closure of POs on invoice approval.
- Manual PO Closure: Yes, we can still manually successfully close those "DISPATCHED" POs from an invoice status change (from APPR to PAID). Or we can just manually change the PO status directly.
Does any one have the similar experience as we do? If so, can you please share your story with us?
If this is a system bug, we are reaching the end of IBM Support for Maximo 7.6. But hopefully it is already fixed in the new version, such like MAS where we are in progress to upgrade to.
Thanks very much,
Frank Meng