Once you’ve resolved the immediate error, take proactive measures to prevent recurrence.
Furthermore, can trigger this error. Organizations frequently customize the standard PO Approval Workflow (POWFRQAG or POAPPRV workflow) to accommodate specific business rules. Errors in the PL/SQL code within these custom wrappers, or invalid data in the PO_HEADERS_ALL or PO_LINES_ALL tables (such as a missing distribution set or invalid charge account), can cause the workflow engine to crash ungracefully, resulting in the generic 14160 message.
Before attempting to cancel or close, verify the current status of the header, lines, and shipments. app-po-14160 document action not completed successfully
: Known bugs in specific Oracle versions (e.g., R12) often require patches like PSA RPC Patch 14563642 or referring to Oracle Support Note 1912083.1 . Recommended Troubleshooting Steps APP-PO-14160: Document Action Not Completed Successfully
According to Oracle Support documentation 1.2.1 , the error APP-PO-14160: Document action did not complete successfully occurs when you attempt to perform a document action (such as Cancel, Finally Close, or Freeze) that is . Once you’ve resolved the immediate error, take proactive
Select your Operating Unit and choose the document type causing the issue (e.g., Standard Purchase Order ).
: Pending transactions in the "Transaction Status Summary" form can prevent document actions from completing. Known Bugs Errors in the PL/SQL code within these custom
If the check fails, navigate to to see the specific budget line causing the issue.
: You are attempting an action (e.g., "Finally Close") on a document that is in a state (e.g., "Closed" or "In Process") that does not allow it. Disabled Charge Accounts