App-po-14160 Document Action Not Completed Successfull __top__y Jun 2026

If the error persists after checking account availability and forcing a clean document revision, look up the My Oracle Support platform and reference or apply the cumulative Procurement RPC patch bundles to fix background functional exceptions. If you would like, tell me:

Browser extensions (ad blockers, script managers) can interfere with ERP JavaScript. Use an incognito/private window or a different browser (Chrome vs. Edge vs. Firefox) to eliminate extension conflicts.

: Pending records in the Transaction Status Summary (inventory or receiving) may block control actions. app-po-14160 document action not completed successfully

The error is a generic but frustrating Oracle EBS failure that usually points to a data inconsistency in the purchasing workflow [1, 2]. Why this happens

Navigate to . Search for the PO number. Delete any error or pending records. If the error persists after checking account availability

Based on extensive troubleshooting logs and vendor documentation, the following are the verified root causes of :

If your organization uses encumbrance accounting, the error frequently triggers because the document failed funds reservation due to insufficient budget. Edge vs

Longer-term fixes and preventive measures

If the PO is in a terminal state (e.g., Closed, Canceled, Fully Invoiced) and you need to modify it:

The PO was linked to a vendor who had been marked "Inactive" the previous day by the AP team. The approval workflow had a validation rule: "Cannot approve PO for inactive vendor."