| Document Status | Permitted Actions | Blocked Actions (Will Cause APP-PO-14160) | | :--- | :--- | :--- | | | Enter/Update data, Save | Approve, Submit for approval, Forward, Close | | In Process | View status, Withdraw (if allowed) | Submit for approval, Reject (unless approver), Modify | | Approved | Create change order, Cancel (if allowed) | Modify original line details (except via change order) | | Rejected | Update/correct data, Resubmit | Approve, Forward | | Closed/Finally Closed | View, Inquire | Update, Cancel, Reopen, Submit for approval |
In the Workflow Status Monitor, select the errored workflow line. Click the button.
A procurement manager repeatedly received "app-po-14160 document action not completed successfully" when trying to approve a $50,000 PO for raw steel. app-po-14160 document action not completed successfully
When you see the error message text: Cause: You attempted to perform a document action that is incompatible with the document status , the system is protecting downstream transactional integrity. The block usually stems from one of four data or account mismatches: 1. Inactive Accounting Key Flexfields
If another user or background process is modifying the same document simultaneously, the system may lock the record. The app-po-14160 error can appear when a process tries to update a PO that is currently locked. | Document Status | Permitted Actions | Blocked
If you are currently troubleshooting this error on a specific document, let me know: Is this happening to a or a Requisition ?
If data corruption prevents the document from progressing, Oracle Support provides standard scripts (such as porvdoc.sql or poxreapr.sql depending on your version) to safely reset the document status back to "Incomplete" or "Requires Reapproval." When you see the error message text: Cause:
This error is more than just a generic failure. It is a specific stop signal indicating that the SAP PO Advanced Adapter Engine (AAE) or the Integration Engine could not process a document (usually an IDoc or XML message) through the defined integration flow. It acts as a catch-all for several underlying issues ranging from incorrect mapping to severe channel misconfigurations.
If your organization uses budgetary control, the "document action" (e.g., increasing the PO amount) might fail if sufficient funds are not available. Some systems return a generic error instead of a specific budget message.
If you are using for PO 7.5+ iFlows, use the Exception Subprocess .
Sometimes, a database patch or compile issue causes the code responsible for document actions to fail. Run this query in your SQL tool to check for invalid objects related to purchasing actions: