App-po-14160 Document Action Not Completed Successupd Fully 〈No Login〉

The Oracle E-Business Suite error "APP-PO-14160: Document action not completed successfully" occurs when attempting to control a document (e.g., cancel, close) that is in an incompatible status, such as "In Process," "Frozen," or "Incomplete". Solutions include clearing stuck receiving transactions, updating the charge account, or utilizing SQL scripts to reset the document status. For more details, visit Oracle Community .

Remember: This error is a symptom, not the disease. Treat the underlying cause—whether it’s an inactive vendor, a closed PO, or a missing approval flag—and your procurement workflow will return to normal.

Missing sequences, stuck workflow attributes, or orphaned rows in the PO_INTERFACE_ERRORS or workflow tables.

Ensure its status is active and processing. If it is deactivated, restart it. Step 3: Run Oracle Diagnostics Scripts app-po-14160 document action not completed successfully

Apply the latest Oracle Purchasing cumulative rollup patches, as many instances of this error stem from known software bugs that Oracle has already resolved.

What is the current of the PO? (e.g., Approved, In Process, Rejected) Are you using Encumbrance Accounting or funds reservation?

: Consult My Oracle Support (MOS) for specific notes related to your EBS version. Quick Troubleshooting Steps APP-PO-14160: Document Action Not Completed Successfully Remember: This error is a symptom, not the disease

You can query the backend tables to see if the document status matches the workflow status. Use this query to inspect the document state:

When using encumbrance accounting or funds reservation, documents can become trapped in a temporary status state (e.g., "In Process" or "Pre-Approved"). If an approver rejects a document or an automated system event drops mid-execution, the document flags remain active in the background, making it incompatible with a manual "Cancel" command from the frontend. Step-by-Step Resolution Strategies Resolution 1: Verify and Re-Enable Accounting Segments

Keep an eye on the Document Approval Manager to ensure it does not become bottlenecked during peak business hours. Ensure its status is active and processing

To fix this issue, you must move past the generic form error and look at the underlying system logs and workflow status. Step 1: Check the Document Approval Status

Oracle provides built-in diagnostics for purchasing documents.