We have a 0 days before and a 180 days after forecast window and for a given part, we have 3 forecast entries. One for January, February, and March.
The forecast entries are not customer specific.
After loading related sales orders and running MRP, the forecast consumption is exactly what is expected.
If I then ship one of the releases, that previously consumed the forecast, for a quantity of 25 and then rerun MRP , I am seeing that the forecast consumed quantity is reduced by 25.
The expectation is that even though the release is now shipped and closed it still falls in the forecast window and should consume the forecast so that MRP is not drive unneeded supply for the quantity of 25, which it is.
I’m gone through several scenarios and tests and I’m not sure if my understanding of forecast consumption is correct or if only open releases that fall in the window will consume the forecast.
We are seeing the same thing, and my expectation is the same as yours. If the order that consumed the forecast is shipped, the forecast should still show as consumed.
I am not sure if this is a new glitch, or if it is something we are doing differently.
At the first of every month, we would normally remove all forecast, consumed or not, for the current month. Our lead times are such that customers should not be ordering within 30 days.
We have recently had a change in who is loading forecast, so those current month forecasts are not getting removed as had been the case in the past.
That being said, it seems the logic should be to not allow previously consumed forecast to reappear after a consuming order is shipped.
I’m a little late to the party here.
I’ve had problems with overlapping forecasts. Never clear which forecast bucket it would take from. I settled with 0 days before and 91 days after. I set my buckets 1/1, 4/1, 7/1,10/1.This mirrors out Customer buying habits.
on 4/1 the forecast for 1/1 drops off time phase .
I’m actually working through an issue now of which date on the forecast consumes which bucket, OrderRel_ReqDate aka Ship by and OrderRel_NeedByDate aka Need By.
If a customer ‘Needs’ product by 4/3 but Sales sees that we have it in hand and Sales Dept enters Ship By 3/22, forecast for 1/1 is consumed. arrgggg . have to catch it and massage the forecast.
Hi, I know this is on a delay, but we just upgraded to 2024.1 from 10.2 and are noticing the same issue. Did you ever manage to get to the bottom of this?
Yes - this issue of previously consumed forecast reappearing was resolved with an update from Epicor. I don’t remember which patch it was, but we are currently at 2024.1.24 and this is no longer happening.