Hello Community,
we are facing some issues with the FEFO batch reservation combined with the Batch Above reservation hierarchy.
We have configured the batch-tracked items in our system with the following features:
- Item model group with the flag FEFO date-controlled enabled
- Reservation hierarchy /BatchAbove/, with the batch above location
With the previous configuration, we are facing two main issues:
1) The system is reserving batches in the inbound location (still not put-away yet) and for this reason we are having many Replenishment work with blank picking location
2) When a worker performs a short pick, both using automatic or manual reallocation, the system is not able to propose a new location with the same item but a different batch
We were trying to find an alternative solution to fix these issues. We have created a new Reservation hierarchy /BatchBelow/, which has the batch dimension under the Location.
Thanks to this reservation hierarchy, we should be able to solve both the issues, but we are losing the FEFO logic: the system is indeed allocating locations where we have a batch that expires after then another stored in a different location.
We have tried to use the location directive action strategies /FEFO batch reservation/ or /Round up to the full LP and FEFO batch/ but it still seems to allocate a non-FEFO batch.
Do you have any suggestion on how to get around these issues?
Are we correctly using the setups?
Thanks and Regards,
Simone
Stay up to date on forum activity by subscribing. You can also customize your in-app and email Notification settings across all subscriptions.
André Arnaud de Cal... 291,253 Super User 2024 Season 2
Martin Dráb 230,188 Most Valuable Professional
nmaenpaa 101,156