Facilitate Recovery of Consumed IBLPNs through Cycle Count Location

We have enhanced the cycle count flow so that, you can now scan Consumed LPNs during a location-driven detailed cycle count. Sometimes, during warehouse operations, an IBLPN is marked as “Consumed” in the system by operational mistake, even though it is still physically available in the facility.

This can occur in the following situations:

In pick operations, when an IBLPN is scanned during replenishment to an active location, but it is not moved to the correct location.
When an IBLPN is moved without being properly updated in the system.

Until now, correcting these records required the Inventory Controller to manually go to the floor and create a new IBLPN to re-introduce the inventory into the system. Now, with this enhancement, the system lets you easily revive these LPNs if they are found in the warehouse. This helps you to keep your inventory records accurate.

To provide the compatibility to consider consumed LPNs, the following are enhanced:

The existing screen parameter “allow-new-lpn-scan” for the module rf.inbound.cwrfcyclecountlocn.
The existing field “allow_new_lpn_count_flg” for the “cycle_count_list” API.

The following table details the behavior of the screen parameter “allow-new-lpn-scan” and the field “allow_new_lpn_count_flg”:

Configuration	Behavior
For the Cycle Count Location mobile transaction, when “allow-new-lpn-scan” = “Yes” For the cycle_count_list API, when “allow_new_lpn_count_flg”= “TRUE”	The system allows auditors to scan consumed LPNs along with canceled or new LPNs during detailed cycle counting. NOTE: The system allows consumed LPNs only for the location-driven detailed cycle count. It is not supported for the “CC-LOCN-BY-ITEM” task type. However, the system supports scanning of new or canceled LPNs to perform both location-based and item-based detailed cycle counts.
For the Cycle Count Location mobile transaction, when “allow-new-lpn-scan” = “No” For the cycle_count_list API, when “allow_new_lpn_count_flg”= “FALSE”	Default behavior: The system does not allow auditors to scan consumed, canceled, or new LPNs during cycle counting.

Configuration

Behavior

For the Cycle Count Location mobile transaction, when “allow-new-lpn-scan” = “Yes”
For the cycle_count_list API, when “allow_new_lpn_count_flg”= “TRUE”

The system allows auditors to scan consumed LPNs along with canceled or new LPNs during detailed cycle counting.

NOTE: The system allows consumed LPNs only for the location-driven detailed cycle count. It is not supported for the “CC-LOCN-BY-ITEM” task type. However, the system supports scanning of new or canceled LPNs to perform both location-based and item-based detailed cycle counts.

For the Cycle Count Location mobile transaction, when “allow-new-lpn-scan” = “No”
For the cycle_count_list API, when “allow_new_lpn_count_flg”= “FALSE”

Default behavior: The system does not allow auditors to scan consumed, canceled, or new LPNs during cycle counting.

NOTE: Post inventory adjustments, the system updates the LPN status to “Located” and creates reserve inventory records.

Steps to Enable

To allow consumed LPN scan in the Cycle Count Location (rf.inbound.cwrfcyclecountlocn) mobile transaction (for Reserve Location detailed count), enable the screen parameter “allow-new-lpn-scan”.

To scan consumed LPNs in the “cycle_count_list” API (for Reserve Location detailed count), set the field “allow_new_lpn_count_flg” to “TRUE”.