Integrate Cycle Count with Warehouse Control Systems

To streamline the cycle count process, you can integrate external Warehouse Control Systems (WCS), such as Automated Storage and Retrieval Systems (ASRS), Robotic arms, and Drones with Warehouse Management (WMS).

This integration allows seamless exchange of cycle count instructions between the WMS and WCS systems. This ensures effective cycle count execution and maintaining precise and up-to-date inventory data, ultimately enhancing the overall inventory accuracy of the warehouse.

With this integration, WMS can orchestrate cycle counting and send the required information to WCS and cycle counting performed by WCS can be recorded in the WMS.

Cycle Count Task Info Generation with MHE Systems

The “Cycle Count Task Info” output interface allows WMS to send the cycle counting instructions to the WCS. It contains the list of cycle count tasks that need to be executed externally (outside WMS).

To generate the output interface file “Cycle Count Task Info”, do the following:

1. Go to Task Creation Template (TaskCreationView) UI.
2. Click the icon to create a CC Task template.
   Note: You can edit the existing CC Task template also.
3. Select a CC Task Template and click details icon.
4. On the Task Creation Template > Details screen, click icon and configure the task creation template details with the following configuration:
   • Enable the checkbox “Release Cycle Count Task Info File”
   • Select an MHE Code from the “MHE System” drop-down
   Note:

   • If you configure “CC-LOCN-LPN-CNT” task type, when the “Release Cycle Count Task Info File” flag is enabled, the system displays an error message “Cannot use container count task type when 'Release Cycle Count Task Info File' is enabled”.
   • If the cycle count task template detail is enabled with “Release Cycle Count Task Info” flag, only then the system generates the “Cycle Count Task Info” JSON file.
   • The drop-down field “MHE System” selection is optional. Select an MHE code that you want to integrate and make sure that the selected MHE system is configured for the “Cycle Count Task Info” output interface. If the selected MHE code is blank, make sure the output interface “Cycle Count Task Info” is configured for blank.
   • The system fetches these MHE codes from the MHE System (MheSystemView) UI.
   • The system generates and integrates the “Cycle Count Task Info” output interface file with the MHE system configured in the Output Interface Configuration (OutputInterfaceConfigView) UI.
5. Click Save.
   Note: You must configure either the “Item Selection Criteria” or the “Selection Criteria” for the task creation template details.
6. Once the configuration is complete, select the newly created task creation template on the Task Creation Template UI and click the Run Template action button.

   The system creates cycle count tasks based on the configured task creation template. 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).

You can view the created cycle count tasks on the Tasks (TaskView) UI, along with the MHE System and Release Cycle Count Task Info File columns. Also, you can view the created cycle count tasks with the Release Cycle Count Task Info column on the Cycle Count Run (CCRunView) > Task List screen.

To regenerate the “Cycle Count Task Info” file for including any cycle count tasks available during the task creation process, you can utilize “Regenerate CC Task Info” action button on the Cycle Count Run UI.

Key Points for Consideration:

• 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 the MHE proceeds with executing the task despite the cancellation, it will be treated as a standalone task initiated 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.
• When attempting to execute a cycle count task via the RF Execute Task transaction, if the “Release Cycle Count Task Info File” flag is enabled, 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” 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”.
• 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.

Cycle Count List API

After completing the cycle count tasks orchestrated in WMS, you can send the cycle count data from WCS to WMS through “Cycle Count List” API in JSON format. Also, WCS can perform standalone cycle counts as well and send the count details to WMS using the same API, without a task number.

URL:

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

For more details about “Cycle Count List” API, refer to the WMS REST API Guide.

On successful processing of the payload, the system creates cycle count adjustment records or updates the inventory adjustments based on the deferred or immediate mode. You can view these processed cycle count records on the From MHE Cycle Count Info (FromMheCycleCountInfoHdrView) UI. If any failed records, you can select and reprocess these records using the action button Reprocess Failed Record.

Note:

• 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.
• The Cycle Count List API doesn't support LPN Count mode (CC-LOCN-LPN-CNT) and counting consumed LPNs.
• For a location driven cycle count (CC-LOCATION), if LPNs are not passed in the payload, the system moves the unscanned LPNs to Lost status.

Cycle Count Adjustment Validations

• After sending Cycle Count Task Info to a MHE system, if you execute a standalone cycle count in WMS, the system displays a warning message. On accepting the warning message, you can proceed with the cycle counting."
• The system handles and processes data from the "Cycle Count List API" in various scenarios:
  • When a cycle count task already exists for a location in WMS, and MHE sends a cycle count list for the same location (standalone count).
  • If WMS has approved or canceled the cycle count adjustment records for a location and MHE sends the cycle count list for the same location.
  • In cases where cycle count adjustment records are rejected, the system generates a new cycle count task as a trigger, and MHE sends the cycle count list for the same location.
  • If you are performing a standalone cycle count in WMS, MHE sends the cycle count list for the same location.
  • If a location doesn't allow multi-SKU, MHE sends a different SKU for the same location in the deferred mode. Note that the system fails the approval of the cycle count record.
  • If a location doesn't allow multi-SKU, MHE sends a different SKU than the dedicated one for the same location in the deferred mode. Note that the system fails the approval of the cycle count record.
  • MHE sends a cycle count list for a location with a different pack or case quantity than the item’s pack or case quantity in the deferred mode. Note that the system fails the approval of the cycle count record.
  • If a location has the “restrict_batch_nbr_flg” set to Yes and MHE sends a cycle count list for the same location with multiple batch numbers for the same SKU in the deferred mode. Note that the system fails the approval of the cycle count record.
  • If item is tracking batch and expiry and MHE sends a cycle count list with a new batch without an expiry date in the deferred mode. Note that the system fails the approval of the cycle count record.
  • If a location has the “restrict_invn_attr_flg” set to Yes and MHE sends a cycle count for the same location with multiple attributes in deferred mode. Note that the system fails the approval of the cycle count record.
  • MHE sends a cycle count list for a serial-tracked item with CC UOM is either pack or case quantity in the deferred mode. Note that the system fails the approval of the cycle count record.
  • If a location has allocations and MHE sends a cycle count list for the same location in the deferred mode (where the counted quantity is greater than the allocated quantity).
  • If a location has inventory from unverified shipments and MHE sends a cycle count list for the same location.
  • If the scanned LPN is in “Partially Allocated” or in “Allocated” status and MHE sends a cycle count list for the same location in the deferred mode. Note that the system fails the approval of the cycle count record.
• The system displays an error message and fails the cycle count list for the task or location in the following scenarios:
  • MHE sends a cycle count list with an invalid location.
  • MHE sends a cycle count list with a location linked to a different facility.
  • If you are performing a standalone cycle count (CC adjustment records are in progress status) in WMS and MHE sends a cycle count list for the same location.
  • When cycle count adjustment records are pending for approval and MHE sends a cycle count list for the same location.
  • When a cycle count task is in-progress for a location and MHE sends a cycle count list for the same location.
  • MHE sends a cycle count list with an invalid item.
  • MHE sends a cycle count list for an item count that is associated with a different company than the dedicated company of the location.
  • If a location is not dedicated and MHE sends a cycle count list for an item from a different company than previously counted.
  • In the immediate mode, If the location doesn’t allow multi-SKU and MHE sends a cycle count list for an item that differs from the previously counted item. The system processes the records if the location is empty or the scanned SKU matches the location's SKU.
  • In the immediate mode, If the location doesn't allow multi-SKU and MHE sends a cycle count list for a SKU other than the dedicated one. The system processes the records if the scanned SKU matches the dedicated SKU.
  • MHE sends a cycle count list for a location with a different pack or case quantity than the item’s pack or case quantity in the immediate mode.
  • If an item doesn’t support decimals and MHE sends a cycle count list with the counted quantity in decimals for the same item.
  • If a location has the “restrict_batch_nbr_flg” set to Yes and MHE sends a cycle count list for the same location with multiple batch numbers for the same SKU in the immediate mode.
  • If item is tracking batch and expiry and MHE sends a cycle count list with a new batch without an expiry date in the immediate mode.
  • If a location has the “restrict_invn_attr_flg” set to Yes and MHE sends a cycle count for the same location with multiple attributes in immediate mode.
  • If the company parameter “SERIAL_NUMBER_TRACKING_LEVEL” set to 2 and MHE sends a cycle count list for a serial tracking item without serial numbers.
  • MHE sends a cycle count list for a serial-tracked item with a serial number that is associated with an inventory record of a different facility.
  • MHE sends a cycle count list for a serial-tracked item with CC UOM is either pack or case quantity in the immediate mode.
  • In cases where the count mode is immediate, and the location has allocations. MHE sends a cycle count list where the counted quantity is less than the allocated quantity, the system displays an error message “Count Qty for is less than allocated Qty, cannot proceed further, item% location%”. For example, if the expected quantity for an item in a location is 10 and 8 units are allocated, cycle count of 7 will not be accepted in the immediate mode. However, in deferred mode with auto-approve, the system records the cycle count as a pending inventory adjustment but will not be approved.
  • MHE sends a cycle count list for a location with an LPN in “Quality Check” or “In-Receiving” status.
  • MHE sends a cycle count list for an LPN that is associated with a different company than the dedicated company of the location.
  • In cases where the count mode is immediate, and the scanned LPN is in “Partially Allocated” or in “Allocated” status. MHE sends a cycle count list where the counted quantity is less than the allocated quantity, the system displays an error message.

Note:

• When the system fails the cycle count list for the task or location, the system processes the other tasks or location cycle counts that are sent in the same payload.
• 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.

3PL Company Scenario

Consider, a 3PL Master Company “MC” has two child companies “C1” and “C2”. The following table briefs the behavior of Cycle Count List API:

Scenario	Deferred Mode Updates	Immediate Mode Updates
An LPN (LPN1) exists across companies “C1” and “C2” with different SKUs and you are counting a reserve location RES1 (empty and allows multi-SKU, not dedicated to any company)	If you send a SKU that doesn’t exist in the company specified in the payload, the system displays an error message “Invalid item”. If you send a valid SKU that exist in the company specified in the payload, after approval, the system updates the company code of the location with the payload’s company code. The system dedicates the location to the company code you passed in the payload and is not allocated for SKUs of other companies.	If you send a SKU that exist in the company that you are passing in the payload, the system updates the company code of the location with the company code you passed in the payload. The system dedicates the location to the company code you passed in the payload. The system doesn’t allocate the location for other SKUs of other companies.

Note:

• The above scenario applies when a user has access to all companies in the 3PL environment.
• Updates are limited to the company that you are passing in the payload and the system references the shared LPN data within that company.