Capture the following before deeper troubleshooting:
APP-PO-14160 Appears When Modifying or Canceling Purchase Orders .
If your accounts are fully functional and no open invoices exist, you are likely encountering an application bug. Oracle has documented specific resolutions depending on your EBS version: apppo14160 document action not completed successfully hot
Check code combinations for inactive segments or closed periods. Error on Blanket Release Approval Oracle EBS Core Code Defect Reference MOS Note 1912083.1 and evaluate Patch 14563642.
on My Oracle Support to see if your system version requires a patch (such as the PSA RPC Patch) to resolve this specific bug. Oracle Communities Are you currently trying to a specific Purchase Order when this error appears? APP-PO-14160: Document Action Not Completed Successfully 18 Jun 2020 — Error on Blanket Release Approval Oracle EBS Core
With systematic logging analysis and resource checks, most instances of APPPO14160 can be resolved within 30–60 minutes. If it becomes chronic, consider re-architecting the document action queue to use a distributed lock manager (e.g., Redis, ZooKeeper) instead of relying on application-level locks.
When two processes try to modify the same document or related table at the same time, a lock occurs. The "hot" nature of the transaction means the system does not wait long enough for the lock to release, resulting in immediate failure. Use code with caution.
: Run scripts or diagnostic tests to ensure the line_location_id on the PO matches the corresponding requisition lines.
SELECT po_header_id, line_location_id, closed_code, cancel_flag FROM po_line_locations_all WHERE po_header_id = :your_po_header_id; Use code with caution.