App-po-14160 Document Action Not Completed Success__link__ Fully Access

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.

• Contact that user and ask them to close their session or save/exit the PO.
• If the user is unavailable or the lock is orphaned (e.g., their session crashed), an administrator can force-release the lock via backend SQL or a system utility.

• Open the PO in “Edit” mode if possible.
• Fill in all required custom fields.
• Replace any invalid vendor or account codes.
• Save as Draft, then retry the desired action.

This should generally be done in a test environment first and may require a patch mentioned in My Oracle Support Note 390023.1 4. Apply Recommended Patches app-po-14160 document action not completed successfully

1. Keep workflow components patched – Apply latest PO and WF cumulative patches.
2. Regularly purge old workflows – Use Workflow Purge program to prevent table bloat.
3. Train users – Ensure they complete all mandatory fields (e.g., Supplier, Ship-to, Bill-to) before approving.
4. Run validation reports – Before mass updates, run the Purchase Order Validation Report to catch inconsistencies.

4. Improved observability and tracing