Apppo14160 Document Action Not Completed Successfully Hot [patched] May 2026

To resolve the APP-PO-14160 error, follow these diagnostic steps:

: In some versions of Oracle EBS, this error is a known bug (e.g., related to Blanket Releases). Oracle often addresses these through specific patches, such as those mentioned in MOS Note: 1912083.1 . Troubleshooting Steps

: If the PO is tied to a requisition, check that the line_location_id correctly maps between the PO and the requisition lines.

: Issues often arise when the PO originated from an internal requisition, and there is a mismatch between the line_location_id and the request lines.

: Ensure the document is in a valid state for the action you want to perform. For example, a document must usually be "Approved" before it can be "Cancelled."

: If the issue persists, your system administrator may need to apply a patch or run a diagnostic script to identify and repair orphaned records in the database. Summary Table Error Code Primary Action Involved Likely Solution APP-PO-14160 Cancel, Close, Approve Check GL account status or apply Oracle patch. APP-14016 General Control Action Verify document status is compatible with action. APP-14230 GL Date Entry Ensure date falls within an open GL period.

: If the charge account associated with the PO lines has been disabled or is inactive in the General Ledger (GL), the system will prevent further document actions.

Are you seeing this error while a specific PO, or is it happening across all documents ? APP-PO-14160: Document Action Not Completed Successfully

The core message indicates that the system is unable to finalize the requested change because the current status of the document or its underlying data is incompatible with the action. Common Causes for APP-PO-14160

The error is often a symptom of underlying data inconsistencies or configuration issues. According to discussions on Oracle Communities and Spiceworks , the following are frequent triggers: