Zavřít nabídku
The error APP-PO-14160: Document action not completed successfully typically occurs in Oracle E-Business Suite when a user attempts to perform a control action (like canceling or finally closing) on a document whose current status or underlying data prevents that action. Common Causes & Solutions
Incompatible Document Status: The most frequent cause is trying to perform an action (e.g., "Cancel PO") that is not allowed for the document's current state (e.g., it is already "Fully Received" or has "In Process" approval).
Check: Use the Purchase Order Summary form to verify the current status of the document.
Stuck Receiving Transactions: Unprocessed or stuck transactions in the receiving interface can block control actions.
Check: Navigate to Receiving > Transaction Status Summary to see if any records are stuck for that PO. Clearing these records often resolves the block.
Inactive Accounts: The error can trigger if the charge account associated with the PO line is no longer active or enabled. Check: Verify the account status in the General Ledger.
Known System Bugs: This error is sometimes linked to specific Oracle bugs that require patches (e.g., Note 1912083.1).
Check: Consult My Oracle Support (MOS) for specific notes related to your EBS version. Quick Troubleshooting Steps APP-PO-14160: Document Action Not Completed Successfully
The error APP-PO-14160: Document action not completed successfully typically occurs in Oracle E-Business Suite when a user attempts to perform a control action (like cancelling or closing) on a Purchase Order or Blanket Release that is in an incompatible status. Common Causes app-po-14160 document action not completed successfully
Incompatible Status: You are trying to cancel or close a document that is already in a state (e.g., Incomplete, Pre-Approved, or Partially Received) that prevents the action.
Disabled Accounts: The charge account associated with the PO lines may have been disabled or is no longer active in the General Ledger.
Stuck Transactions: Records might be stuck in the "Transaction Status Summary" interface, preventing further actions on the PO shipments.
Known Bugs: There are specific bugs related to this error code that may require applying patches, such as PSA RPC Patch 14563642. Recommended Solutions
Check Document Status: Ensure the PO is in a status that allows the action. For example, to cancel a PO, it generally needs to be in Approved or Open status.
Verify GL Accounts: Navigate to the PO distributions and confirm that the Charge Account and Accounting Date are still valid and within an open encumbrance period. Clear Interface Tables: Navigate to Receiving > Transaction Status Summary. Query the problematic PO. Delete any stuck records and save.
Run Workflow Processes: If the document is stuck in "Pending Approval," run the Workflow Background Process for the "PO Approval" item type to clear deferred activities.
Review Oracle Support: Consult Note: 1912083.1 on My Oracle Support for specific patches if the error persists across multiple documents. APP-PO-14160: Document Action Not Completed Successfully Q3: Can I ignore the error and force the action
The error "app-po-14160: Document action not completed successfully" is a generic but frustrating Oracle EBS failure that usually points to a data inconsistency in the purchasing workflow [1, 2]. Why this happens
This error typically occurs when the system cannot move a document (like a Purchase Order or Requisition) to the next status. Common culprits include:
Stuck Workflows: The background process for approvals has stalled or errored out [2, 3].
Inconsistent Data: The document status in the header doesn't match the status in the action history [1, 4].
Missing Setup: A change in the approval hierarchy (like a deleted user or missing supervisor) has left the document with nowhere to go [3]. How to fix it
Check Workflow Status: Run the "Workflow Background Process" for the PO Approval item type. This often pushes "stuck" documents through [2, 3].
Verify the Approval Hierarchy: Ensure the requester and the next approver in the chain are active and have the correct job/position assignments [3, 4].
Data Cleanup (DBA Level): If the workflow is fine, a developer may need to check the PO_HEADERS_ALL table. If the AUTHORIZATION_STATUS is 'IN PROCESS' but there are no active workflow activities, the status may need to be reset via a data fix script [1, 4]. Ask users if someone else is editing the same PO
Review System Logs: Check the FND Log at the time of the error for more specific details, such as a "Unique Constraint" or "Null Value" error hidden behind the generic message [5].
A: No. Ignoring it or using backend SQL to force a status change can break financial integrations, duplicate POs, or cause invoice mismatches.
Encountering error codes in enterprise software can be a major roadblock, especially when they interrupt critical procurement workflows. One such cryptic but increasingly common error is "app-po-14160 document action not completed successfully."
If you have landed on this article, you are likely staring at this red-lettered alert in your procurement or ERP system, wondering what went wrong and how to fix it fast. This error typically appears in Oracle Procurement Cloud, E-Business Suite (EBS), or similar enterprise resource planning systems when users attempt to perform an action on a Purchase Order (PO)—such as approving, updating, canceling, or creating a change order.
In this detailed guide, we will dissect the root causes of the app-po-14160 error, provide step-by-step troubleshooting methods, explain how to prevent it in the future, and outline when to escalate to technical support.
A: The error is deterministic. If it worked before, something changed—either the PO’s state, your permissions, or a related master data element (like a vendor or account code).
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.