App-po-14160 Document Action Not Completed Success|best| Fully May 2026

"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

: Ensure that all General Ledger (GL) codes and charge accounts associated with the PO are active and enabled. Clear Stuck Transactions : Navigate to the Transaction Status Summary app-po-14160 document action not completed successfully

6. Suggested immediate mitigations (triage)

• **FND_LOG_MESSAGES** table for the related transaction ID.
• Application server logs (access log, error log).

• Regular Workflow Audits: Periodically review approval rules and hierarchy to ensure no missing approvers.
• Data Cleansing: Maintain clean supplier, item, and contract data. Use validation rules on PO entry forms.
• User Training: Ensure buyers understand not to modify POs after receipt or invoicing unless using formal change orders.
• Budget Monitoring: Set up alerts for low funds to avoid failed document actions.
• Test Before Upgrades: Any system update or custom integration should include regression testing for PO actions.

Proven Solutions to Fix "App-PO-14160"

: 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 **FND_LOG_MESSAGES** table for the related transaction ID

6. Integration or API Failures

Follow these steps to diagnose and resolve the issue: app-po-14160 document action not completed successfully