App-po-14160 Document Action Not Completed Successfully -

Navigate to the read-only view of the same PO. Look for:

No. Forcing a document update bypassing validation can corrupt the PO lifecycle. Always resolve the root cause.

If the above steps do not resolve the issue, gather the following before opening a Service Request (SR):

Reference: Oracle Knowledge Document ID 438091.1 (APP-PO-14160 Troubleshooting Guide)

Final Note: While "Document action not completed successfully" is frustrating, in over 80% of cases the culprit is either a stuck workflow or a missing employee-to-user link. Systematic checking of the above layers will lead you to the resolution.

Last Updated: October 2025

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 is a message from Oracle E-Business Suite (EBS), specifically within the Purchasing (PO) module. It typically triggers when you attempt a document action (like cancelling, approving, or modifying a Purchase Order) that is incompatible with the document's current status. Common Causes and Solutions

Status Mismatch: You may be trying to cancel a Purchase Order (PO) or Blanket Release that is in a status where that action isn't allowed, such as a PO originating from an internal requisition.

Inactive Accounts: The charge account associated with the PO may no longer be enabled. app-po-14160 document action not completed successfully

Known Software Bugs: In certain versions (e.g., r12.2.12), this error can be caused by a bug. Consult My Oracle Support (MOS) regarding Note 1912083.1 to see if a patch is required.

Incomplete Documents: For documents in "Incomplete" status, users may need to Delete the document rather than cancel it.

Open Dependencies: Ensure all associated shipments, lines, or timecards are properly closed or cancelled before attempting to final-close the main agreement. Troubleshooting Steps

Verify Status: Open the document and check the "Status" field to ensure the action is valid.

Check Charge Accounts: Ensure the GL accounts used are currently active and have not expired.

Review Dependencies: Check for linked sales order lines or approved timecards that might be blocking the action.

Contact Support: 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

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

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 Navigate to the read-only view of the same PO

APP-PO-14160: Document action not completed successfully in Oracle E-Business Suite

typically occurs when a user attempts an action (such as canceling or approving) that is incompatible with the document's current status Oracle Communities Primary Causes Status Incompatibility:

The document status (e.g., "In Process", "Pre-Approved") does not support the action you are trying to perform. Disabled Accounts:

The charge account associated with the document may be inactive or disabled. Stuck Transactions:

Records related to the Purchase Order (PO) are stuck in the "Transaction Status Summary" form. Known Bugs:

In some versions (like R12), this error is a known bug associated with Oracle Note 1912083.1 Oracle Communities Troubleshooting & Resolution Guide 1. Verify Account and Document Status Check Accounts:

Ensure all charge accounts associated with the PO lines and distributions are active. Review Action History: Navigate to Tools > View Action History

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

If the document is stuck in a state that prevents further action: Use the Oracle-provided reset script, often called poxrespo.sql for POs or porreset.sql for requisitions. This script reverts the document status to Incomplete , allowing you to fix errors or resubmit for approval.

This should generally be done in a test environment first and may require a patch mentioned in My Oracle Support Note 390023.1 4. Apply Recommended Patches

Consult with your System Administrator to check for relevant patches if you are on a version susceptible to this bug: Note 1912083.1 recommends specific patches like PSA RPC Patch 14563642 for certain blanket release errors. Spiceworks Community 5. Check Workflow Errors Review the Workflow Status

to identify specific activity failures, such as "Is Document Complete?". Common failures include missing Supplier Site

details that were not entered before the document moved to "In Process". SQL queries to check for stuck records in your database tables? APP-PO-14160: Document Action Not Completed Successfully

The error code APP-PO-14160: Document action not completed successfully is a common validation error in Oracle E-Business Suite (Purchasing module). It occurs when a user attempts to perform a control action—such as cancelling, closing, or finally closing a document—that is restricted by the document's current state or underlying data issues. Core Causes

The primary reason for this error is a mismatch between the requested action and the document status. Specific triggers include:

Status Conflicts: Attempting to cancel or close a document that is already in a terminal state (e.g., already cancelled or finally closed) or in a transitional state (e.g., Pending Approval). Reference: Oracle Knowledge Document ID 438091

Internal Dependencies: Trying to cancel a Purchase Order (PO) derived from an internal requisition or one with linked sales order lines that are still open.

Fully Received Lines: The system prevents cancellation of lines that have been fully received or where the received quantity has already been consumed by the warehouse.

Account Issues: A disabled or inactive charge account on the PO distributions can block completion of document actions.

Software Bugs: Known bugs in specific Oracle versions (e.g., R12) often require patches like PSA RPC Patch 14563642 or referring to Oracle Support Note 1912083.1. Recommended Troubleshooting Steps APP-PO-14160: Document Action Not Completed Successfully

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].

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].

Scenario 1: Workflow Stuck If the document is stuck in the workflow:

Scenario 2: Data Corruption (Missing/Invalid Data)

Scenario 3: Custom Code Conflict If recent customizations were deployed to the PO forms: