App-po-14160 Document Action Not Completed Successfully [verified] May 2026

The error APP-PO-14160: Document action not completed successfully 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

Understanding the specific "why" behind this error is the first step toward a resolution. The system usually blocks the action for one of the following reasons: APP-PO-14160: Document Action Not Completed Successfully

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

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

  1. 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.
  2. 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.
  3. 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.
  4. 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. 000 and that field is empty

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

For System Administrators:

Step 1: Check the Full Error Context

Do not rely solely on the pop-up message. In most systems, you can:

5. Database Constraint Violation

A backend rule (like a required custom field or a unique index) is failing silently. For example, if a custom validation requires a "Justification" text field for any PO over $10,000 and that field is empty, the app-po-14160 code may fire instead of a user-friendly validation message.