App-po-14160 Document Action Not Completed Successfull ^new^y Jun 2026

: In Oracle EBS, if an approver or a buyer has left the company and their user account or employee record has been disabled, any document awaiting their action may become stuck. When another user attempts to act on their behalf, the system may block the action due to a missing or invalid approver record.

No. It is an application logic error. Your database is likely fine; the application is rejecting the request because business rules are not met.

: In advanced configurations, the system's approval workflow may require specific cost object approvals before moving forward. If a particular cost object lacks an assigned approver, the system might skip an approval step or throw a document action error when the process doesn't follow the expected path. app-po-14160 document action not completed successfully

Ensure its status is and that the actual number of running processes matches the target number. If it is inactive, restart it. 5. Review the Budget and Encumbrance Status If your organization enforces strict budgetary controls: Open the PO in the Purchase Orders form. Click on Tools > Check Funds .

To prevent the APP-PO-14160 error from recurring in your Oracle EBS environment: : In Oracle EBS, if an approver or

The charge account associated with the PO distribution might be inactive, invalid, or closed, preventing the final closing process.

Select the or specific PO diagnostic scripts (like po_diagnostics.sql via Oracle Support). It is an application logic error

If the document action error is masking an underlying account generation failure:

If the internal requisition has been cancelled, the PO might need to be "Final Closed" rather than "Cancelled." Step E: Review Known Issues and Patches

: You may be trying to cancel a Purchase Order (PO) or Blanket Release that is in a status where that action isn't allowed, such as a PO originating from an internal requisition.