The Demand Plan server has Moving Average Period defaulted to 6, but when checking individual parts in the Demand Plan client, the effective Moving Average Period shows as 1 instead, and the resulting system forecast is 0 across the board — what's actually driving the forecast in this situation?

All FAQ questions / Supply chain

Answer

The moving average forecasting model always produces a flat-line forecast (unless a seasonal profile is layered on top), calculated as the plain average of demand from the N most recent historical periods, where N is whatever the effective Moving Average Period value is for that part — not necessarily the site/server-level default you configured. If the effective per-part value is 1 rather than your intended 6, the model is just using the single most recent period's demand as the entire forecast, and if that single most recent period happens to have no recorded demand, the flat-line forecast comes out as zero. Worth explicitly checking (and correcting, if needed) the actual effective Moving Average Period value being used at the part level, since it can differ from whatever default you set server-wide.

Documentation-based answer. Confirm the product and release before applying it. This answer has not been verified in an IFS environment.

← Browse Supply chain questions