Cycle Count

[Jan_Stas]

We would like to use the Next Count Date in our cycle count selection. When testing in PY we saw that at the moment of receipt the Next Count Date doesn't get filled in. As we use lot control our receipts are strictly counted and we don't want to make our users count every receipt to get the next count date filled in. Any ideas to solve this problem. Thanks a lot in advance.

 

[ame]

How do you count your items... by lot number or by item or by location.. in
other words... on Monday when I go to do a cycle count... will I select
particular items or a particular location? One idea is to use the ABC
analysis on the items and set A items to be a certain time period B ...
etc... and then run a UBE to populate the next count date. Another idea is
if all the items are counted on the same day (like all item A counted on
10/20)... and you just receive in a new lot number of Item A on 10/21...
that you run a UBE to populate the new lot's cycle count date with whatever
was calculated on the other lot numbers. Just a couple of ideas. thanks,
Bobby

 

[jeremey_garcia]

There is a process that needs to be followed prior to next count date gets filled in. Once you count the items, and input them, then you need to approve the count. Once the count has been approved then the next date is filled in. We learned this the hard way. We now have to go through and reset (manually) all our count criteria and dates.

 

[Jan_Stas]

Thanks a lot for your input.
Just wondering. Bobby talked about running a UBE. Is that a standard UBE or one that we have to write ourselves?

 

[Tim Lyons]

There is not a pre-defined UBE for initially populating the next count date. You should carefully consider how you might want to do this. In general, cycle counting is based on counting the same number of items each day (or each week). The number of items to be counted is determined, at least in part, by the resources available to do the counting and reconciliation. Then, you need to consider different frequencies for different types of items, as has already been suggested. If you don't aproach this in a systematic way, the number of items to be cycle counted could vary tremendously from day to day or week to week.
Many companies begin by manually selecting items to be cycle counted until all or most have been counted, then let the system do the selection based on next count date. You could also write a UBE to assign a next count date, but this would still involve a manual selection process to decide how to assign the dates. It's always a good idea to have a report listing items without a next count date, so new items aren't overlooked.