Note: Always run these scripts in a test environment first and review Oracle Support guidelines (Doc ID 454374.1 or similar) before applying fixes to production. Prevention Best Practices
If a difference exists between the approved version of the PO stored in the archive tables ( PO_REVISIONS_ALL ) and the active transaction document in the base operational tables ( PO_HEADERS_ALL ), Oracle rejects control actions. This structural mismatch happens when a change order is improperly saved or interrupted mid-cycle. 3. Linked Requisition and Open Supply Interlocks app-po-14160 document action not completed successfully
Search for the specific PO. If there are stuck records, delete them to clear the "Quantity Due" mismatch. Verify Account Validity Ensure all Charge Accounts Budget Accounts Note: Always run these scripts in a test
: Navigate to the General Ledger and confirm that all accounts used in the PO Distributions are Active and have not passed their End Date . 2. Clear Stuck Transactions Verify Account Validity Ensure all Charge Accounts Budget
The document amount exceeds the approval limit of the person attempting the action, and the system cannot find a valid next approver with a higher limit.
Look for the exact exception class (e.g., oracle.apps.fnd.framework.OAException or PoException ).
"Error: APP-PO-14160: Document action not completed successfully."