Something does seem to be going on with the stowing. I was backstocking some stuff the other day and I found a couple of eaches of a product I had already stowed, but when I scanned it, it said there were none located.
I had just located it a few minutes prior so I KNEW I didn't forget to scan it in or anything. So I went and checked everything else I had stowed and found one other DPCI that acted like it hadn't been scanned in. So that was 2 DPCIs out of probably 25 that I stowed that just didn't take for whatever reason.
Also, maybe related, maybe not.. I've noticed that when I stow something, it will show a ridiculous "in back" count. Like, before I stow, there will be 0 in back, I'll stow 5 and it will say 256 in back. But if I scan the item again, it correctly shows 5. So it seems to just be a display error after stowing, but it's still troubling, especially given the other issue with items seemingly coming unlocated for no reason.
Another weird thing, I was running a SFS batch and checked an item in MyWork, it said we had -4 in the back. In a location for something that I had previously backstocked. In this case, no matter how many times I refreshed, it still had that negative number. So I had another TM enter the DPCI and it showed 0 in back on theirs. Then when i refreshed mine, it was no longer showing the -4.
So yeah, something very weird is going on with MyWork and the backroom. Which is kind of scary because that points to some sort of corruption/data integrity issue and that can get really nasty really quickly.