Hi all,
We have an issue where once a delivery has been released for pick, if a user subsequently adds additional lines and allocates them, M3 is automatically creating a new (suffixed) pick list for just those lines, setting the CO line status to 44, which results in those few lines printing a pick list.
If another user then goes and adds some more lines and allocates them, M3 is again automatically putting those lines on a new (suffixed) pick list and sending the pick list to status 44, and printing it.
Due to the nature of our business, this can result in 25+ pick lists with only a few lines on pick lists 2 - 25.
What we need is to be able to release an order for pick, then add additional lines and have these stay at status 33.
Then we need to effectively 'release' this order again, so that a suffixed pick list is then created with any lines that have been added since the initial release for pick.
We need to manually control the generation of the suffixed pick lists, so that we can wait for more lines to have been added before subsequent pick lists are created.
It seems like once a delivery has been released for pick the first time, any further allocations are automatically placed on a new pick list and printed.
Our dispatch policy in this instance looks like this:
Does anyone know how we can control the flow of pick lists in this instance?
Cheers,
Iain
