Hello,

I'm just a user of WMS but one thing I noticed is that when setting up a pick location I can set the "max" and "min" cases.

Shouldn't a replenishment task be generated when you hit the "minimum" for a location? at my site this doesn't happen, instead all of the tasks are generated immediately when a new wave is released.

This causes issues as such : replen driver will have X amount of tasks, the wave calls for say 100 cases to be picked from a certain location which can hold 10 at a time, with the min cases set to 2.

Now  when the wave is released it will generate all 10 tasks right away for 10 cases to that slot.

Is there a way for it to only generate the replen task when the minimum is reached on the location?

Hopefully the above is clear

Hi Dan,

I believe they are generated as 50s (maybe the first is a 40? I do see 40s sometimes..usually priorities are 10, 30 or 50 with the occasional 40)

Does WMS have a way to configure it so that replens are generated only when we hit the location minimums? How could I do that? 

I mean, what other options are there other than "replenish to max" -- I can look at the wave templates tomorrow most likely

*edit* to clarify .. is the following possible:

given a location has a MAX value of 100 cases. The minimum is set to 10.

The wave calls for 1000 cases. We have pallets in reserve which cotain 100 cases each.

As it is now it WMS generates 10 replen tasks immeeldiately at priority 50.

Is it possible to have WMS only generate a task when the location reaches the minimum (10) but still Wave the 1000 cases?

I'm all over the place but hope you can understad.

Thanks for your help

Hi,

There's a few parameters in play here.

First, as Dan mentioned, there's the drop-down that lists Replen up to Max, Replen up to Need, and Replen up to Lesser of Need/Max. That's at the Warehouse Master level, though it's possible there's also a choice at the Wave level to override the warehouse default. 

Next, there's a parameter on the wave that says Combine Priority 40/50 Replens. As far as I know, priority 40 means "the wave needs this quantity, and it will currently fit in the location"; priority 50 means "the wave needs this quantity, but it won't yet fit in the location". If you have the combination turned on, I think they'll all come out as priority 40 replens. 

There's also a parameter that says Suppress Post-Pick Replens, on the Wave parameters. This is the one that causes the system to generate a replen when your location drops below the min quantity, as opposed to when your location drops below 0.