If you are creating a Purchase Order for inventory items, the system must generate distribution accounts. If the "Account Generator" workflow fails to build a valid GL code combination (perhaps due to a new cost center or invalid segment values), the document cannot be saved or approved. While this often triggers an "Invalid Account" error, it can sometimes roll up into the generic 14160 error if the failure happens during the final submission validation.
Understanding the "why" is the first step toward a fix. The system triggers this message when internal validations fail for one of the following reasons: app-po-14160 document action not completed successfully
Unprocessed receiving transactions or "stuck" records in the Transaction Status Summary form can prevent document actions from completing. If you are creating a Purchase Order for
-- Check for orphaned foreign keys SELECT * FROM po_headers ph LEFT JOIN vendor_master vm ON ph.vendor_id = vm.vendor_id WHERE vm.vendor_id IS NULL; Understanding the "why" is the first step toward a fix
The error is a frequent technical hurdle in Oracle Purchasing (E-Business Suite) . It typically occurs when a user attempts to perform a control action—such as cancelling , finally closing , or approving —that the system deems incompatible with the document's current state . Core Causes of APP-PO-14160