App-po-14160 Document Action Not Completed Successfull ((hot))y Info
For Purchase Orders, Oracle Support recommends running the script (or the updated equivalent for your EBS version). For Requisitions, use porstoc.sql .
: Ensure the GL accounts used are currently active and have not expired.
When a document's database status and its user interface status are out of sync due to a workflow delay: app-po-14160 document action not completed successfully
Go to the and search for the Item Type (use PO Approval for Purchase Orders or PO Requisition Approval for Requisitions). Enter the Document Number as the User Key.
Most APP-PO-14160 errors are tied to a failed workflow background process. Log in with the responsibility. For Purchase Orders, Oracle Support recommends running the
Check the field. Is it In Process , Pre-Approved , or Requires Reapproval ?
While not every occurrence can be prevented, a disciplined approach to data entry and system management can significantly reduce the frequency of this error. When a document's database status and its user
Sometimes, this is caused by known bugs in older versions of EBS, which are typically resolved by applying patches. 2. Common Scenarios for APP-PO-14160
: Most operational occurrences of this error stem from users attempting to perform actions on documents in an incompatible status. Regular training on the purchasing document lifecycle—emphasizing which actions are allowed at which status—can dramatically reduce these errors. Users should understand the difference between "Incomplete," "Approved," "Rejected," and "Closed" statuses.
Longer-term fixes and preventive measures