Enhance Modify Cancel OBLPN Transaction to Transfer Inventory Lock Codes to IBLPN

We’ve enhanced the Modify/Cancel OBLPN transaction in Redwood Mobile to transfer inventory lock codes to the resulting LPNs. This enhancement allows you to modify or cancel OBLPNs with the correct lock codes, improving both flexibility and accuracy, especially in Return to Vendor process.

In case a lock code is applied to an OBLPN during or after packing, the system transfers the associated lock code to the corresponding IBLPN where the inventories are shifted through a modify/cancel operation.

For example, If an OBLPN has 5 (un-allocatable) units with Return to Vendor lock code. When you try to modify the OBLPN inventories to 3, the scanned IBLPN will have the RTV lock code transferred from the OBLPN inventory.  

Inventory History Transaction (IHT) UPDATES

When the Modify Cancel OBLPN transaction is dealing with lock codes:

Case 1: When the OBLPN has no lock code and modcanoblpn-lock-code has no default lock code configured, then the system writes IHT-29-Create Allocatable Container.

Case 2: When the OBLPN has no lock code and the module has default lock code configured (allocatable/unallocatable), then the system writes IHT-29-Create Allocatable Container or IHT-30-  Create Unallocatable Container depending on the default lock code is allocatable or unallocatable. The system writes IHT-23 Lock container for the default lock code and ERP bucket to populate accordingly. 

Case 3: When the OBLPN has 3 lock codes and the module has default lock code configured (allocatable/unallocatable), then the system writes IHT-29-Create Allocatable Container or IHT-30 - Create Unallocatable Container depending on the default lock code is allocatable or unallocatable. The system writes 4 times IHT-23 Lock container for the 3 lock codes and the default lock code. Lock code priority is honored if the parameter is enabled and ERP bucket to populate accordingly.

Steps to Enable

You don't need to do anything to enable this feature.