The truck left, but the status didn't. The pick released, but nothing's in Pick Confirm. The hold won't even apply. Pick your symptom — a flashcard tells you what's actually going on in plain words, the fix step by step, exactly where to click in Fusion, and the SQL when you need to look under the floor. The answers Google keeps behind Oracle's support login, served free and readable.
Community-written quick reference for widely-known Oracle Fusion fulfillment troubleshooting practice; statuses and behavior vary by release and configuration — verify in your instance. Costing side of transfers and shipments: the Costing triage room. The full journey these documents live in: P2P Live.
Orchestration has handed the line to the warehouse and is waiting for ship confirm to interface back. If it lingers: the shipment is either physically unfinished (not picked/confirmed) or confirmed-but-stuck in the shipping/inventory interfaces — run Manage Shipping Interfaces and check Manage Pending Transactions.
The ship confirm happened, but the interface run that reports it back never completed. Run Manage Shipping Interfaces for the source org, then check the shipment line's OM/INV interfaced flags — both should flip to Y. If a flag stays N without a visible error, the interface run's own log in Scheduled Processes usually names the cause.
Because the pick never actually materialized — release sent the request, but allocation failed silently: no onhand in a pickable subinventory, a reservation pointing at different stock, or a zero-allocated pick wave. Fix the supply, then re-release the line for a fresh pick.
Two gates: the line must be in a wait state (holds can't land on a task mid-flight), and the line must not be in error recovery — Fusion refuses hold requests on lines in error recovery. Recover the error first, then apply the hold.