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

Transfer order lifecycle, where is mine, actually?

A transfer order lives a double life: an ORDER (requested → awaiting fulfillment → closed) and its EXECUTION (pick → ship → in-transit → receive → putaway at destination). The order status only moves when execution events interface back, so 'stuck' almost always means an execution event didn't report home.

Root cause

TO status lags execution because interfaces carry the news.

How to fix it
  1. Find the TO and read line status + fulfillment details
  2. Map which execution step last completed (picked? shipped? received?)
  3. The gap between 'what physically happened' and 'what the status says' names your stuck interface: shipping interfaces (outbound) or receiving/putaway processing (inbound)
  4. Costing note: the ISSUE leg must fully cost before the destination receipt can, our Costing room's transfer card covers that half
Where to go in Fusion
Diagnostic SQL

TO lines and statuses

select header_id, status_code, fulfillment_status from inv_transfer_order_lines where header_id in (select header_id from inv_transfer_order_headers where header_number = '&to_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