to have a count option of Jobs (JobId) and Orders (OrderId) to be able to set on the customer what we want to show. Screens that show jobs (e.g. open to induct jobs, in progress jobs,...)
Problem/opportunity trying to be solved
UniPharma is a customer that is batching orders with their WMS for singles. With a result that we from them get 1 JobId wil multiple OrderIds. If we currently look at LocusView to the open to pick (jobs and lines), it was by default count a count on JobId. But because of the batching for them OrderId is more important/relevant compared to JobId. |
|
Quantify the problem/opportunity
There is the option to count on either Jobs or Orders in LV - Picking.RemainingMajorUnitsToDisplay from JOBS to ORDERS. We were in LV able to update jobs to orders providing the required visibility for the customer. |
|
What is the root cause of the problem/opportunity
Customer is doing the batching of singles in their own WMS. If they would allow us to do the batching of singles, the number of JobIds and OrderIds before the actual batching would be the same number. We are still discussing this with their WMS consultants, but it will not be an easy change. |
|
Customer need date | Dec 31, 2024 |
Urgent request | No |
Report Tag | CSM, Data |