LPNs With 2 Lock Codes When Combine/Split Screen Merges LPNs With Different Locks
(Doc ID 2563719.1)
Last updated on JULY 08, 2020
Applies to:Oracle Warehouse Management Enterprise Edition Cloud Service - Version 18 and later
Information in this document applies to any platform.
On : 18C version, Core Product Functionality
LPNs with 2 lock codes when Combine/Split screen merges LPNs with different locks
When inventory from an LPN with lock code A (e.g., "SHPHLD" allocation and loading not allowed) is merged with inventory with lock code B (e.g., "FG" allocation and loading is allowed) the inventory merges on the LPN so that all the inventory is said to have both locks. This makes little sense because the two locks have contradictory flags. Which flag will apply when this happens?
There is another important reason to block this type of transaction. Lock codes are used in WMS (per Oracle's stated strategy) to represent the ERP subinventory. An LPN in WMS with an "FG" lock code is tracked in the ERP "FG" subinventory. LPNs with multiple lock codes cause integration issues. The inventory cannot be in multiple sub-inventories in ERP at the same time.
Can Combining inventory to one LPN with multiple locks be prevented from happening when using the Split/Combine screen?
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