App-po-14160 Document Action Not Completed Successfully !!top!!

This generic error typically surfaces when a user attempts to approve, forward, reject, or submit a Purchase Order (PO) or Purchase Requisition. Because the error message itself provides very little context, troubleshooting requires a systematic approach to uncover the underlying data or workflow issue.

If the PO is in a terminal state (e.g., Closed, Canceled, Fully Invoiced) and you need to modify it:

The error typically occurs in Oracle E-Business Suite when a user attempts to perform a control action (like cancelling or closing) on a Purchase Order or Blanket Release that is in an incompatible status. Common Causes app-po-14160 document action not completed successfully

Click on or Activity History . Look for activities marked with an Error status (usually highlighted in red).

The error is deterministic. If it worked before, something changed—either the PO’s state, your permissions, or a related master data element (like a vendor or account code). This generic error typically surfaces when a user

Based on your diagnosis, apply the appropriate fix.

Here are the specific system-level factors that can contribute to a bug-driven occurrence of this error: Common Causes Click on or Activity History

Corrupt or inconsistent data in the background tables can trigger the error. This includes:

Run the "Workflow Background Process" for the PO Approval item type. This often pushes "stuck" documents through [2, 3].