App-po-14160 Document Action Not Completed Successfully [work] Access
The error APP-PO-14160: Document action not completed successfully 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
Inactive Accounts: The charge account associated with the PO may no longer be enabled. app-po-14160 document action not completed successfully
- Fix: Ensure token scopes/roles include document action; add clear 403 with guidance; audit RBAC config.
Check the Status: Ensure the PO is not "In Process." If it is, use the Workflow Monitor to see if it’s stuck and needs to be reset. Clear Stuck Interface Records: Fix: Ensure token scopes/roles include document action; add
2. Workflow State Violation
Each PO follows a lifecycle: Draft → Pending Approval → Approved → In Receiving → Closed. The error appears when you try to perform an action reserved for a different state. Example: Trying to "Approve" a PO that is already "Invoiced." Check the Status : Ensure the PO is not "In Process
Disabled Accounts: The Charge Account associated with the Purchase Order (PO) might be disabled in the Chart of Accounts.
to see where the document is currently sitting in the workflow. If it is stuck "In Process," it may need a reset. Oracle Communities 2. Clear Stuck Transactions If the issue occurs during cancellation or returns: Navigate to Receiving > Transaction Status Summary Query the problematic PO. Delete any stuck records and save. Try the document action again. 3. Reset the Document Status
