Negatives

by

in

Periodically it is necessary to check EVO for negative items. Negatives can happen for any number of various reasons; Bugs, Duplicate items, missing receiving logs, and most commonly due to incorrect physical inventory counts. There are various ways one could check for negatives, I choose to run an sql query opposed to an report from within EVO.

SELECT
 i.id, 
 i.sku,
 concat(i.description, i.longDescription) as 'description',
 iq.qtyio, 
 iq.qtyOrd, 
 iq.qtySpOrd, 
 iq.lastSold, 
 iq.lastOrdered,
 iq.lastReceived,
 i.vendorid,
 iv.vendorSku,
 iv.vendorcost,
 i.ourPrice,
 c.catCode as 'Category',
 i.department,
 lcacs.lastCost,
 v.name as 'Vendor'
 FROM items i
 left join itemqtys iq on iq.itemid = i.id
 left join itemvendors iv on iv.vendorId = i.vendorid and i.id = iv.itemId
 left join vendors v on v.id = i.vendorId
 left join categories c on c.id = i.categoryId
 left join lastcostaveragecostsummary lcacs on lcacs.itemid = i.id
 left join itemcomponents ic on ic.itemId = i.id
 WHERE 
 c.trackinventory = '1' and iq.qtyIO < 0 and ic.id is null and i.vendorid != '1393' and i.buyer = 'Negative'

I am using i.buyer to mark items as I go through them. Currently going to use terms like “assigned”, “over sold”, “bug” in-order to better categorize and fix. It can be assumed that some of the over sold items will be missing items during physical inventory.


Comments

Leave a Reply

Your email address will not be published. Required fields are marked *