The system uses forecast data in Replenishment Planning at two points. To be able to use both points, you need to set the forecast indicator for the RP type to obligatory or optional forecast.

• In replenishment planning, you can consider forecasted sales as expected issues. In doing so, sales are considered from the time of planning until the end of the replenishment lead time.

• If you work with dynamic target stock, the system recalculates the target stock in replenishment planning based on forecasted sales data. In this example, sales are calculated based on the end of the replenishment lead time for the duration of the target range of coverage.

A number of models are available for running a sales forecast (for example, trend models or constant models).

Planning methods for multi-step replenishment that use a forecast, only use the sales forecast. Note that you can only use multi-step replenishment for stores.

You maintain the forecast parameters in the article master. You can also select the periods in which the forecast values should be updated, for example, each day, week or month.

You can start the sales forecast using transaction WFCS01. The sales forecast has numerous selection options to enable you to set up target-oriented forecasts.

In contrast to the forecast in MRP, the sales forecast uses its own data basis for movement data (POS history + sales forecast values). In order to achieve an optimal distribution of computer capacity and the best possible performance, you can use parallel processing of stores when carrying out the sales forecast.

You can display mainly technical information about the activities performed during the sales forecast run in a log.

You can display the results of the sales forecast using transaction WFCS03. The movement data and the master data for the individual articles/plants are in the foreground.

During the course of the sales forecast, lots of data, especially movement data is created. In order to keep the size of the database table down to a minimum and thus maintain the performance of the system, you should regularly delete obsolete logs from the sales forecast using transaction WFCSL02. You should also delete movement data for the sales forecast that is no longer valid at regular intervals using transaction WFCS02.

If you plan to replace the standard forecast or MRP with the sales forecast, you can carry out a legacy data transfer from table MVER to table WFCS_WRFT using transaction WFCS04.

Maintain the Forecast consumption indicator in Customizing for Planning Characteristics whilst transferring legacy data.