If a user creates a purchase order revision by modifying lines or quantities, the status changes. Trying to execute a action on a modified document before the new revision is fully approved will trigger the error. 2. Disabled or Inactive Accounting Elements
The Oracle E-Business Suite (EBS) is a powerful, yet complex, enterprise resource planning system. For professionals in purchasing and procurement, encountering a sudden error can bring workflows to a halt. One of the more common yet potentially confusing errors is , accompanied by the message "Document action not completed successfully." While this specific error is well-documented in Oracle's records, it's also an issue that can frustrate users at any level of experience.
Click on the icon (usually a red circle with an X). Look for the "Nested Exception" or "Detailed Message" . This is your gold mine. app-po-14160 document action not completed successfully
Keep your Oracle Procurement modules up to date with the latest Recommended Patch Collections (RPCs) to eliminate known bugs associated with document action packages.
: The document requires an approver who lacks the necessary signing limits, or the routing position path is broken or inactive. If a user creates a purchase order revision
Based on extensive analysis of Oracle Support and field experience, this error usually stems from one of the following:
This error typically surfaces when attempting to perform a critical document action—such as approving a purchase order (PO), releasing a hold, changing a line item, or confirming a receipt. The "app-po-14160" code points to an application-level permission or state conflict (with "PO" strongly suggesting module), while "document action not completed successfully" indicates the system’s backend validation failed. Click on the icon (usually a red circle with an X)
: If mandatory fields are missing on a requisition or purchase order, the document remains "Incomplete." The approval action is not available until all required information is provided.
The error 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