App-po-14160 Document Action Not Completed Successfully ((install)) – Direct Link

: In some versions (like R12.1), this error can be caused by known bugs. Oracle Support often recommends checking specific notes (e.g., Note: 1912083.1) or applying specific RPC patches (e.g., Patch 14563642). Spiceworks Community Recommended Solutions Check Accounting Periods

Unprocessed receiving transactions or "stuck" records in the Transaction Status Summary form can prevent document actions from completing.

When multiple users or background jobs try to modify the same PO record simultaneously, the database may place a lock. The application attempts the action but receives a "timeout" or "resource busy" signal, which it translates into error 14160.

If found, these records must be resolved or deleted before the system allows a "Finally Close" or "Cancel" action. 4. Address Bug-Specific Issues (Note 1912083.1)

Log in to My Oracle Support and search for .

a general exception in Oracle E-Business Suite (Purchasing) indicating that the system cannot proceed with a specific document control action (such as Finally Close

Is the charge account active? Re-enable the account if it was disabled.