App-po-14160 Document Action Not Completed Success|top| Fully

Use transaction SM12 to display and delete locks. Select the table containing your PO number and remove the lock entry.

Navigate to the workflow administration console. Verify that:

Records related to the Purchase Order (PO) are stuck in the "Transaction Status Summary" form. Known Bugs: app-po-14160 document action not completed successfully

⚠️ : You cannot perform any further actions (like receipts or invoices) once a PO is Finally Closed .

Review the output HTML report for any flagged errors regarding invalid accounts, missing encumbrance flags, or broken hierarchies. How to Resolve the Error Use transaction SM12 to display and delete locks

: Attempting to cancel or close a document that is already in a terminal state (e.g., already cancelled or finally closed) or in a transitional state (e.g., Pending Approval).

The error can be frustrating, especially when it halts important procurement or document workflows. However, in most cases, it is solvable by systematically checking required fields, refreshing sessions, or reviewing workflow rules. For persistent cases, backend logs and database checks will reveal the true culprit. Verify that: Records related to the Purchase Order

If you have administrator access, check the server logs or audit trails. Search for "14160". You may find a more detailed stack trace:

The document status (e.g., "In Process", "Pre-Approved") does not support the action you are trying to perform. Disabled Accounts:

If you are currently troubleshooting this issue, tell me (Requisition or PO) is throwing the error and if you have access to the Workflow Status Monitor . I can guide you through the exact steps to find the underlying error log. Share public link

: Another user or a hanging system process has locked the specific PO record in the database tables ( PO_HEADERS_ALL , PO_LINES_ALL ), preventing updates.