Cycle counting through MM at R6

We have an issue with the cycle count process using MM at R6. Our issue is that we love the way we can set up MM for cycle counting by particular area of our plant based on subsets within the Warehouse Locations object, that part of the process works slick for our needs and is easy for the people to use.

Our problem is that we are mandated by our corporate office to count a certain amount of A, B, and C type items which are set based on usage in the VALUC field in the ITEMASA file.

We then programmatically set the date of last count in ITEMBL to be offset 3 months for A items and set the CYCLE COUNT CODE for these items to 2; set the date of last count in ITEMBL to be offset 6 months for B items and set the CYCLE COUNT CODE for these items to 3; and set the date of NEXT count to the current date for C items and set the CYCLE COUNT CODE to a 4.

Where we run into our problem is explained in this scenario:

We decide we need to count 30 A items daily, 30 B items daily, and 30 C items daily. The problem is, if we set the date and cycle count codes for 30 of each of these, by the time the Mapics MM program goes out to SLQNTY to get the actual items to count these numbers could be much higher or lower due to the potential one-to-many relationship between ITEMBL and SLQNTY making it very difficult for us to stay within our corporate guidelines for count penetration.


We've looked at potentially offline loading the cycle count items but were just curious as to whether anybody else has seen this issue and how they addressed it.

Thanks,
Mike Smith
IT Manager
Thomas & Betts Reznor