I am trying to see if I can understand what makes a part show up within or out of tolerance. I manually set the tolerance at the Part / Warehouse record and it triggered the part to be out of tolerance on my cycle count report. However, I changed it back to 0 and it still remains out of tolerance. It would never show up as being out of tolerance until I put a number in that Value field.
Does it only consider the tolerance settings at the time the Cycle count is initiated? Or should I be able to toggle those tolerance settings and see it update the in/out of tolerance column on the Count Variance Report?
I understand that. But it was always 0. And not showing out of tolerance. I changed it to a different value (500). I saw it recognize out of tolerance for that part. I changed it back to 0. Nothing I do now will get it to show as in tolerance.I tried a bigger number.
Percent Tolerance and Value Tolerance are copied to the CCDtl table when the cycle count is initiated. The values are probably frozen at that point and won’t update.
Do you have ABC codes assigned to all of your parts? We were missing this when we started our count. I ended up having to write an updatable BAQ to load in the ABC codes we missed into CCDtl for the variance to calculate.
I wonder if until you set and save an actual value it isn’t 0 but instead blank which in this case would be distinctly different and why it wasn’t showing up on your variance report until you actually entered a value. The help clearly states 0 means no tolerance at all.
Any tolerance we entered would not get picked up by the calculation until we had ABC codes assigned to our cycle count details. We had an awesome support rep work through this with us.
Thanks for all the pointers!
CCDtl was a big help. I didn’t realize that was storing some data there.
That table does update if I update the PartWhse record and then re-run the Count Variance report. Really interesting. It’s interesting because I can’t get the dang thing to show within tolerance no matter what I do! None of this is real world testing because I don’t expect to be changing this stuff mid-count. But in preparing for our actual count, I was hoping to try different values to see what was a good fit. I also see that the Total Frozen Qty/Value in CCDtl is 0 as well as the Total Counted Qty/Value. When I generate the Variance Report, it clearly shows counted totals/values. It must be calculating on the fly? All of this is fine - just trying to understand it all.
It does seem to take effect when you run the Cycle Count Variance report. That’s when it updates the CCDtl table… Not just re-printing the report… but actually launching it from the menu. That’s where I was going wrong. I had the report open and was making tweaks and then re-printing the report and nothing changed. That’s why. I needed to close that print screen and re-launch it from the Actions menu.
