Select a method to use to reduce forecast requirements during master scheduling. If you choose None: Forecast requirements ...

Select a method to use to reduce forecast requirements during master scheduling. If you choose None: Forecast requirements are not reduced during master scheduling. If you choose Percent - reduction key: Forecast requirements are reduced according to the percentages and time periods that are defined by the reduction key. If you choose Transactions - reduction key: Forecast requirements are reduced by the transactions that occur during the time periods that are defined by the reduction key. If you choose Transactions - dynamic period: Forecast requirements are reduced by the actual order transactions that occur during the dynamic period – the dynamic period covers the current forecast dates and ends with the start of the next forecast. The Transactions - dynamic period method does not use or require a reduction key and when you select this option: If the forecast is reduced completely, the forecast requirements for the current forecast become 0 (zero); If there is no future forecast, forecast requirements from the last forecast that was entered are reduced; Time fences are included in the forecast reduction calculation; Positive days are included in the forecast reduction calculation; If actual order transactions are greater than the forecasted requirements, the remaining transactions are not forwarded to the next forecast period.
English
English (United States)
日本語
Japanese