: In some versions of Oracle EBS R12, this is a known bug related to PSA (Public Sector Advanced) components, often requiring specific patches like Patch 14563642 (refer to Oracle Support Note: 1912083.1). Oracle Communities Troubleshooting & Solutions Check Transaction Status Navigate to Receiving > Transaction Status Summary
Navigate to .
The error is a common validation message in Oracle E-Business Suite (EBS) Purchasing. It occurs when a user attempts to perform a document control action—such as cancelling , closing , or finally closing a Purchase Order (PO) or Blanket Release—that the system deems incompatible with the current state of the document . Common Causes for APP-PO-14160
Keep an eye on the Document Approval Manager to ensure it does not become bottlenecked during peak business hours. app-po-14160 document action not completed successfully
If the functional checks above do not resolve the issue, data corruption or a stuck workflow process is likely the culprit. Technical teams can use the following methods to clear the error. Method A: Run the "Resubmit PO Approval" Script
If the cause is a desynchronization between archived versions and active PO data, you can bypass the block by forcing Oracle to re-index the document:
When a Purchase Order is automatically generated from an or standard requisition, its lifecycle is strictly bound to that source. If the parent internal requisition line is locked, stuck in a separate approval workflow, or has mismatched line allocations ( LINE_LOCATION_ID mismatches between PO and Requisition), actions like cancellation are halted. 4. Stuck Approval Workflows (Encumbrance Mismatches) : In some versions of Oracle EBS R12,
Query the problematic document in the screen.
Open the affected Purchase Order via the entry form.
When a document gets permanently stuck in a "Looping" or "In Process" state, Oracle provides a standard data fix script known as poxonpo.sql (for Purchase Orders) or porqonrq.sql (for Requisitions). It occurs when a user attempts to perform
to see where the document is currently sitting in the workflow. If it is stuck "In Process," it may need a reset. Oracle Communities 2. Clear Stuck Transactions If the issue occurs during cancellation or returns: Navigate to Receiving > Transaction Status Summary Query the problematic PO. Delete any stuck records and save. Try the document action again. 3. Reset the Document Status
The most common culprit is a broken or stuck approval workflow. If the approval chain has changed (e.g., a manager has left the company or an approval rule is misconfigured), the system cannot route the document to the next approver, resulting in this generic failure.
TECH-PO-14160-R1 Applies to: Oracle Purchasing (PO), Oracle E-Business Suite (R12.x & 11i) Symptoms: Error pop-up when attempting to approve, create, or update a purchase order.
