Apppo14160 Document Action Not Completed Success[patched] Fully Hot May 2026

: Verify that all segments of the charge accounts assigned to the PO lines are active and have not expired.

Are you seeing this error while a specific PO, or is it happening across all documents ? APP-PO-14160: Document Action Not Completed Successfully

: Issues often arise when the PO originated from an internal requisition, and there is a mismatch between the line_location_id and the request lines. apppo14160 document action not completed successfully hot

The error is often a symptom of underlying data inconsistencies or configuration issues. According to discussions on Oracle Communities and Spiceworks , the following are frequent triggers:

: Search for the error code along with your specific version of EBS. Many instances of this error are documented in MOS notes like Doc ID 1309940.1 , which provides specific data fix scripts for common causes. : Verify that all segments of the charge

To resolve the APP-PO-14160 error, follow these diagnostic steps:

: If the PO is tied to a requisition, check that the line_location_id correctly maps between the PO and the requisition lines. The error is often a symptom of underlying

When working with Oracle E-Business Suite (EBS) or related Oracle Applications, encountering the error can bring critical procurement workflows to a halt. This error typically surfaces when a user attempts to perform a control action—such as cancelling , closing , or approving —on a Purchase Order (PO) or a Blanket Release.

: If the issue persists, your system administrator may need to apply a patch or run a diagnostic script to identify and repair orphaned records in the database. Summary Table Error Code Primary Action Involved Likely Solution APP-PO-14160 Cancel, Close, Approve Check GL account status or apply Oracle patch. APP-14016 General Control Action Verify document status is compatible with action. APP-14230 GL Date Entry Ensure date falls within an open GL period.