One of your ideas has been delivered from your suggestion.Warehouse Automation Driven Cycle Counting for Reserve Locations

You can now streamline the exchange of cycle count instructions and details between the Warehouse Management System (WMS) and Warehouse Control System (WCS) for Reserve locations. We have enhanced our support for reserve location cycle counting with Warehouse Automation, providing an accurate and comprehensive cycle count of your inventory.

You can now send the cycle count information of reserve locations from external WCS such as ASRS, Drones etc., using the “Cycle Count List” API and subsequently create relevant inventory or cycle count (CC) adjustment records.

After executing a cycle count task creation template, based on the MHE Code configuration, the system sends the “Cycle Count Task Info” output interface file to the respective external Warehouse Control Systems (WCS).

The following “Cycle Count List” API now processes the reserve location cycle count information.

URL

POST .../wms/lgfapi/v10/cycle_count_info/cycle_count_list/

On successful execution of the API, the system creates an individual cycle count info header record on the “From MHE Cycle Count Info” UI for each reserve location and either updates the inventory records or creates cycle count inventory adjustments based on immediate or deferred mode respectively.

For more details on configuring the cycle count automation, refer Integrate Cycle Count with Warehouse Control Systems.

NOTE:

  • Processing of Cycle Count List API payload is applicable only in async mode.

  • Cycle Count List API doesn't support counting of consumed LPNs.

  • When the parameter “allow_new_lpn_count_flg” is set to “true”, then the API allows you to update the inventory or create CC adjustment records with new or cancelled LPNs.

  • When the parameter “lpn_scan_flg” is set to “true”, you can only send the LPN barcodes to perform “Reserve Location LPN Scan” mode. In this case, if you send the inventory details for the LPNs, the API fails.

  • Automated cycle count is not applicable for LPN Count mode (CC-LOCN-LPN-CNT).

  • For a location driven cycle count (CC-LOCATION), in the payload, if you didn’t send LPNs, the unscanned LPNs will be moved to Lost status.

Steps to Enable

To generate an output interface file “Cycle Count Task Info” with list of cycle count tasks, do the following:

  1. From the Task Creation Template (TaskCreationView) > Details screen, create a CC task template detail with the following configuration:

    • Enable the checkbox “Release Cycle Count Task Info File”.
    • Select a code from the “MHE System” drop-down.

  2. Select the configured task creation template and click Run Template action button.

The system creates cycle count tasks based on the configured task creation template. Also, it creates the “Cycle Count Task Info” file with “Create” action code (if cycle count tasks are created in Ready/Held status and are enabled with “Release Cycle Count Task Info File” flag).

NOTE:

  • When the “Release Cycle Count Task Info File” flag enabled, the system restricts task template detail creation for task type with screen RF Reserve LPN Number Count (rf.inbound.cwrfccresvnbrcount). In the above case, the system displays an error message “Cannot use container count task type when 'Release Cycle Count Task Info File' is enabled.”.

  • The drop-down field “MHE System” selection is optional.

  • The system generates and integrates the “Cycle Count Task Info” file with the MHE System configured in the Output Interface Configuration UI.

Key Resources