WMS DROP LPN Field In WMS Pick Drop Page is Populated Despite Parameter DROP_INTO_LPN is Set to No
(Doc ID 1368805.1)
Last updated on FEBRUARY 05, 2019
Applies to:Oracle Warehouse Management - Version 184.108.40.206 and later
Information in this document applies to any platform.
In the Mobile WMS Pick Drop page, the field 'Drop LPN' will be populated (if applicable) although parameter DROP_INTO_LPN has been set to 'NO' in the function definition of WMS_DROP_LOADED_LPNS_MOB
Expected that field "DROP LPN" will not be populated
Create a scenario where a delivery consists of at least two picking tasks. Perform pick and drop for task 1. Then perform pick for task 2 and try to drop the task. In this case, the previously dropped LPN of task 1 will be suggested in the field 'Drop LPN'.
When following this suggestion (leaving the field as it is), dropping the lpn of task 2 will lead to a nested lpn structure (LPN of task 2 will be nested into lpn of task 1).
However as we only pick and drop complete pallets, nesting lpns will physically never occur, so when a user does not explicitly empty the field 'Drop LPN',
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document