App-po-14160 Document Action Not Completed Successfully [patched] Jun 2026

When you see the error message text: Cause: You attempted to perform a document action that is incompatible with the document status , the system is protecting downstream transactional integrity. The block usually stems from one of four data or account mismatches: 1. Inactive Accounting Key Flexfields

If this error is occuring frequently for seemingly valid POs, it may be necessary to check with an Oracle Apps DBA for a potential data corruption or patching requirement. app-po-14160 document action not completed successfully

Fixing the "APP-PO-14160: Document Action Not Completed Successfully" Error in Oracle EBS When you see the error message text: Cause:

: While more commonly associated with other errors, if the Account Generator workflow fails to generate a required account (e.g., an accrual or variance account) for a specific document line, the document may be stuck in a state where certain actions are blocked until the account issue is resolved. Ignoring this error leads to data loss, transactional

: 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.

Ignoring this error leads to data loss, transactional inconsistencies, and frustrated business users wondering why their purchase orders or customer invoices never reached the target system.

The error 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