App-po-14160 Document Action Not Completed Successfully ((link)) -

The Oracle E-Business Suite error "APP-PO-14160: Document action not completed successfully" occurs when attempting to control a document (e.g., cancel, close) that is in an incompatible status, such as "In Process," "Frozen," or "Incomplete". Solutions include clearing stuck receiving transactions, updating the charge account, or utilizing SQL scripts to reset the document status. For more details, visit Oracle Community .

If this is a known bug in the Oracle database version, include the patch details here: app-po-14160 document action not completed successfully

• Data Integrity Issue: The document header or line data is corrupted. For example, a line amount may not match the distribution total, or a mandatory segment of the Accounting Flexfield is missing.
• Workflow Notification Stuck: The document is stuck in the approval workflow. If the workflow engine fails to process a previous notification (e.g., due to a system timeout), subsequent actions may trigger this error.
• Custom Validation Triggers: Custom database triggers or client-side extensions (OAF/JavaScript) preventing the update without returning a specific error message.
• Concurrent Manager Locks: The record is currently being locked by a running concurrent request (e.g., Purge/Summarize PO or Workflow Background Process).

• Application namespace style ("app-po-14160") suggests:

  Disclaimer:

  Error codes and module names vary across software platforms. While "app-po-14160" strongly correlates with purchase order modules in several ERPs (including Oracle EBS, JD Edwards, and some custom .NET applications), your specific system may use a different mapping. Always consult your internal IT team or software vendor before making administrative changes. Data Integrity Issue: The document header or line

  Step 3: Examine Approval Workflow