App-po-14160 Document Action Not — Completed Success[updated] Fully

Ensure that the parent position currently has an active employee assigned to it.

: This error is sometimes linked to specific Oracle bugs (e.g., Oracle Support Note 1912083.1), which may require applying a patch. Recommended Troubleshooting Steps Check Document Status

It is important to note that while online discussions and technical notes often refer to this error in as APP-PO-14160 , the exact formatting can vary depending on the system interface and logging configuration. The lowercase version, "app-po-14160," is essentially the same identifier and points to the same underlying issue. When searching for solutions in Oracle support portals, using the uppercase format generally yields the most accurate results.

A partially invoiced or matched PO might throw this error if the invoice status is pending. 3. How to Resolve APP-PO-14160 Follow these troubleshooting steps to resolve the error. Step A: Verify Document Status Navigate to the Purchase Order Summary screen. Query your document. app-po-14160 document action not completed successfully

The charge account associated with the PO distribution might be inactive, invalid, or closed, preventing the final closing process.

The Oracle E-Business Suite error "APP-PO-14160: Document action not completed successfully" occurs when attempting to control a document (e.g., cancel, close) that is in an incompatible status, such as "In Process," "Frozen," or "Incomplete". Solutions include clearing stuck receiving transactions, updating the charge account, or utilizing SQL scripts to reset the document status. For more details, visit Oracle Community .

⚠️ : You cannot perform any further actions (like receipts or invoices) once a PO is Finally Closed . Ensure that the parent position currently has an

By following the systematic troubleshooting approach outlined in this guide—first identifying the document status, then applying the appropriate corrective action, and finally escalating to patches or support if needed—you can resolve this error efficiently and get your procurement workflows back on track.

The error 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

Most enterprise applications write detailed errors to a log file or database table. Search for: then applying the appropriate corrective action

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

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.

If your organization uses Encumbrance Accounting, a failure to reserve funds will trigger this error. Open the stuck PO or requisition in the entry form. Go to > Check Funds .

Disclaimer: This article is provided for informational purposes. Error codes and application behaviors may vary between software versions and vendors. Always consult your official system documentation and follow your organization’s change management procedures before modifying backend data or configurations.

If you are trying to cancel a PO shipment, ensure no pending receipts exist in RCV_TRANSACTIONS_INTERFACE or MTL_TRANSACTION_INTERFACE . Go to . Ensure there are no pending transactions for this PO. Step C: Verify Accounting Date and Setup