App-po-14160 Document Action Not | Completed Successfully ((top))

: 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

Keep your Oracle Procurement modules up to date with the latest Recommended Patch Collections (RPCs) to eliminate known bugs associated with document action packages.

What do you see in the Workflow Status Monitor? app-po-14160 document action not completed successfully

For certain Oracle errors, running specific concurrent requests can resolve underlying data inconsistencies. One documented approach for related error scenarios is to execute the request from the System Administrator responsibility. This process rebuilds certain critical data structures and has been known to resolve specific Oracle Purchasing errors.

The charge account associated with the PO distribution might be inactive, invalid, or closed, preventing the final closing process. : Ensure that all General Ledger (GL) codes

: If returning or canceling, ensure there is sufficient "On Hand Quantity" if the items have already been processed. Oracle Communities Are you currently trying to a document or finally close it when this error appears? Oracle Communities

Check the field. Is it In Process , Pre-Approved , or Requires Reapproval ? The charge account associated with the PO distribution

The error typically occurs in Oracle E-Business Suite when a user attempts to perform a control action (like canceling or finally closing) on a document whose current status or underlying data prevents that action. Common Causes & Solutions

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:

A second major cause is . Often, the workflow background engine encounters a "hanging" process. If a previous workflow activity did not complete cleanly—perhaps due to a database timeout or a locking issue—the document enters a state of limbo. Subsequent attempts to act on the document fail because the system perceives the document as currently being processed or locked by another session.

: Oracle regularly releases cumulative patches and updates. Keeping your Oracle EBS environment up-to-date, especially with patches that address known purchasing bugs, is one of the most effective preventive measures. The existence of a specific patch referenced in Note: 1912083.1 indicates that this error has been recognized and addressed by Oracle in some versions.