Hi Ho, Hi Ho its Monthly Inventory time to go!!! And we have a part that on 11/29 the last entry showed a quantity of 28,741,365.00. Yet on 11/30 at 8:29 AM we have a whopping total of 28,804,365. And we had nothing added to this, in fact all we had all day was subtraction.
So, first, I think internally we need to reassess how and when we do inventory. But for the Epicor Question, why would it be off by so much? I did a part refresh on Monday so it should be good. Thoughts.
My accounting lady takes an Inventory snapshot then everyone counts their stuff and then puts the numbers into the system. After that time she runs the Detail Count Variance Report to show any differences. While I am newer to Epicor, it appears these are Epicor reports and uses, not customized.
So my snap shot at 4pm on 11/29 is 28,804,365 but my part transaction history is 28,741,365. About 80K off. I’m assuming Part Trans can be a little off at times, but is this much variance normal.
Will,
The snapshot amount will equal the amount that was on hand in THAT warehouse at the TIME the count was initialized.
Epicor then keeps track of the transactions that occur during the count and are accounted for before the adjustment is made. The Count Tag Entry also records the time that the count was entered and the adjustment will be applied at that point in time. If you are NOT using handhelds for live count entry and transactions occur during the count then you run the risk of a transaction occurring between the count and the entry of that count.
While I cannot see the full history for 11/29 in your screen shot, I would assume that at the time the count was started the inventory in the warehouse (not all warehouses, make sure your Transaction history is only looking at the warehouse being counted) was 28,804,365, but I can’t see if there are other transactions that day, nor do you have the transaction time in your screenshot (might need to do a BAQ on PartTran to get that. (there is a SysTime and a TranTime, you might want to look at both).
It is also possible for some transactions to be back dated which can cause issues like this, rare but it’s possible.