One of your ideas has been delivered from your suggestion.Optimize Cycle Counting through Integration with Warehouse Automation

To streamline the cycle count process, we have introduced integration for external Warehouse Control Systems (WCS), such as Automated Storage and Retrieval Systems (ASRS), robotic arms, and drones, with Warehouse Management (WMS). We have implemented a mechanism that facilitates communication between WMS and external WCS.

Through this mechanism, cycle count instructions are conveyed from WMS to WCS, and the count details are transmitted back to WMS. To enable this communication, we have developed new input and output interface that can be seamlessly integrated with various automation solutions. These interfaces act as a bridge, allowing WMS to orchestrate cycle counting and receive accurate inventory date from the WCS. This ensures effective cycle count execution and maintains precise and up-to-date inventory data, ultimately enhancing the overall inventory accuracy of the warehouse.

INTERFACE CHANGES

To facilitate communication between WMS and WCS, we have added the following input and output interfaces:

  • A new output interface file “Cycle Count Task Info” in JSON format is added to send cycle count task data from WMS to WCS. You can configure this file on the Output Interface Configuration (OutputInterfaceConfigView) UI.
  • A new API “Cycle Count List” in JSON format is added to send the cycle count details from WCS to WMS.

UI CHANGES

To support Cycle Counting with Warehouse Automation, the following enhancements are made:

  • A new flag Release Cycle Count Task Info File and a new drop-down field MHE System are added to the Create/Edit panes in the Task Creation Template (TaskCreationView) > Details screen. These are applicable only for the “CC” type task creation template. The system fetches these MHE codes from the MHE System (MheSystemView) UI.
  • Two new columns MHE System and Release Cycle Count Task Info File are added in the Tasks (TaskView) UI.
  • A new column Release Cycle Count Task Info File is added in the Cycle Count Run (CCRunView) > Task List screen.
  • On the Cycle Count Run UI header, a new action button "Regenerate CC Task Info" is added. You can utilize this action button to regenerate the “Cycle Count Task Info” file including any cycle count tasks available during the task creation process.
  • A new UI From MHE Cycle Count Info (FromMheCycleCountInfoHdrView) is added to capture and display records that are processed based on the “Cycle Count List” API.
  • The From MHE Cycle Count Info UI features a new action button “Reprocess Failed Record”, enabling you to reprocess the selected failed records.
  • The From MHE Cycle Count Info > Details screen includes a column “View Serial Number” that displays the hyperlink to the serial numbers associated with the stage detail record.

NOTE: Though the system creates tasks for reserve locations, we are restricting the “Cycle Count List” API to accept reserve location cycle count tasks for this release. We will support reserve location MHE cycle count updates in future releases. If you send reserve location cycle count data via “Cycle Count List” API, the system displays an error message. In 25A, we are supporting only active locations.

API CHANGES

We have introduced a new API to support the “Cycle Count List” in JSON format. Here are the API details.

URL

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

On successful execution of the interface, the system creates cycle count adjustment records or updates the inventory adjustments based on deferred or immediate mode. For more details, refer to the WMS REST API Guide.

NOTE: In this release, processing of payload is applicable only in async mode.

POINTS FOR CONSIDERATION

  • If the cycle count task template detail is enabled with “Release Cycle Count Task Info File” flag, only then the system generates the “Cycle Count Task Info” JSON file.
  • If you cancel a cycle count task in the Task UI, the system creates the “Cycle Count Task Info” JSON file with “Cancel” action code. So that MHE does not execute the task. However, if MHE continues to execute the task despite the cancellation, the task execution will be treated as a standalone task orchestrated by the MHE.
  • The system populates the item list in the “Cycle Count Task Info” JSON output interface file only for the item driven cycle count tasks.
  • If you try to execute a cycle count task with the “Release Cycle Count Task Info File” flag enabled via the RF Execute Task transaction, the system displays an error message “Cannot execute task as its exposed to external system”.
  • If you click “Regenerate CC Task Info” on the Cycle Count Run UI and there are no eligible cycle count tasks for file generation (“Release Cycle Count Task Info File” flag is disabled for all task), the system displays an error message “No eligible TASKs found”.
  • If you regenerate cc task info for multiple CC Run Numbers, the system displays the successfully processed task count in a pop-up message “Cycle Count Info file generated for %SUCCESS task out of %TOTAL_CNT”.
  • After processing the “Cycle Count List” API, the API honors the existing company and facility parameters “INVN_ADJ_APPROVAL_REQUIRED” to update inventory.
  • If you are in immediate mode, the system updates the inventory adjustment without approval. If you are in deferred mode, the system creates the inventory adjustment records for approval.

NOTE:

  • The system currently generates the “Cycle Count Task Info” output interface file, that includes cycle count task and location details, when the “Release Cycle Count Task Info File” flag is enabled.

  • You can define the MHE system in the Task Creation Template (TaskCreationView) > Details screen. Then, the system generates one common output interface file per task creation template. Now, there is no selection criteria for the “Cycle Count Task Info” output interface target. Hence, we recommend utilizing one MHE code for each task creation template.

  • The MHE code generated in the “Cycle Count Task Info” output interface file should match the MHE code provided in the output interfaced target.

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.