Automatic discrepancies

Automatic discrepancy cycle counts are triggered based on events that occur during normal business transactions. You are asked to verify the quantity in a location. For example, if you pick a location to zero on the RF unit, you are asked to verify that the location is empty. If the location is empty, you click Yes. Then the quantity should be equal to the quantity TWL expected. Thus, there is no quantity discrepancy. If you click No, then a discrepancy is created because the quantity is not what TWL expected.

When you are at the location and the quantity counted is zero, the impact to productivity is minimal and the planned cycle count is eliminated. An activity is also scheduled to replenish the location, if the location is a primary pick location, to its maximum quantity. The disadvantage is that only medium and fast-moving parts are counted regularly. Slow-moving parts rarely reach the automatic discrepancy quantity.

Cycle counts are also triggered when a TWL warehouse is the shipping warehouse and an exception is processed in Transfer Exception Receipt Entry. The shipping warehouse is responsible for resolving warehouse transfer exceptions because the receiving warehouse verifies the error. A Transfer Exception Receipt Entry cycle count wave is created for the location in question, and you must verify that the location does not contain any inventory.

When a transfer exception triggers a count, TWL assigns a cycle-count wave number to the inventory record. You can access the number and begin looking for the discrepancy. You can also view the transfer exception wave number on the TWL Cycle Count Accuracy report.