Locus Robotics Ideas Portal
What they confirm is that we have build in the totevalidation (scan of handling unit) as part of the barcode verification interface. SAP is saving the first and the last barcode. And because the last barcode now is the handling unit, the parsing out is not being done anymore and the 2nd barcode that contains the batch and the sequence number is not saved anymore.
Customer would like for us to not include the handling unit verification in the barcode string that SAP receives from us.
|
Problem/opportunity trying to be solved
Since the use of ProGlove for the totevalidation scan, Abbott is seeing differences in how information is stored in SAP. The Handling Unit (toteid) is saved as additional barcode since using ProGlove. Because of the additional scan, the parsing out is not happening correctly anymore. The full parsing out is not happening correctly cindlugin Segment 91 (seq number).
Single barcode: Double barcode: Before ProGlove After ProGlove: That means with the double barcode it is no longer traceable with seq number has been scanned and therewith traceability is completely gone. |
|
|
Quantify the problem/opportunity
They have lost traceability of the seq number and therewith traceability of a unique item is completely gone. This is important to get resolved for the customer |
|
|
What is the root cause of the problem/opportunity
Abbott Heerlen started to use ProGlove to do the totevalidation scan. They had issues with correctly picked items but put in the wrong tote. With the totevalidation scan with ProGlove we have significantly improved the error rate. And even though the process works well, we need to restore that visibility. |
|
| Customer need date | Nov 1, 2025 |
| Urgent request | Yes |
| Report Tag | CSM, Deployment |
I had a call with Taylor on this and he believes there is something we can do, but he believe that needs to be managed as a new functionality. He was still further analyzing this, but proposed to already get this AHA request in.