Hi,
In our distribution company we have a business scenario where the manufacturer decides which batch code must be delivered to customers. Therefore batch code is already fixed in the Sales orders and Deliveries.
At WM level we have 2 areas: pallets area and picking area for the picking of cases.
When running standard deliveries replenishment (transaction LP22), the batch is just ignored, and the Transfer Requirement is created without batch information. Depending on other settings (SLED management, etc...), when the replenishment TO is created, any batch can be picked and moved into the picking area.
When picking the delivery, it will retrieve the stock from the fixed batch, but this stock might well not have been moved into the picking area for the reasons above, thus not being the picking optimized.
In the past we've gone through a full enhancement of LP22 via user-exits to consider batches, but it is difficult (batch code must be considered when obtaining deliveries requirements, stock available, previous TR's, etc...) and prone to errors.
Could you please advise if there is any standard or clean/easy solution to have LP22 to consider only the batches fixed in the deliveries, or to replenish picking area only with the batches in the deliveries?
Thanks in advance
Félix
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.