For the record, this evening I was able to clear that field out via a DMT (version 2024.1.9) on the Part Warehouse table simply by doing an update with that column blank for the respective company, part, plant, warehouse. Then ran the Initialize dates program to have them repopulated. It was much faster than the clear last cc date datafix that I got from support.
I don’t know if this is true, because after getting off with Support I tried setting my calendar back to it’s original 4-days and was able to get parts selected still. Maybe it doesn’t like doing it the first time with only four days or there was something else amiss with my dates that was the real issue and the passage of time corrected it.
Either way, if the five day calendar thing is true, then I found that I could easily schedule a period and when it creates the five sequences you can simply select the last sequence, delete it to reduce the count days down to four, and then run part selection.
We have many of our branches scheduling only a few days. We actually recommend setting the branch counting calendar to 4 days so that Friday gives them a “catch up” day. Our Quebec branch has only one day per week for counting, for example.
Our normal sequence of events is the HR department maintains the master production calendar for each branch and then we make a copy for cycle counting and adjust from there. This makes it that we don’t generate cycles on holidays.
Yeah, I’m not convinced that it was the shortened calendar that was causing the issue, but rather something not obvious with my dates.
Perhaps such as: although the period dates were in the future far enough out from my last cycle count dates, the system was somehow using the date of the day I was trying to run the part selection process to determine which parts to select and not actually using the period dates.
@d_inman I wanted to thank you for having this discussion. I have a new company that we just imported all of the parts in and I could not get parts to be selected. I had run initialize, but @Graemer’s point about having to null them first was the answer. I used your method of DMT with the empty column and then I got parts. Then just to test I set a three day calendar and got counts.
I ran the nulling and initializing a few time to watch the dates and depending on the count frequency it set the dates so based on the code they would all get counted within the cycle. I guess setting LastCCDate to the date added for new parts is random enough if you have been running Epicor for a while, but if you are starting to do counts it is a problem.
You’re very welcome! It’s what I love about this community and happy to contribute something helpful when I can.
Your experience confirms for me that my original issue was date related, rather than calendar related as support suggested. Marking your response as the answer, since it concisely states what works.
