Set reminders to open GL and PO periods at least a few days before the start of a new month.
: Verify the header and shipment statuses. If the PO is "In Process," it must be reset to "Incomplete" using scripts like poxrespo.sql before further actions can be taken. Clear Stuck Transactions Navigate to Receiving > Transaction Status Summary Query the PO number to find any stuck records.
Encountering the error can be an unwelcome interruption, but it is almost always surmountable. For the business user, it serves as a helpful reminder that the system is enforcing the correct business process, preventing actions that could lead to data inconsistency. For the system administrator, it may point to a known bug that requires a simple patch application. app-po-14160 document action not completed successfully
When you first see the error, follow these steps. Most can be performed by an end user without admin rights.
: Ensure the PO is in a status that allows the action. For example, to cancel a PO, it generally needs to be in Approved or Open status. Set reminders to open GL and PO periods
: Use the Purchase Order Summary form to verify the current status of the document.
The charge account associated with the PO distribution might be inactive, invalid, or closed, preventing the final closing process. Clear Stuck Transactions Navigate to Receiving > Transaction
If functional checks do not resolve the issue, a system administrator or database administrator (DBA) must investigate the backend tables. 1. Identify Stuck Workflow Processes
If the basic steps fail, administrators will need to dig deeper. The following solutions assume you have access to backend logs, database query tools, or system configuration panels.
Select the concurrent program (or use the script poxreops.sql if provided by Oracle Support for your specific version). Enter the Operating Unit and Document Number parameters.