App-po-14160 Document Action Not Completed Successfully -

  • "document action not completed successfully" means a workflow step that alters, saves, routes, or finalizes a document returned failure or timed out.
  • Typical scenarios:
  • If asynchronous: send message and watch worker process; inject faults in message consumer.

    • Locate the error logs. In Oracle EBS, check:

    Look for the exact exception class (e.g., oracle.apps.fnd.framework.OAException or PoException).

    Use backend queries to validate the PO’s integrity. Example SQL check for inconsistent approval status: app-po-14160 document action not completed successfully

    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.

    If another user or background process is modifying the same document simultaneously, the system may lock the record. The app-po-14160 error can appear when a process tries to update a PO that is currently locked. If asynchronous: send message and watch worker process;

    The APP-PO-14160 error is a generic, yet common, roadblock encountered by buyers and procurement agents in Oracle E-Business Suite. The message simply states:

    "Document action not completed successfully" Locate the error logs

    While the text is vague, it typically signals a failure during a workflow process, a data integrity issue, or a missing security setup within the Purchasing module. The error prevents the user from approving, forwarding, or modifying the document (PO, Release, or Blanket Agreement).

    Attempting to perform an action that is invalid for the PO’s current state. For example: