Search results for query: *

Are you becoming a key carrier for it? If so it will probably involve lots of door opening and dealing with the alarm panel. If there are any third party contractors you will also have to deal with them too. The presentation TL will probably(hopefully) also be going overnight and should be...

The Y/N will prompt if you are entering more than the system thinks is in location, as far as doing this in the CAF pulls is concerned I am not really sure if this causes an error on the report I have not tested it. However doing this is SUBT will not causes errors, this is because errors are...

The system recognizes errors during the pull process, every time you are in a batch doing a pull it is double checking to make sure that everything that you scan in the location is located in the system. If you are pulling from a location and scan something that was not located in that location...

Errors on the BRLA TM report under LOCU can be from the audit only if the person doing the audit missed an item in a location they scanned during the audit (this is because the audit is pretty much the same function as LOCU). So, any errors on the BRLA TM report under LOCU would only be from...

The BRLA TM report only shows errors made by M-deleting wrong, using Y/N wrong, and using LOCU wrong. Unfortunately, it cannot determine who is responsible for an error caused by counting incorrectly because it could have been the person who backstocked it or the person who pulled it(or the...

Just to clarify I don't recommend using LOCU instead of M-delete it is cheating, it can also get you in trouble if any of the district/group people dig into your numbers.

It would be more productive to fix this when you come across it, besides creating baffle errors the items you scanned will just come up in the next pull and could possibly be missed by a less experienced team member creating an additional M-delete error. Also, your team leader will now have an...

I would not really recommend this method. It can be useful to check items in STO to see if they are located; for example after you pull 6 of an item and there is 1 left in location check in STO to see if that one is still located, if it is not located I would just throw it on the pull. Also...

You could also cheat the system and have your team LOCU instead of using M-delete, that is if your a fan of doing extra work just to make a score green.

one team member doing someone thing wrong can DESTROY location accuracy. The best thing you can do for location accuracy is educate the team, they need to understand exactly how errors are calculated and what causes them. Also, the team member location accuracy report does not cover...