I am running a cycle count in our system, I am expecting to see around 6 parts to count each and every day. The result is an initial smaller number, and then lots of zero’s. I have outlined the steps taken below. If anyone has any insight on what I maybe doing wrong here, then that would be greatly appreciated.
Steps taken:
Review of the ABC codes
ABC Code
ABC Code
Exclude?
Stock Valuation
Count Frequency
A
No
80
7
B
No
89
14
C
No
96
60
D
Yes
100
180
Calculate ABC Codes
Historical Usage From [4 months prior to today]
Projected Usage Through [4 months post today]
Include Projected usage TICKED
Include Current On-hand TICKED
Update ABC Codes TICKED
Schedule Now
Calculate ABC Codes Report generated, and this produced 279 A, 179 B, 344 C, 870 D.
Cycle Count Period Definition
New period created, Period Start [today] Period End [4 months post today]
Cycle Count Schedule Maintenance
New
Warehouse chosen
Current year chosen
New cycle period chosen
Saved
Perform Part Selection [Parts Selected red box appears]
I’m not sure exactly but my gut tells me that the conflict may lie with the fact that the ABC code setup for Count Freq is in Days, and your period is 4 months. Plus you don’t mention what the Part/Site/Whse, Warehouse, and Site cycle count configuration details are. Everywhere except ABC codes, the Count Freq is in months and that might be in conflict with what you are trying to calculate.
so you want the A items counted every 7 days? If that is the case, you need to have your cycle periods last only 7 days… reason… a part can only be in one period at a time. If you have your cycle periods set to 28 days (4 weeks) but want your A items counted once per week, it will not work.
Thank you Tim. On a related note, back at the earlier stage of calculating ABC Codes, there are parts on the report where the last CC date shows as far back as 2013. Is there a way for the system to ‘reset’ the CC dates so they all show as being last counted today for example?
Not exactly. But it is a VERY common request, and if you put in a ticket with Epicor Support (EpicCare), they are always very fast to respond with a data fix.
I have had to ask for it many times. It’s unique to the version you are on, which is why I can’t reuse the same one over and over.
And then after that you would do the “initialize lastccdate” process, or whatever it is called.
The program to “Set last CC Date” only works if the last cc date is blank.
The Cycle Count program design came from one of our legacy products… in that product, it actually had an option to “reset” the last cc date… somehow that feature never made it into ERP/Kinetic. It would be a great (and simple) enhancement to add a checkbox to that program to allow the resetting of the last cc date for ALL parts. Note that the “workaround” that tech support gives basically clears out all the dates to null, and then the program will set it again. How does the Reset last CC Date work? Well, it takes all the parts that do not have a last date, and it assigns a random date in the past… the date it assigns is sometime in the X days that is assigned to the ABC Code… so, if you cycle count C items every 365 days, then every C item will be assigned a random date sometime in the last 365 days… if A items are every 60 days… then they will all get a date in teh last 60 days.