If the issue persists, it may be a known Oracle bug, particularly in version 12.2.5.
Select your Operating Unit and choose the document type causing the issue (e.g., Standard Purchase Order ).
Last Updated: October 2025
When you first see the error, follow these steps. Most can be performed by an end user without admin rights.
That strongly suggests an approval workflow limit. The system is trying to route the PO to a higher‑level approver, but that approver’s user account may be missing or inactive. Check your approval rules. app-po-14160 document action not completed successfully
For certain Oracle errors, running specific concurrent requests can resolve underlying data inconsistencies. One documented approach for related error scenarios is to execute the request from the System Administrator responsibility. This process rebuilds certain critical data structures and has been known to resolve specific Oracle Purchasing errors.
Set the parameters as required (usually left blank to refresh the entire hierarchy). If the issue persists, it may be a
Most APP-PO-14160 errors are tied to a failed workflow background process. Log in with the responsibility.
This is the "X-ray" for Oracle EBS. It will show exactly which activity failed (e.g., Is_Forward_To_Valid or Reserve_Action ). Most can be performed by an end user without admin rights
The error is undoubtedly frustrating, but it is rarely a system-breaking catastrophe. In the vast majority of cases, the error is the application’s way of protecting data integrity—telling you that the requested action violates a rule, lock, or permission.
Unlikely, unless the issue was a stuck local lock or memory corruption. Restarting might clear your cache, which helps in some web-based ERPs.