Except for anything in the casepack locations, or any time the upc didn't update to the new dpcis.Somewhat off topic, but the Item Merge is a complete waste.
The ability is there for item conversions. They are used frequently for most departments. All in all they are basically the same thing. A becomes B. Only for the Merge you have to LOCU to get the old UPC/DPCI off location and add the newly associated DPCI with the same UPC on location. Conversions do it automatically.
Except for anything in the casepack locations, or any time the upc didn't update to the new dpcis.
Every bakery dept change I've had this issue. It's like we can't even pretend to care.And that people don't actually do the damn merge report and don't re-sto the product properly. I have found so much crap that should have been completed and the reports said they were worked. But nope they just re-sto'd it with the old DCPI. And no one pulled the old pick labels.
And that people don't actually do the damn merge report and don't re-sto the product properly. I have found so much crap that should have been completed and the reports said they were worked. But nope they just re-sto'd it with the old DCPI. And no one pulled the old pick labels.
Items are stored into the SLS via dpci, not UPC. The logic does not have the capability to delete and resto a given product when a dpci changes, hence the reason for the item merge. It would be costly to fix this.Hence why there should just be a conversion. Both the DPCI and UPC are re-associated with the new DPCI.
How do the audits tie into BRLA? I had thought the audit fixes errors, but it looks like it fixes errors and then counts against your BRLA.
I'd look at BRLA TM and demote the high bafflers to flow until the truck is done, then have them come to the back. See if their location accuracy improves.
My STL's fix idea was to scan an item in STO after you pulled it anytime it asked you to pull less than the quantity in the location. This way you could backstock anything that was a baffle into the location. I actually do that before I pull it, then pull 1 more than it asks for if the quantity is lower than actual. This way it will ask me if I pulled all, I say no, then it will let me know if it wants more or not. This however will not fix accuracy, but idgaf. My job is to identify the morons.
I've gotten super fast with it using toggle and the left arrow for return. If I toggle over to STO and there are 6 in the location, but it asked for 4, I will hit return, toggle back to pull, and pull 4. If it says there are 4, but there are actually 6, I will pull 5, it will ask if I pulled them all, I will say no, then it will tell me if it wants more or not. Now the baffle has been created, but it will be fixed in the audit.So with your method you're creating the baffle so you can track who did it? Plus that seems like a lot of time to go into sto for everything when pulling cafs.
Also I feel like this assumes that every correct CAF pull will always ask for all of a specific item from a location..
I've gotten super fast with it using toggle and the left arrow for return. If I toggle over to STO and there are 6 in the location, but it asked for 4, I will hit return, toggle back to pull, and pull 4. If it says there are 4, but there are actually 6, I will pull 5, it will ask if I pulled them all, I will say no, then it will tell me if it wants more or not. Now the baffle has been created, but it will be fixed in the audit.