Sage 100

Trying to import a physical count in v2014 PU7 where the items are lot valuation. Customer needs to zero the items out due to a change in standard u/m. I did one the other day for the same customer with the lot numbers included in the import but it said the quantity on hand for each lot was the total quantity on hand, not the lot quantity. After manually correcting them the other day, I tried adding the ChangeQuantity to be the existing qty on hand but it did the same thing. Found a KB article saying to delete the perform logic and now there is NO qty on hand for the variance. What am I missing???

We have an open case with Sage on this same issue with version 2016. When doing an import it assigns the Qty on Hand to every single Lot Number making a real mess. Sage finally admitted this was a huge problem and was able to recreate it last Thursday. They sent it to engineering but we have not heard back. Now I'm not sure how many versions have this issue. This could be a really big problem at year end with anyone importing a physical count with either lot or serial tracked items.

KB article says they added the perform logic in 2013 and 2014 and that they are currently reviewing the situation. It created negative quantities on hand for many lot numbers. I had to go in and manually add them in Physical Count Entry as zero. What a PITA! https://support.na.sage.com/selfservice/viewdocument.do?noCount=true&externalId=45154&sliceId=1&cmd=displayKC&dialogID=46056&docType=kc&isLoadPublishedVer=&stateId=46061&docTypeID=DT_Article&ViewedDocsListHelper=com.kanisa.apps.common.BaseViewedDocsListHelperImpl

I encountered a similar issue last month with lot numbers (v2016 as well). My problem was that I was importing all items (many with zero values) into physical inventory. Big, Big mess. When I cleaned up the import to only include lines with values, all was good.

Won't freezing the items set the counted quantity to zero automatically?

There's no easy way to freeze them individually. It's by vendor but not all items for a particular vendor.

comma separated list...?

Meaning??

Wow, I'll have to remember that but you can't freeze when users are in the system so no such luck today.

One thing I have done in the past is to populate the inventory cycle with a value or create a UDF in CI_item Then use the selection criteria in physical inventory to select those items. If you have many items like this, dump into Excel, edit it, then do a VI import into CI_Item.

Excellent tip @KevinMoyes - posted it to Evernote

That comma separated list method should work in all selection grids and there is a character limit (a quick test shows it is 1500, max).

The CSL works great in the grids. Just make sure you don't leave a space after the comma.

To freeze inventory items in Physical Count without getting users out of the system: Write a VI Import to IM_Physical. Add the Warehouse Code, Item Number and as the Counted Quantity, set it to a blank column in your spreadsheet. That will ""FREEZE"" just the items in your list. It actually puts in a Count Quantity of zero; so be sure someone does not Update the Register by accident. Then later, come back and update the spreadsheet with counts and set the Counted Quantity Column to your count column. Not sure if this will work with Lot/Serial Valuation, but it works well with Fifo, Lifo, Ave & Standard Cost Items.

If Providex, copy the company, freeze in the copy company code, then copy the frozen IM_Physical.M4T back to the live folder. If Premium, same concept except you use a SQL select into statement to copy the IM_Physical data back to the live company code table.

Lot numbers are what causes the problem @MadelineStefanou and yes, I could copy to a backup company @KevinMoyes . May do that next time as we are working on a project for this company that is requiring multiple phys. counts. Thanks all!

Have you tried importing into a count card?

No but do you think that would be different??

It's a different business object, so if that's where the bug is... things might work with a different _bus.

Will check it out with the next batch - thanks for the thought!