Action Not Completed Successfully __hot__ — App-po-14160 Document

: 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

: The charge account associated with the PO lines may have been disabled or is no longer active in the General Ledger. app-po-14160 document action not completed successfully

The error is often a "wrapper." If you look at the underlying , 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 : Query PO_HEADERS_ALL and PO_LINES_ALL to ensure the

The error is a message from Oracle E-Business Suite (EBS) , specifically within the Purchasing (PO) module. It typically triggers when you attempt a document action (like cancelling, approving, or modifying a Purchase Order) that is incompatible with the document's current status . Common Causes and Solutions Does this happen for all documents or just one specific PO

The error is deterministic. If it worked before, something changed—either the PO’s state, your permissions, or a related master data element (like a vendor or account code).

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