App-po-14160 Document | Action Not Completed Successfully [best]

when you attempt an action (like canceling, finally closing, or approving) that is incompatible with the current status of the document Oracle Communities Common Root Causes Incompatible Document Status

SELECT item_key, activity_status, activity_result FROM wf_item_activity_statuses_v WHERE item_key = '<DOCUMENT_ID>' ORDER BY begin_date DESC;

: If you are trying to cancel a Purchase Order (PO) line that has already been fully received, the system will block the action. Disabled Accounts app-po-14160 document action not completed successfully

To minimize the recurrence of this error in your Oracle EBS environment, implement these proactive measures:

: Navigate to the General Ledger and confirm that all accounts used in the PO Distributions are Active and have not passed their End Date . 2. Clear Stuck Transactions when you attempt an action (like canceling, finally

: A disabled or inactive charge account on the PO distributions can block completion of document actions.

: Verify if the POAPPRV workflow is stuck or has errored out. Clear Stuck Transactions : A disabled or inactive

Never look at the red light; look at the log behind the red light. Is it a mapping? A connection? A missing receiver? Once you identify the specific action that failed (Map, Send, Write), the fix becomes linear.

The error typically occurs in Oracle E-Business Suite when a user attempts to perform a control action (like cancelling or closing) on a Purchase Order or Blanket Release that is in an incompatible status. Common Causes

Funds checking failed (no funds available, account closed, or GL date closed).