App-po-14160 Document Action Not Completed Successfully top | 2026 Release |

Deep analysis: "app-po-14160 document action not completed successfully"

1. Symptom

When attempting to perform a document action (such as Approve, Reject, Submit for Approval, or Update) on a Purchase Order or Requisition, the system displays a generic error message:

"Error: APP-PO-14160: Document action not completed successfully."

In some instances, the error may be accompanied by a Java stack trace or a database constraint error in the backend logs. The user is forced to navigate away from the page, and the transaction is rolled back.

6. User Action Plan

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

: 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 app-po-14160 document action not completed successfully

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

Step 5: Run Data Fix Scripts (SQL)

Caution: Run these only with DBA approval.

Query PO_HEADERS_ALL for the document ID:

SELECT wf_item_type, wf_item_key, approval_status
FROM po_headers_all
WHERE po_header_id = <your_id>;

If approval_status = INCOMPLETE but workflow status is PROCESS, update manually (or use the Workflow Administrator to retry).

4. Reproduction steps (general template)

Use a test account with same role/permissions.
Prepare a document payload that matches the one causing failure (same size, metadata, fields).
Execute the same action (create/save/submit/approve) via the same channel (UI/API/batch).
Observe response codes and logs; if no failure, incrementally:
- Increase payload size to test file-size/disk limits.
- Introduce concurrent updates to test optimistic locking.
- Disable retries to see raw failure.
- Simulate downstream failures (DB connection drop, DMS unavailable).
If asynchronous: send message and watch worker process; inject faults in message consumer.

6. When to Contact Oracle Support

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

Full screenshot of the error window.
Application log file snippet (ICX_PO.log or FND_LOG).
Output of SQL query showing the document's approval_status and workflow_item_key.
Steps to reproduce the issue in a test instance.

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

Title: Troubleshooting the "APP-PO-14160: Document Action Not Completed Successfully" Error in Oracle Purchasing

Introduction

In the landscape of enterprise resource planning (ERP) systems, Oracle E-Business Suite (EBS) stands as a colossal framework for managing organizational procurement. However, its complexity often gives rise to cryptic error messages that can halt critical business processes. One such prevalent and often frustrating error is "APP-PO-14160: Document Action Not Completed Successfully." This error typically surfaces during the approval workflow of Purchase Orders (PO) or Requisitions, acting as a bottleneck that prevents the procurement cycle from moving forward. Understanding the root causes of this error—ranging from workflow notification issues to setup inconsistencies—is essential for database administrators and functional users to maintain operational efficiency.

Understanding the Context

The error code APP-PO-14160 is a generic catch-all message signaling that the workflow engine failed to execute a specific action on the document. In Oracle Purchasing, the workflow engine acts as the traffic controller, moving documents through various states (e.g., Draft, Incomplete, Requires Approval, Approved). When a user attempts to approve, reject, or forward a document, the system initiates a background workflow process. When this process encounters an exception—be it a data integrity issue, a missing approval hierarchy, or a system configuration error—it terminates and throws the 14160 error. Because the message itself offers little detail, it necessitates a deeper diagnostic approach.

Primary Causes and Technical Mechanisms

The etiology of the APP-PO-14160 error is multifaceted. One of the most common causes lies within the Position Hierarchy and Approval Group setups. Oracle Purchasing relies heavily on the position hierarchy to determine the chain of authority. If a user's position is not correctly assigned to a job that falls within the approval limits required for the transaction, the workflow cannot determine the next approver. Consequently, the workflow state becomes "No Approver Found," leading to the failure of the document action.

A second major cause is Workflow Notification System (WFS) congestion or corruption. Often, the workflow background engine encounters a "hanging" process. If a previous workflow activity did not complete cleanly—perhaps due to a database timeout or a locking issue—the document enters a state of limbo. Subsequent attempts to act on the document fail because the system perceives the document as currently being processed or locked by another session.

Furthermore, customizations and data corruption can trigger this error. Organizations frequently customize the standard PO Approval Workflow (POWFRQAG or POAPPRV workflow) to accommodate specific business rules. Errors in the PL/SQL code within these custom wrappers, or invalid data in the PO_HEADERS_ALL or PO_LINES_ALL tables (such as a missing distribution set or invalid charge account), can cause the workflow engine to crash ungracefully, resulting in the generic 14160 message.

Diagnostic and Resolution Strategies

Resolving the APP-PO-14160 error requires a systematic approach, moving from the application layer to the database layer.

Workflow Status Checks: The first step is to utilize the "Status Monitor" in Oracle Workflow. By searching for the item key associated with the Purchase Order, administrators can view the workflow diagram to identify exactly which node failed. This helps pinpoint whether the error occurred during the "Notify Approver" phase or the "Approval" phase.
The wfstat.sql and POXWDDB.sql Scripts: Oracle Support provides diagnostic scripts such as wfstat.sql to check the status of workflow items and POXWDDB.sql to debug PO workflows. These scripts reveal if the document is stuck in a specific activity and can identify "Blocked" or "Errored" activities.
Position Hierarchy Validation: Functional consultants must verify the Approval Group and Position Hierarchy setups. Ensuring that the user attempting to approve the document has a valid position defined in the hierarchy and that the "Document Total" falls within their approval limits is a crucial validation step.
Database Intervention: If the document is physically locked or the workflow activity is stuck, intervention via the backend may be required. Administrators may need to use the Workflow Administration console to "Retry" or "Skip" a stuck activity. In more severe cases, verifying the PO_ACTION_HISTORY table to see if there is a mismatch between the application status and the database record is necessary. If the document is in a "Locked" state, identifying and killing the blocking session or resetting the workflow status may be the only recourse.

Conclusion

While the "APP-PO-14160: Document Action Not Completed Successfully" error is a daunting obstacle in Oracle Purchasing, it is a solvable one. It serves as a reminder of the intricate dependencies between organizational hierarchy setups, workflow engine logic, and underlying database integrity. By systematically analyzing workflow logs, validating hierarchy setups, and employing Oracle diagnostic scripts, technical teams can resolve these blockages. Ultimately, a proactive approach—ensuring clean setups and monitoring workflow performance—is the best defense against such disruptions, ensuring that the procurement lifecycle remains fluid and uninterrupted.

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. In some instances, the error may be accompanied

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 code APP-PO-14160: Document action not completed successfully is a common hurdle found in Oracle E-Business Suite (EBS), specifically within the Purchasing module. It typically pops up when a user tries to approve, reserve, or forward a document (like a Purchase Order or Requisition) and the system hits a logical "dead end." 1. The "Why" Behind the Error

This isn't usually a bug in the code, but rather a data integrity check failing. The system is essentially saying, "I tried to process this, but something about the document's current state or the setup doesn't add up." Common culprits include:

The Approval Loop: The document is stuck in a "Pre-Approved" or "In Process" status because the next person in the hierarchy doesn't have enough signing authority or isn't assigned a proper position.

Budgetary Control: If your organization uses Encumbrance Accounting, the error often triggers because there are insufficient funds in the specific GL account, or the budget period is closed.

Inactive Users: The person who originally created the document or the next approver in the chain has been deactivated in the system. 2. How to "Unstick" It

If you are troubleshooting this, the "interesting" part is that the fix is almost never on the document itself, but in the Workflow:

Check the Workflow Monitor: This is the "X-ray" for Oracle EBS. It will show exactly which activity failed (e.g., Is_Forward_To_Valid or Reserve_Action).

The "Reset" Script: Oracle provides a specific script (porvdoc.sql) that DBAs use to "force-reset" a document's status back to 'Incomplete' so it can be re-submitted correctly.

Verify the Employee-Supervisor Hierarchy: Ensure there isn't a "broken link" in the chain. If a manager left the company and their supervisor link wasn't updated, the document has nowhere to go. 3. A Pro-Tip for Techies workflow engine logic

The error is often a "wrapper." If you look at the underlying PO_ACTION_HISTORY, you might find a more descriptive sub-error. Usually, if APP-PO-14160 appears alongside a message about "Tax Calculation," the issue is actually in the E-Business Tax (eBTax) module failing to calculate a rate, which then halts the entire PO approval. Are you seeing this error on a specific document type, or AI responses may include mistakes. Learn more

Q5: Does this error affect other users?

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.

App-po-14160 Document Action Not Completed Successfully __top__ | 2026 Release |