Hi all,

Anybody come across the problem where the pick release process is still creating move order lines when your sales order export (customised or otherwise) is exporting the delivery lines to the WMS?

The issue then of course is that the shipment confirmation from the warehouse will not contain all of the delivery lines so ship-confirm will fail (although of course you can manually transact the move order and then ship-confirm the delivery).

The easiest and quickest solution to this is to place all of your warehouse pick-release rules into a request set, with the last stage of the set then being the export process. Of course this means that you need one request set per warehouse but then if you have one or several pick-release rules per warehouse and a scheduled export anyway for all warehouses there really shouldn’t be a problem with this.

This is preferable I think to having some form of check on what has been exported or selected for export versus what is against the delivery as the pick-release may still be running - and how long do you want to wait in order to ensure that the export data set contains all the move order lines?

I know of course that the pick-release process should be incompatible with the export process, but for installations of multiple warehouses this could have severe performance issues. In any case, you should ensure that the new request set is incompatible with itself, just in case it is submitted manually.

Anybody got any thoughts on that or a better solution? We have several dozen pick-release rules across multiple warehouses and existing performance considerations

Regards, Mark.