App-po-14160 Document Action Not Completed Successfully -

Some versions of procurement software have known bugs that trigger app-po-14160 under specific conditions (e.g., tax calculation failures). Check your vendor’s knowledge base for relevant patches.

Users typically encounter this error in one of the following five scenarios:


For web-based ERPs:

For thick clients (Java, .NET):

Do not rely solely on the pop-up message. In most systems, you can: app-po-14160 document action not completed successfully

To fix the problem, you must first understand the error syntax.

In plain English: You tried to do something to a purchase order (like approve, edit, or delete), but the system refused because the document is in a state that does not allow that action—or because your security profile lacks the necessary permission. Some versions of procurement software have known bugs


  • If asynchronous: send message and watch worker process; inject faults in message consumer.

  • To avoid encountering APP-PO-14160 in the future:

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

    "Error 14160: User [ID] attempted to set status='APPROVED' on PO_ID=5678 but workflow rule WF-210 requires vendor approval flag=True."