The error APP-PO-14160: Document action not completed successfully typically occurs in Oracle Purchasing (E-Business Suite) when you attempt to perform a control action—like Cancelling or Finally Closing—that is prohibited by the document's current state. Common Causes
The Approval Loop: The document is stuck in a "Pre-Approved" or "In Process" status because the next person in the hierarchy doesn't have enough signing authority or isn't assigned a proper position. app-po-14160 document action not completed successfully
If you have backend access, running these checks can pinpoint the root cause: | | Security & Access | The user
| Category | Typical Root Cause |
| :--- | :--- |
| Workflow Issues | The Purchasing Document Approval Workflow (POAPPRV) is stuck, corrupted, or missing an approver. |
| Security & Access | The user lacks APPROVE or MODIFY privileges on the Operating Unit or Document Type. |
| Data Corruption | Missing or invalid data in PO_HEADERS_ALL (e.g., blanket_total_amount = 0 when required). |
| Hold or Control | A financial hold (e.g., encumbrance, budget) or a document control status (e.g., "Incomplete") blocks the action. |
| Integration Conflict | Another process (e.g., AME, Cloning) has locked the document row. | |
| Integration Conflict | Another process (e
: If the document was modified but not archived, you may need to undo those changes before the system allows a "Cancel" action. Review My Oracle Support (MOS) Notes Note 1912083.1 if the error occurs during Blanket Release. Note 390023.1
In some versions (like R12), this error is a known bug associated with Oracle Note 1912083.1 Oracle Communities Troubleshooting & Resolution Guide 1. Verify Account and Document Status Check Accounts:
Check Charge Accounts: Ensure the GL accounts used are currently active and have not expired.