Example of Generating More Count Schedules Than Expected

There are times when more count schedules are created for an item in a cycle count than you expected based on your entered scheduling frequency.

For example, multiple count schedules might be created for an item in the cycle count when the items are only supposed to be counted once per year. This example describes how this can occur.

Classes

Let’s say you have three classes in a cycle count.

On the Create Cycle Count: Define Classes and Items page, you define three classes in the cycle count:
  • Class 1 has 284 items with 4 counts per year
  • Class 2 has 402 items with 2 counts per year
  • Class 3 has 1249 items with 1 count per year

Frequency

On theCreate Cycle Count: Define Schedules and Approvals, you set the Frequency to Daily.

Calculations

Let’s assume there are 260 working days in a year. The count schedule is run every day.

Here’s a summary of the count schedule calculations and the resulting number of items scheduled per day:
Class Number of Items Counts per Year Counts Calculation Number of Items Scheduled per Day
Class 1 284 4

(284*4)/260 = 4.4

Since this is a decimal, we take the next integer. So, we schedule 5 items for Class 1 per each day schedule.

5 items per day
Class 2 402 2

(402*2)/260 = 3.1

Since this is a decimal, we take the next integer. So, we schedule 4 items for Class 2 per each day schedule.

4 items per day
Class 3 1249 1

(1249*1)/260 = 4.8

Since this is a decimal, we take the next integer. So, we schedule 5 items for Class 3 per each day schedule.

5 items per day

Let’s look at the actual number of items scheduled per day for Class 3. Since 5 items are scheduled per day for Class 3 instead of 4.8, 51 items are counted two times per year instead of one time per year.

(5 items per day * 260 days = 1300 items)

[1300 items - (1249 items * 1 count per year)] = 51 items

The number of counts per year is honored, but when we get a value that’s not an integer for the number of items to be scheduled, we must take the next integer. This might result in counting a few percentages of items one time more than the scheduled frequency.