We are in the process of setting up cycle counting and going through everything in our Test environment. We are planning to run this on two different warehouses so that parts in each can be counted with different frequencies: one our stocking warehouse and currently the only warehouse we have in Live; the second a new “Production” warehouse. However, I am unable to get any parts to be selected or selected in Cycle Count Schedule Maint.
Both warehouse records exist for all active parts in PartWhse table and an ABC code has been applied to each one. We will be manually maintaining our ABC codes, so I have not bothered to enter anything regarding value in the ABC setup for each warehouse. I’ve made sure that there are no open cycle counts, that all of the parts have a last cycle count date outside of the expected count period, and that there is a quantity on hand for the parts.
For example, the first period I am trying to schedule in the new Production warehouse is for 1/5/2025-1/11/2025 with a production calendar that is setup for Mon-Thu. There are only 10 A parts in this warehouse that all have a Last CC date of 12/10/2024 or 12/13/2024 and a count frequency set to 5 with Exclude Zero QOH checked by default. Would expect to see all 10 parts be selected for the period with 2-3 in each of the 4 count days.
I even went ahead and created the 2025 fiscal year and monthly periods, made sure the January period is open and transferred balances from 2024 to 2025. So far, nothing that I have done selects any parts. Am I missing something or is there a known bug around this in 2024.1.9??
Expand for screenshots of my settings for reference:
We’re doing the same thing hoping to go live sometime in 2025. We’re on an older version, but I will list our steps below, maybe you can spot what you’re missing:
define ABC codes
assign ABC codes to Parts (Part Entry / DMT)
create cycle count period (Cycle Count Period Definition Maintenance)
Is there a reason you are overriding count frequency in your PROD warehouse?
The parts in question are all flagged as stock on that site?
If you add the parts manually through Cycle Count Part /PCID Selection Update, do you get an error?
If you don’t get an error when manually adding them, if you were to go through the process, do you get any errors at any point through posting and posting gives you the expected changes?
Thanks for listing out the steps. Those are the same ones we are following. This step is where we get hung up. We can create the Schedule, but when we do it does not list any number of parts to be selected and when we run the “Select Parts” process it doesn’t select any.
Honestly, checked that to see if had any impact, because it hadn’t previously been checked and the warehouse level is where we want all of this driven from, so I checked it to see if it would resolve my issue. It did not. Though the Prod warehouse is what I’m showing in my example, I am also not getting any parts to select in my stocking warehouse.
Yep. All are stock and marked as quantity bearing.
Yes, tried to, but no records found because all of my parts–in both warehouses–have a Last CC date already. My understanding is that program will only add dates for records where the Last CC date is blank.
Is there any chance that a full physical has been started in your test environment? It doesn’t show by default on the Count Cycle maintenance grid - you need to search and select ‘Include Physical Inventory’.
I can manually add parts, but I cannot use the Paste New feature to add a list of parts more efficiently. I get errors like “invalid part” and “part required” while those statements aren’t true: I’m using a real part and I’m providing a part, respectively. You know if this is a limitation/known issue of Kinetic (assuming I’m not doing something wrong)? Nope, that was my error.
Hmm, the fact that you can manually add them pretty much rules out them being on another cycle somewhere you can’t see.
I know its the option of last resort but I think you are probably down to contacting support.
It has been a number of years since we started but I think you need to clear the count date field. The “initialize…” process already mentioned by Sue should do that.
I think the default in the system is to fill this field in when a part is created.
This process was added after I started our process as I did a SQL update to clear it.
If you are turning on the zero QOH flag maybe try it without that on and see if parts are selected.
I know when I was researching this the documentation was missing a fair amount of critical steps to get the process going. I had to compile all my testing into a word document so the next schmuck would have a chance to figure out what was going on.
The key was to break all the steps into roles so everyone knows what needs to be done or else you will spend your life babysitting this. I automated the period generation every fiscal year and last year I finally did a trace log on the cycle generation and part selection so I could build a function and make this automatic each quarter.
I don’t think I would recommend clearing the last counted date, doing so, particularly on a mass level would have it selecting a ton of parts on that first round of cycles. I suppose in theory removing it from a few select parts to force them onto the next cycle might not be as bad but in that case I would suggest adding them manually but that is just me.
This particular issue though seems like something is broken so I think support is the way to go.
Well, but that’s the point of the “initialize” process. It assigns bogus dates to the parts with no date, so that you don’t get all the parts at once.
Conversely, if you don’t clear the dates out, then you are guaranteed to get all the parts at once.
Support will provide a fix to clear the dates. I’ve had to do that several times - it’s embarrassing to say how often we restarted the cycle count program here.
Also, a few months ago we switched to just manually entering part numbers. That seems to be the more common path.
Thanks Jason. Normally clearing this date is the “nuclear option” because it will force all parts to be counted. I checked my notes from 2019 and with each Branch (site) I started the process with, I set the date to Null and then ran the initialize process to properly set the date. If there is any value in there - which part entry seemed to add on its own - then the initialize will not work.
There is no harm in putting in a ticket if there is the slightest trepidation here.
This is from my documentation from 2019. Epicor may have fixed this in the mean time.
Just got off with Support on this issue and got it to work by updating the calendar that I had on my schedule. It is a 4 day calendar with Friday as a non work day. We added Friday back onto the calendar and then it did perform the part selection process.
So, I guess you can’t use less than a 5 work-day calendar on a cycle count? …I’m going to have to play around with that some more to see if I find a way to make it work on a 4-day calendar so that my cycle count guy doesn’t have to move selected parts from the last weekly sequence into the other four sequences every week.
