I am hoping that there is someone out there that can assit me with this query.

We are implementing Cycle Count with Automatic Scheduling using the ABC Compile Criterion Historical Usage Value. When checking the ABC Descending Value Report, it was noted that the compiled qauntity column does reflect actual usage of the item.

Our understanding of usage are issues (Move Order Issues) that were carried out on the item. For example:
Item X
Current QOH: 100
Total Issues: 20

Therefore, usage for that item is 20. However, based on our analysis, the ABC Compile Criterion Historical Usage Value interprets usage for this item as 120 and not 20.

Hence, my question is how does this compile criterion works? Isn't an items's usage exactly what it is, that is, what was used/issued, that is Move Order Issue, what is issued out of the sub-inventory/inventory?

We were implementing Cycle Count with Automatic Scheduling using the ABC Compile Criterion Historical Usage Value. When checking the ABC Descending Value Report, it was noted that the compile quantity column does not calculate the actual usage.

That is, our understanding of usage, is that when an item is used/issue (Move Order Issue) out it is 'usage'

Therefore, the quantity used is 20. However, based on Analysis of the ABC Descending Value Report with the ABC Compile Criterion: Historical Usage Value it was found that Oracle usage for this item is 120.