Order cannot be Shipped due to inv_lot_loc_id data not found

Shipment orders that are impacted are consolidated in pick & sort waves. 

If user is using pick & sort function in the RF, user does not need to scan pickToTraceId. But in the above orders pickToTraceId was scanned to the wrong id.

which is the cause of the inventory not tally. The picktoTraceId is the suspected field that’s causing the issue. Therefore it is assume that user is using other RF function for this pick.

ShipperB2C confirmed their operational behaviour as below:

Cases that happened: 

1. This issue happens due to our Operation team creating the Pick and Sort wave but processing the Picking using RF Wave Picking so they only use 1 picking Box for all 6 orders.

2. This issue happens due to our Operation team creating the Single Line and processing the Picking using RF Wave Picking

To prevent these cases from happening again, now we're turning off the access for all ops team for RF Wave Picking & RF Picking and Allocation until we can replicate the cases in the staging or production for a dummy BOOYAH client.

Second step - Backend update to inventory table (Inv_Lot_Loc_id)

This is not recommended solution for user. DB admin or consultant needs to perform this step.

See the attachment for more information.