Logic for Cycle Interval When Creating Count Reports

Hi everyone,

I’m trying to establish a cycle count program using count reports and I’m having an issue with the business logic being used to add lines to the count report. I’m finding a disconnect between the cycle interval on the inventory part, and the last date an inventory part has a COUNT-IN or COUNT-OUT transaction. It appears the ‘Last counted date’ which is being fetched by the Get_Last_Count_Date function,  is populated on the inventory part in stock, but is granular down to the part/config/location/lot/serial/ecn/wdr/handling unit combination. So if I count a part at a specific location, then move it, the last counted date will be lost. 

My interpretation of the cycle interval logic is as follows. If the cycle interval on the inventory part record is 60, and the part is counted on October 1st, then the next time the part would be fetched and added to a count report would be December 1st. (our distribution calendar is 7 days a week @ 24 hours a day). My testing has completely different results than this expectation. Am I interpreting the use of the cycle interval incorrectly? 

The help says the cycle interval is “The interval, in working days, for cycle counting. I.e., the period between one automatic count and the next.”

Does anyone have any experience working with this logic?

Thank you