Zero out all inventory quantities

Yes, you can zero out an entire items database. I do this on a per location basis for our closed stores. I run the following two queries, where 'x' your store id, this is what I use for the HQ side, you would modify for SO by dropping the StoreId part. Backup your database first:

UPDATE ItemDynamic SET Quantity = 0 WHERE StoreId = x UPDATE ItemDynamic SET SnapShotQuantity = 0 WHERE StoreId = x

Regarding inactivating/deleting items, I think it is always best to inactivate to preserve historical data.

I have two notes Jocelyn,

1-This was u won't be having any history for the changes u've made, corresponding records should be inserted in InventoryTransferLog with Type=5 (manual adjustment) so that u r able to know -at anytime- the manual adjustments u've made in the past

2-for the store, the table updated will be Item, no itemDynamic table in store db, besides, i prefer to make a physical inventory instead of making up update statement that should follow an insert statement in InventoryTransferLog table

Nashat

Robert,

Even easier, maybe a better, trackable way, SO Manager | Inventory | New | All Items | Give it a name | Calculate | Commit | OK

All quantities will be 0 except items that you have committed, like layaways and work orders. All items will be shown set to 0 because of an inventory count, on Movement reports too

We also recommend inactive instead of deleting them, UNLESS, there has been NO activity for the item. If multi-store, you must delete them at each store, whereas inactive can be done from HQ.

Jeff,

I agree that zeroing out all of the inventory items via a Physical Inventory is the best option. We have had to use the zeroing out of the Item Dynamics because of the structure of our Analytical Services.

Definitely the best way to go here is with this Physical Inv option.

True, but, I would say with our closed locations back reporting against the manaual adjustments does not really matter. I also prefer the physical inv route, but, I found that when reporting against a closed location within our analytical services, the inv was still there, because they are pulling data from the wrong fields in to the cubes.

Go with the physical and zero it all out.