S Shortlisted
Oracle Fusion Order Management · stuck order or shipment · cause and fix

Line shows Released to Warehouse, but it's not in Pick Confirm

“Released to Warehouse” means a pick request went out. If nothing shows in Pick Confirm, the pick never actually materialized, usually because allocation failed silently: no onhand in the pickable subinventory, a reservation pointing elsewhere, or the pick wave excluded it.

Root cause

Pick released but allocation/move order never created or was created empty.

How to fix it
  1. Check the pick wave result for that line, did it allocate? Zero-allocated lines look 'released' but produce nothing to confirm
  2. Check onhand in the PICKABLE (reservable) subinventories, org-level onhand isn't enough
  3. Check reservations: a reservation against a different subinventory/lot hijacks allocation
  4. Re-release the line after fixing supply; it creates a fresh pick
Where to go in Fusion
Diagnostic SQL

What did allocation actually create?

select delivery_detail_id, released_status, subinventory, lot_number from wsh_delivery_details where source_header_number = '&order_number'

Read-only diagnostic queries. Substitute the bind values for your instance; run in a test environment first.

Checked Order Management and Fulfillment troubleshooting for Oracle Fusion, rewritten in plain words from publicly known practice and reviewed by a working consultant. Checked against the current release, Jul 2026. Navigation and behavior vary by configuration; verify in your own instance and test before acting.

Solve it, then prevent it

This page covers one error. These help with the rest:

More Order Management and Fulfillment errors