Trigger Item-Driven Cycle Count during Active Location Short Picks

When SKUs are short picked from an active location, the system creates a cycle count task for the entire location based on cycle count trigger. Auditors need to count the entire location instead of counting only the short picked SKUs which may not be ideal. Also, active locations may contain multiple SKUs. When a few SKUs are short picked from an active location, you are forced to cycle count other SKUs that are not included in the picking task. Now, we are introducing a new feature to create item-driven cycle count tasks for the short picked SKUs in active locations.

When a picker short picks a SKU from an active location (due to missing, damaged, or unavailable inventory), the system can now trigger a cycle count task only for the short picked SKU, not for the entire location.

This provides the following advantages:

• Inventory Operators can count only the short picked SKUs, not the entire location.
• Reduces unnecessary cycle counts, saving both time and resources.
• Item-specific cycle count speeds up inventory discrepancy resolution for the short picked SKUs.

NOTE: This applies only for short picking from active locations (not reserve locations).

To trigger item-driven cycle count task creation for the short picked SKUs in an active location, we have enhanced the Short pick active trigger. In the Cycle Count Trigger Management (CCTriggerMgmtView) UI, you can now select a “CC-LOCN-BY-ITEM” task type for the Short pick active trigger.

Once you configure the Short pick active trigger with a “CC-LOCN-BY-ITEM” task type, when you short pick SKUs from an active location, the system creates item-driven cycle count tasks for the short picked SKUs at the active location.

This applies to the following mobile transactions and API:

• Pack NC Active Order (rf.outbound.cwrfpackncactiveorder)
• From MHE Pick Confirmation API when “short_flg” is set to True
• Pick Cart (rf.outbound.cwrfpickcart)
• Pick IBLPN (rf.outbound.cwrfpickiblpn)
• IBLPN Pick for Consolidation and Replenishment (rf.inbound.cwrfpickiblpnreplen)

NOTE: If a CC-LOCN-BY-ITEM task already exists (in Ready status) for a location and doesn’t include the short picked SKUs, the system appends the newly short picked SKUs to the same task.

This applies only when the “CC-LOCN-BY-ITEM” task type is same. If the task type is different, the system creates a new item-driven task for the short picked SKUs.

POINTS FOR CONSIDERATION

• If a location-driven cycle count (CC-LOCATION or CC-LOCATION-DTL) task exists for a location, the system doesn’t create item-driven cycle count tasks for the short picked SKUs for the same location.
• The system groups all short picked SKUs at a location into the same cycle count task.
• When summary count discrepancy, alternate location picking, or picking to zero triggers are triggered for a location, the system cancels existing item-driven tasks associated with the location (created via the “Short pick active” trigger) and creates a location-driven cycle count task for the location.

Steps to Enable

To trigger item-driven cycle count task creation for the short picked SKUs in an active location, on the Cycle Count Trigger Management UI, select “CC-LOCN-BY-ITEM” task type for the Short pick active trigger.