I searched before posting this, and I just have to say, I saw my own picture entirely too much in the results. So this is not making me terribly optimistic… Anyway, here is what I am being asked to do (or guide).
Let’s say we need to count 1,200 parts in October
And let’s say there are 20 counting days that month (thus 60 parts per day)
Management wants to put no more than 10 part numbers on a count
So I need 6 counts per counting day (10 part numbers each)
Also, this is a single warehouse
How would you do this?
I am pretty sure the only way is to have six “periods” for the month of October, all overlapping identically.
Because if I try to use the same period in the same warehouse on two schedules, I get this:
Well, I mean, I suppose I could really hack it and create a period that is 6x as long and then reassign all the dates of the counts…
What happens is that if you put 60 (or even 20) parts on a single count, invariably 2 or 5 of them will have “issues” that require investigation.
Then they decide to not post any of the count until everything is reconciled, which is maddening because as the hours and days go on, you are really struggling to hit that moving target of, “Was that pallet there this morning?”
Now, you can, in fact, post part of a count. Just make sure some of the tags are not returned (electronically) and that should sufficiently torpedo that part number. I know this from not wanting that.
Regardless, I sympathize with the idea of smaller chunks. I feel the pain.
Does it have to be a real cycle count?
I created a customization that finds the top x parts that need to be counted on any given day (logic is based on ABC code and how long since its been counted) and then emails a baq report to the warehouse manager. It works by modifying the last cycle count date once the part is selected for count (so assumes they actually do count it that week).
They don’t need the tags though, they just work off the report (excel spreadsheet) and then do quantity adjustments if needed.
It could work for your scenario if you don’t have to do a real cycle count, because you could use a baq to identify the parts and then put them into groups of 10, and break your report on those groups.
I think I outlined that in the following paragraph, no?
Even if it is possible to post partial counts, it’s just a lot more manageable to have smaller ones. I’m actually agreeing with management on this one.
Are you open to writing a little code that generates the cycle count records you want? You could use DMT to run them to create the cycle counts that the system will not let you create/process the way you want.
I’ve not played with it in this way, but from the template generator in DMT, it seems it allows for a CycleSeq value.
I agree with Mike. You don’t have to use the Kinetic Cycle Selection process. At a previous gig, we managed the parts selected and pasted them into the cycle. This facility hasn’t done a physical in ten years passing every single audit.
I read the same day thin in the schema and did some testing with the part selection criteria. You can make the same warehouse and dates for multiple schedules. You would have to precalculate like with the DMT to put 5/6ths of the parts on hold and check exclude on hold for each pass , but that is the once a year setup.
DMT would be a quicker and more defined process, but what they want is doable.
It’s the Count Tag DMT, where the assumption was that you created the cycles prior to the DMT. But since you found where to activate the CycleSeq field I pointed out then you’ve got it covered!
