I'd like to know if this is the standard SAP function of cycle counting logic and if it is, I'd like to know the solution for this within standard as possible.
We implement cycle counting project but one big issue happened.
Let's say we have a "A" class material which requires cycle counting today so I did it... create doc, count, and post the differences.
Now I expect the bin's next cycle counting will be one month later because we set 12 counts per year for A class material.
But since it's fast moving material, it's delivered to customer today.
And since the bin is empty it's replenished from other location.
As a result, since the quant has been changed, the system proposed new cycle counting tomorrow...
It's same material number with same bin I counted today, needs to be counted tomorrow?
I'm talking about 5000 bins every day.
Is there a way to skip this kind of case?
If any company using Cycle counting in WM, how do you use it?
Thank you.
We implement cycle counting project but one big issue happened.
Let's say we have a "A" class material which requires cycle counting today so I did it... create doc, count, and post the differences.
Now I expect the bin's next cycle counting will be one month later because we set 12 counts per year for A class material.
But since it's fast moving material, it's delivered to customer today.
And since the bin is empty it's replenished from other location.
As a result, since the quant has been changed, the system proposed new cycle counting tomorrow...
It's same material number with same bin I counted today, needs to be counted tomorrow?
I'm talking about 5000 bins every day.
Is there a way to skip this kind of case?
If any company using Cycle counting in WM, how do you use it?
Thank you.