We are running into an issue with replenishment when we have the “Allow wave demand to use unreserved quantities” flag set to “Yes” for items with multiple fixed locations in the same warehouse. My client uses wave demand replenishment to replenish pick locations on the fly. They cannot use slotting or min/max replenishment due to only one tote location open on the line and no staging area for the product. When we run a wave where the location directive is set to pick from a specific pick location, it will create replenishment work for that location for the items that will need to be replenished as part of the pick wave. We have a replenish unit/quantity that is likely higher than the total wave quantity for that SKU, which leaves an opportunity to reserve against open replenishment work instead of creating duplicate replenishment work and bringing too much product to that location.
If we then ran a wave where the location directive is set to pick from a different pick location for that same item and the replenishment work going to the original location has not been closed out yet, it will try to direct to pick from the original pick location due to open replenishment work for that SKU having a replenishment put location of the original location. This is NOT the result we want. We would want to always pick from the pick location specified on the related order and matching location directive. However, once this toggle is set on the location directive, it looks for any open replenishment work for that item regardless of associated location directives. There appears to be an open Microsoft Idea that hasn't been added to the development backlog: Microsoft Idea (dynamics.com)
Does anyone have any ideas on how we could work around this issue?
Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.
3
Share
Report
All responses (
Answers (
