Backorder/Partial Ship

When Inventory Management Cloud (WSH) performs a partial ship and there is no backordered event coming into Oracle Transportation and Global Trade Management Cloud (OTM) from Order Management Cloud (OM), a transportation planner could manually enter partial ship info in OTM by creating a new Order Movement for the remaining quantity and either plan a new shipment from the newly created Order Movement or add the new Order Movement to an existing shipment and send that Planned Shipment details to WSH. Below is an example detailing this use case.

1. OM sends an order (e.g. FA.ORDER1) with a quantity of 10 to OTM.
2. OTM plans a shipment from that order and sends the planned shipment (Eg: FA.SHIPMENT1) to WSH with quantity of 10 for execution. An order movement (e.g. FA.OM1) with quantity of 10 will also be automatically created.
3. WSH does a partial ship (e.g. quantity of 6) of the shipment and sends shipment actuals to OTM with a shipped quantity of 6. This will update the existing shipment with quantity of 6.
4. WSH communicates to OTM manually that the remaining quantity of 4 needs to be addressed as in this specific case there won’t be a backordered line request coming from OM.
5. OTM planner in this case could create a new order movement (Eg: FA.OM2) for the remaining quantity of 4. Create a new shipment (Eg: FA.SHIPMENT2) from the new order movement with quantity of 4. As a note, the new order movement (FA.OM2) can also be added an existing shipment instead of creating a new shipment if intended.
6. Send the new planned shipment (FA.SHIPMENT2) to WSH for execution.

Alternatively, Inventory Management Cloud publishes a backordered event that can be consumed by OTM and setup a replan workflow.