App-po-14160 Document Action Not Completed Successfully May 2026

Objective
Ensure that when document action app-po-14160 fails, the system provides clear diagnostics, automatic retry where appropriate, and a user-friendly recovery path.

Detailed Requirements

If you share more details about your environment and the exact failure symptoms, I can tailor this specifically to your case.

The error APP-PO-14160: Document action not completed successfully is a common issue in Oracle E-Business Suite (EBS), specifically within the Oracle Purchasing module. It typically appears when a user tries to perform a control action—like canceling, closing, or approving—on a Purchase Order (PO) or Blanket Release. Core Causes of APP-PO-14160

This error is essentially a "catch-all" notification indicating that the system cannot process your request due to an underlying data inconsistency or status mismatch.

Incompatible Document Status: The most frequent cause. You may be trying to cancel a document that is in a status (like 'In Process' or 'Pre-Approved') where that action is not permitted.

Disabled Charge Accounts: If the charge account associated with the PO distribution is disabled or end-dated in the General Ledger, the system will block any further actions on the document.

Stuck Receiving Transactions: Pending or "stuck" records in the RCV_TRANSACTIONS_INTERFACE or the Transaction Status Summary form can prevent a PO from being modified or canceled. app-po-14160 document action not completed successfully

Known Software Bugs: Certain versions of Oracle EBS have documented bugs related to this error, often requiring specific patches like the PSA RPC Patch. Troubleshooting & Solutions 1. Check Document and Account Status Before deep-diving into technical fixes, verify the basics:

Document Status: Ensure the PO is not currently "In Process." If it is, you may need to wait for the workflow to complete or abort it.

Account Validity: Navigate to the General Ledger and confirm that all accounts used in the PO Distributions are Active and have not passed their End Date. 2. Clear Stuck Transactions

If you are trying to cancel a PO and receiving this error, check for pending transactions: Navigation: Receiving > Transaction Status Summary.

Action: Query the specific PO. If records are stuck here, delete them and save your changes. This often "releases" the PO for further actions like cancellation. 3. Review Internal Requisitions

For POs created from Internal Requisitions, the error often occurs if there is a mismatch between the line_location_id on the PO and the corresponding request lines. Ensure that the link between the requisition and the PO remains intact and consistent. 4. Apply Oracle Patches

If the data appears clean but the error persists, you may be facing a system bug. Reference Oracle Support Note 1912083.1 on My Oracle Support. Common patches include:

PSA RPC Patch 14563642 (or the latest cumulative equivalent). Technical Diagnostics for Admins

If you have backend access, running these checks can pinpoint the root cause:

Check Workflow: Verify if the POAPPRV workflow is stuck or has errored out.

Table Check: Query PO_HEADERS_ALL and PO_LINES_ALL to ensure the AUTHORIZATION_STATUS and CLOSED_CODE are consistent with what you see in the frontend. If you'd like to troubleshoot further, let me know: What action were you taking (Canceling, Approving, etc.)? What is the current status of the document? Does this happen for all documents or just one specific PO? APP-PO-14160: Document Action Not Completed Successfully

APP-PO-14160: Document action not completed successfully typically occurs in Oracle E-Business Suite (EBS) when a user attempts a "Control" action (such as Cancel, Finally Close, or Close) on a document that is in a status incompatible with that action. Common Root Causes Status Conflict User Notification

: The most frequent cause is attempting to perform an action on a document that is already in a status like In Process Pre-Approved Fully Received Lines

: You cannot cancel a Purchase Order (PO) line that has already been fully received. Stuck Transactions

: Unprocessed receiving transactions in the "Transaction Status Summary" form can block control actions. Disabled Charge Accounts

: If the charge account associated with the PO line has been disabled in the General Ledger (GL), the system may fail to process the cancellation or update. Software Bug

: In specific versions (like R12), this error can be a known bug (e.g., related to PSA RPC Patch 14563642). Recommended Troubleshooting Steps Check Document Status

: Verify the header and shipment statuses. If the PO is "In Process," it must be reset to "Incomplete" using scripts like poxrespo.sql before further actions can be taken. Clear Stuck Transactions Navigate to Receiving > Transaction Status Summary Query the PO number to find any stuck records.

Delete these stuck records and save before retrying the action. Verify Account Validity : Ensure all segments of the Charge Account are active and allow posting for the current date. Undo Recent Changes

: If the document was modified but not archived, you may need to undo those changes before the system allows a "Cancel" action. Review My Oracle Support (MOS) Notes Note 1912083.1 if the error occurs during Blanket Release. Note 390023.1

for instructions on resetting PO status using the standard Oracle script. Proactive Follow-up: to check for stuck transactions or the parameters required to run the poxrespo.sql reset script? APP-PO-14160: Document Action Not Completed Successfully

APP-PO-14160: Document action not completed successfully typically occurs in Oracle E-Business Suite (EBS)

when you attempt an action (like canceling, finally closing, or approving) that is incompatible with the current status of the document Oracle Communities Common Root Causes Incompatible Document Status

: The most frequent cause is trying to perform an action on a document that is in a state where that action is disallowed (e.g., trying to cancel a purchase order that is already fully received). Stuck Receiving Transactions : Unprocessed or stuck records in the Transaction Status Summary form can prevent closing or canceling actions. Disabled Charge Accounts Automatic Retry Mechanism

: If the charge account associated with the PO line is inactive or disabled, the system may block document actions. Known Bugs/Patches

: 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

Search for the specific PO. If there are stuck records, delete them to clear the "Quantity Due" mismatch. Verify Account Validity Ensure all Charge Accounts Budget Accounts

associated with the PO lines are active and currently enabled. Review Document Status

Confirm the PO is not "Fully Received" if you are trying to cancel it. A PO cannot be canceled if the ordered quantity matches the received quantity.

For "Finally Close" actions, ensure no open shipments or unprocessed receiving transactions exist. Try the "Hold and Release" Workaround Open the Purchase Order and navigate to Tools > Controls and save the document. Tools > Controls Release Hold , and save again.

Attempt your original action (e.g., Update or Cancel) to see if the status resets. Consult My Oracle Support (MOS) Search for Note: 1309940.1 Note: 1912083.1 My Oracle Support portal

for scripts to identify specific data corruption or required patches. Oracle Communities APP-PO-14160: Document Action Not Completed Successfully

A: Usually not. It is session-specific. However, if the underlying cause is a corrupt workflow definition, all users may experience it on the same document.

A: Unlikely, unless the issue was a stuck local lock or memory corruption. Restarting might clear your cache, which helps in some web-based ERPs.

Based on real-world incident analysis, the following are the most frequent triggers:

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: