Q - This has happened mysteriously a few times over the past few months. Someone will go to print a pick ticket, and the system responds with a "nothing in range" message. When that user tries again with a different number, the same thing happens. Then someone runs a B/O report and orders show that pick tickets were printed, but they were not.
They find that the orders are marked with today's date in Order-Date-Picked, but no one printed the orders. They do not typically print "All" -- each customer service rep enters an order then prints his/her order. Sometimes they will enter a few and print a small batch, but not usually.
You see from the image below an example of a back order that printed today, yet no one actually changed the Qty To Ship, so they wouldn't have printed the B/O.
What possible program could have printed - or at least set the Picked date - to cause this problem? Needless to say, this is how their back orders would slip through the cracks.
A - In addition to a pick ticket program that will update "Order Date Picked" field, the following are two other possible reasons why this field might have updated:
- If the user prints a packing list before printing a pick ticket, then the order date picked value will be updated.
- If the user prints a legacy bill of lading, it can optionally update the order date picked value per Global Setup -> Cop-Ctl -> Legacy Bill of Lading, field "6. Update Order Picking Date After Printing."
If you want to find out when and who performed a function that resulted in an updating of the Order Date Picked field, you can implement Audit Master to track it down.