Log into using the Purchasing Responsibility .
-- Example for a foreign key violation SELECT * FROM po_headers_all WHERE vendor_id NOT IN (SELECT vendor_id FROM vendors);
Sometimes the UI misleads users. For example:
The person who originally created the document or the next approver in the chain has been deactivated in the system. 2. How to "Unstick" It app-po-14160 document action not completed successfully
Click and look for workflows with a status of Error or Active (stuck).
Missing data in the interface tables, mismatched sequence numbers, or invalid combination IDs (such as Code Combination IDs for accounts) block the database from updating the document status.
Verify that the supplier is still active and has a valid site. Log into using the Purchasing Responsibility
The APP-PO-14160 error is essentially a wrapper message. It indicates that the Oracle Purchasing form or concurrent program attempted to execute an action (like APPROVE ), but the database or workflow engine failed to complete it. The most frequent underlying causes include:
Apply changes and test.
Ensure that the period corresponding to the PO’s target date is set to . Do the same for the General Ledger (GL) periods. 4. Inspect the Document Manager Status Verify that the supplier is still active and
Go to the Workflow Status Monitor, click on the errored activity, and view the error details. If it points to an approver issue, correct the supervisor assignment in the People form ( PER_ALL_PEOPLE_F ), then use the Workflow Monitor to Retry the activity. Scenario B: Concurrent Request Log Shows Database Errors
Unlikely, unless the issue was a stuck local lock or memory corruption. Restarting might clear your cache, which helps in some web-based ERPs.