App-po-14160 Document Action Not Completed Successfully May 2026

Corrupt or inconsistent data in the background tables can trigger the error. This includes:

The pop-up message is often truncated. To see the real cause:

Once you have diagnosed the cause, apply the corresponding fix below. app-po-14160 document action not completed successfully

Based on extensive analysis of Oracle Support and field experience, this error usually stems from one of the following:

| Category | Typical Root Cause | | :--- | :--- | | Workflow Issues | The Purchasing Document Approval Workflow (POAPPRV) is stuck, corrupted, or missing an approver. | | Security & Access | The user lacks APPROVE or MODIFY privileges on the Operating Unit or Document Type. | | Data Corruption | Missing or invalid data in PO_HEADERS_ALL (e.g., blanket_total_amount = 0 when required). | | Hold or Control | A financial hold (e.g., encumbrance, budget) or a document control status (e.g., "Incomplete") blocks the action. | | Integration Conflict | Another process (e.g., AME, Cloning) has locked the document row. | Corrupt or inconsistent data in the background tables

Use backend queries to validate the PO’s integrity. Example SQL check for inconsistent approval status:

SELECT po_header_id, approval_status, wf_item_key
FROM po_headers_all
WHERE segment1 = 'YOUR_PO_NUMBER';

Compare the approval_status against the workflow state. Once you have diagnosed the cause, apply the

If the workflow is out of sync, use:

Work with your system admin to ensure your role has the correct privileges. For app-po-14160, focus on these action rights:

After updating permissions, log out completely and restart your client to refresh your security token.