: If the charge account associated with the PO line has been disabled in the General Ledger (GL), the system may fail to process the cancellation or update. Software Bug
This error typically surfaces when attempting to perform a critical document action—such as approving a purchase order (PO), releasing a hold, changing a line item, or confirming a receipt. The "app-po-14160" code points to an application-level permission or state conflict (with "PO" strongly suggesting module), while "document action not completed successfully" indicates the system’s backend validation failed.
Read the exact wording of buttons. If you see a button like “Complete Action” or “Process,” try that instead of the generic “Save” or “OK.”
If the data appears clean but the error persists, you may be facing a system bug. Reference on My Oracle Support. Common patches include: app-po-14160 document action not completed successfully
: Sometimes putting the document On Hold and then Releasing it can refresh the action history and clear minor logic glitches. 💡 Quick Tips
The error is often a "wrapper." If you look at the underlying , you might find a more descriptive sub-error. Usually, if APP-PO-14160 appears alongside a message about "Tax Calculation," the issue is actually in the E-Business Tax (eBTax) module failing to calculate a rate, which then halts the entire PO approval. Are you seeing this error on a specific document type , or AI responses may include mistakes. Learn more
Resolving the APP-PO-14160: Document Action Not Completed Successfully Error in Oracle EBS : If the charge account associated with the
As noted in the Oracle community and references to Note: 1912083.1, a known bug can trigger this error. To check for and address this issue:
Understanding APP-PO-14160: Document Action Not Completed Successfully
To minimize the odds of seeing again, implement these best practices: Read the exact wording of buttons
Many ERPs show a bell icon or notification center. Look for messages like:
Last Updated: October 2025
If you are using the RFC or IDoc adapter, the error might be due to stale metadata.