Use transaction SM12 to display and delete locks. Select the table containing your PO number and remove the lock entry.
The error is a generic symptom of an underlying failure within Oracle EBS Purchasing. By systematically checking the Workflow Status Monitor , verifying HR hierarchies , ensuring periods are open , and reviewing Document Managers , you can quickly isolate the true root cause and restore your procurement operations.
Rarely, but yes. Some aggressive web filters or script blockers prevent the ERP’s JavaScript from running fully. Temporarily disable such extensions to test.
Understanding and Fixing Oracle EBS Error: APP-PO-14160 Document Action Not Completed Successfully app-po-14160 document action not completed successfully
The PO Approval workflow failed or is stuck in an error state.
If you are currently troubleshooting this issue, tell me (Requisition or PO) is throwing the error and if you have access to the Workflow Status Monitor . I can guide you through the exact steps to find the underlying error log. Share public link
Regularly monitor the WF_ITEMS and WF_ITEM_ATTRIBUTE_VALUES tables for stuck workflows. Use transaction SM12 to display and delete locks
If the basic steps fail, administrators will need to dig deeper. The following solutions assume you have access to backend logs, database query tools, or system configuration panels.
: If you are following the standard process and the error persists, report it to Oracle Support as it may require a specific system patch. APP-PO-14160: Document Action Not Completed Successfully
Use database or application commands to kill stale locks: By systematically checking the Workflow Status Monitor ,
To minimize the occurrence of APP-PO-14160 errors in your daily operations, implement these proactive measures:
The PO was linked to a vendor who had been marked "Inactive" the previous day by the AP team. The approval workflow had a validation rule: "Cannot approve PO for inactive vendor."
