If the manager is running, the issue is likely data-specific. Check if the person is active in the system.
: Periodically audit "Buyer" records to ensure they are active and not end-dated in the HR system. SQL queries to check for mismatched line IDs or to verify the workflow status of a stuck PO? APP-PO-14160: Document Action Not Completed Successfully 18 Jun 2020 —
If the error occurs during standard operations on Blanket Releases or during a "Finally Close" action, you are likely hitting an identified product bug. apppo14160 document action not completed successfully hot
If the General Ledger (GL) accounts attached to the PO lines, shipments, or distributions have been disabled or frozen, Oracle prevents any further document action. Even a cancellation action requires account validation to reverse funds or update encumbrances. 2. Internal Requisition Mismatches
To clear the error and process your procurement documents, follow this logical technical troubleshooting path: If the manager is running, the issue is likely data-specific
Run the System File Checker (SFC) tool to scan and repair corrupted system files:
Confirm if the line status, shipment status, and distribution status match. If a single shipment is closed or fully billed, a global "Cancel" action will fail. 3. Run Oracle Procurement Analyzers SQL queries to check for mismatched line IDs
The specific charge account, accrual account, or variance account associated with the PO lines has been disabled or expired in the General Ledger.
: Known bugs in specific Oracle EBS versions (like R12) can trigger this error during standard document management tasks. Troubleshooting Steps