Task Manager/RF-directed cycle count configuration

This section describes:

  • Scheduled cycle class task generation.
  • Steps for configuring the application to generate Task Manager/RF-directed cycle counts

Cycle class

A cycle class is a set of parameters you can apply to an item. These parameters enable the application to automatically generate cycle counts for items. It also determines an acceptable range of variance and the variance level that would require a manual override.

You must assign cycle classes to items based on parameters in the cycle class. The application generates cycle counts in the Task Manager/RF-directed task queue when released through the Cycle Count Generation screen.

RF-directed cycle counts

RF-directed cycle counts are driven by the Task Manager. Count tasks are distributed to associates in location sequence for the area in which the associate is authorized to perform cycle count tasks. With RF-directed cycle count, adjustments to inventory are performed automatically unless the last amount logged is outside of pre-defined variances.

For each count task the associate performs, information is recorded in the cycle count tables at Execution > Cycle Count > Maintenance. One cycle count header record is created for each count task. A cycle count detail record is created for each count the associate performs for the count task.

Example 1: An associate is given a count task, performs the necessary count, does not violate any variance constraints, and presses Esc to finish and accept the count. One header and one detail are created. In this instance, the header record has a Posted status, the detail record has a Posted status, and any necessary adjustments to inventory are made if the owner is configured to allow adjustments during RF-directed counts. If the owner is not configured to allow adjustments during RF-directed counting, the header record and the detail record status is Not Posted.

Example 2: The associate is given a count task, performs the necessary count, and violates a variance constraint. One header record is created with an Out of Variance status, and one detail record is created with an Out of Variance status. If the associate chooses to count the location again, a new detail record is created with the count information and is given the appropriate status.

Example 3: The associate is given a count task, performs the necessary count, and violates a variance constraint. If the cycle class assigned to the item being counted is set to create Supervisor Counts then a Supervisor Count will be created. One header record is created with a Supervisor Count status, and one detail record is created with a Supervisor Count status. If the associate chooses to count the location again, a new detail record is created with the count information and is given the appropriate status

You can continue this process until no more count tasks are available for dispatch.

Note: 
  • The Last Cycle Count date in the Item screen (Cycle/Costs tab) is updated when the cycle count tasks are generated from a Release Cycle Count.
  • If you attempt to exit the screen without performing a cycle count, you must provide a valid reason code.