We had a similar problem when we first started using Vantage. Because partwhse.counteddate was empty for every part, every part was due to be counted, so cycle counting started doling them out (alphabetically, maybe, I can't remember for sure) without regard to their ABC values. I force-filled the counteddate field and after that, the parts it picked started making a lot more sense.

I created a quick ODBC report that contains partplant.partnum, partplant.systemabc, partwhse.warehousecode, partwhse.counteddate and a calculated formula to show when the next count date should be. Filter out inactive and non quantity-bearing parts. It should be easy enough to do as a BAQ as well.

None of this helps with the zero quantity issue, however, since they don't actually get counted if you exclude them so the counteddate isn't updated. We ended up having to "count" the zeros. If anybody came up with a better answer, I'd love to hear it too.

HTH

I created a quick ODBC report that contains partplant.partnum, partplant.systemabc, partwhse.warehousecode, partwhse.counteddate and a calculated formula to show when the next count date should be. Filter out inactive and non quantity-bearing parts. It should be easy enough to do as a BAQ as well.

None of this helps with the zero quantity issue, however, since they don't actually get counted if you exclude them so the counteddate isn't updated. We ended up having to "count" the zeros. If anybody came up with a better answer, I'd love to hear it too.

HTH

--- In vantage@yahoogroups.com, "m_sprowles" <msprowles@...> wrote:

>

> We have only been on Vantage for a short while and we are just beginning to cycle count. I have a couple questions, (below), if anyone can help me...Thx!

>

>

>

> The first thing I had to do was to let the system calculate the ABC's Â– for our beta version p first attempt, I set the following thresholds:

>

>

>

> A Â– parts with a unit value of greater than $1000 Â– counted every 60 days

>

> B Â– parts with a unit value of greater than $250 Â– counted every 180 days

>

> C Â– parts with a unit value of greater than $10 Â– counted every 365 days

>

> Z Â– parts with a unit value of greater than $0.01 Â– counted every 730 days

>

>

>

> The 2nd step is to set up the count group and indicate the maximum number of parts for this group Â– and for this week I have chosen 150 parts Â– and then ask the system to pick the parts Â–

>

>

>

> Observations Â–

>

>

>

> The system starts at the beginning and gives you the first 150 parts to count, regardless if there are any on hand.

>

>

>

> I cannot determine any regard to selection of parts based on ABC Â– my first 150 could be all C's Â– not sure.

>

>

>

> I started the first count with 150 parts Â– and I asked it to omit zero on hands Â– and when I set up the tags, I requested 10 blank tags Â– When I print previewed the tags Â– all I had was the blanks; therefore, in the first 150 parts requested for cycle counting Â– NONE Â– were on hand.

>

>

>

> Do you think that I will need to just replicate this until I actually hit something to count?

>

>

>

> Normally, I could run the variance report "with Notes" and I will get a printout of all parts counted Â– but I do not think I would get this if I ask the system to omit zero qty's Â– so HOW do I prove that I have counted these parts Â– to meet our frequency requirements?

>