Lot Direct Picking in Oracle Cloud Apps 25D SupplyChain/Inventory avoidable?
Dear community,
We've just implemented Oracle Fusion Cloud Inventory and Warehouse execution processes, and we are looking for advice from other customers who moved from legacy WMS or ERP solutions where picking did not enforce lot level allocation during pick release or execution.
In our legacy process, pickers could pick “any valid lot” based on basic rules (FEFO, expiry, etc.), and the lot could be determined at a later point in the process (or at packing/shipping), what's also known as non-lot direct picking, basically, pickslips were not suggesting or reserving/allocating any lot in particular, if there was enough available stock in the system, operator could pick any lot. In Fusion, for lot controlled items, the standard behavior drives lot level picking and reservation, which is a significant change for our warehouse operations.