Forecast consumption occurs when forecasted quantities are reduced by a reduction key or by actual orders during forecast scheduling. Forecast consumption results in smaller forecasted quantities being transferred to master scheduling to calculate net requirements.
Example 1
This example illustrates how a reduction key consumes sales forecast requirements. You must link the reduction key to the item's coverage group and select in the drop-down list in the form. Set up the form with the following lines:
Change |
Unit |
Percent |
---|---|---|
1 |
Month |
100 |
2 |
Month |
75 |
3 |
Month |
50 |
4 |
Month |
25 |
Create a sales forecast of 1000 pieces per month. If you run forecast scheduling on January 1, the sales forecast requirements are consumed according to the percentages that are specified above, and the following requirement quantities are transferred to the master plan:
Month |
Number of pieces required |
---|---|
January |
0 |
February |
250 |
March |
500 |
April |
750 |
May - December |
1000 |
Example 2
This example illustrates how actual orders consume sales forecast requirements. Select in the drop-down list in the form. The following sales orders exist on January 1:
Month |
Number of pieces ordered |
---|---|
January |
956 |
February |
1176 |
March |
451 |
April |
119 |
Using the same sales forecast of 1000 pieces per month, the following requirement quantities are transferred to the master plan:
Month |
Number of pieces required |
---|---|
January |
44 |
February |
0 |
March |
549 |
April |
881 |
May - December |
1000 |