App-po-14160 Document Action Not Completed Successfully [portable] File

Make a minor cosmetic modification that triggers a revision increment (e.g., update the field or change the header descriptive flexfield).

: 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

While not every occurrence can be prevented, a disciplined approach to data entry and system management can significantly reduce the frequency of this error.

Source: Oracle Applications Error Messages Guide app-po-14160 document action not completed successfully

If the document is stuck in a state that prevents further action: Use the Oracle-provided reset script, often called poxrespo.sql for POs or porreset.sql for requisitions. This script reverts the document status to Incomplete , allowing you to fix errors or resubmit for approval.

If the error occurs during "Final Close," check the accounting setup.

The GL (General Ledger) or PO period for the document date is closed, preventing the system from creating necessary accounting entries. Make a minor cosmetic modification that triggers a

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

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

Note: Only perform this if you have confirmed the source system can resend the data, as you are deleting the document permanently. What is the current status of the document

: If an invoice has already been matched to a PO shipment, the shipment is considered "Matched" or "Billed." The system will block the cancellation action to preserve financial integrity.

This article provides a comprehensive overview of why this error occurs, common scenarios, and actionable troubleshooting steps to resolve it. What is APP-PO-14160?

When the error occurs consistently despite following correct procedures, it may indicate an underlying bug in the Oracle application. One of the most frequently cited references for this error in the Oracle community is on the Oracle Support (MOS) portal. According to community reports, this note identifies the issue as a known bug for which Oracle recommends applying specific patches. The suggested patches mentioned include PSA RPC Patch 14563642 to resolve the issue. This indicates that in certain versions of Oracle EBS, the error can be triggered by a flaw in the program code rather than user error.

The requisition is in a state where it cannot be re-opened, blocking the cancellation of the related purchase order.