The first step in using an uploaded user defined forecast is to enable the Forecast Source option to use the option Requirement Plan Override as opposed to the Statistical Value or Approved Demand Plan (when the S&OP add-on is enabled). If changed in system settings the default for all items will be a user defined forecast.

The options to set the Forecast Source are:

• System Settings
• Multi-Edit Settings
• Item Planning Details Options Tab

Selecting "Requirement Plan Override" will default all items to use an uploaded user defined forecast in the requirement plan as their forecast source.

This option may be enabled in system settings if a group of items are using an uploaded forecast to drive demand. In this case select a number of items and click edit in the selection interface.

This is most applicable in situations where customers share their forecasts with their suppliers via VMI or other data sharing platform.

This option is available in the Option tab of the item planning detail view. You may also enable the UD forecast option in the options tab of an item after the upload without having to rerun a requirement plan.

There are two types of monthly upload files. One version is for DRP (mulit-location) and a second version is when there is no DRP module enabled (single location).

Create a spreadsheet with the following information. Leave the column headers in the file so DemandCaster will know what date buckets to apply the forecast against. The two formats are shown in the image below.

The table columns are as follows:

• A - Item Code: The item receiving the user defined forecast.
• B - Type: Enter the value 2 to define a location specific forecast. If DRP is not enabled, column B should not be included.
• C - Loc. Code: The location the forecast is being applied. This is required if DRP is enabled. If DRP is not enabled, column C should not be included.
• D- Past Due (Optional): Used when on hand at a customer or VMI location is being considered. If included, the values should be populated with 0 for items that don't have past due. The reason it is called past due is because the value goes into the past due column of the forecast and should be a negative number if on hand is included. This can also be used to include unconsumed forecast.
• E - Day 1 Month 1 Forecast. If DRP is not enabled, the forecast should start on column B or C (if on hand is included).
• F - Day 1 Month 2 Forecast
• G - Day 1 Month 3 Forecast
• H - Day 1 Month 4 Forecast
• I - Day 1 Month 5 Forecast
• J - Day 1 Month 6 Forecast
• K - Day 1 Month 7 Forecast
• L - Day 1 Month 8 Forecast
• M - Day 1 Month 9 Forecast
• N - Day 1 Month 10 Forecast
• O - Day 1 Month 11 Forecast
• P - Day 1 Month 12 Forecast
• Etc

Once the file is ready, save as a tab delimited text file (.txt) with the name userdefinedforecastmonths.txt and then zip.

Upload using the manual data upload function.

Once uploaded run a new requirement plan for the item(s).

The Type and Location Code are included in columns B and C.

The Type and Location Code ARE NOT included. The forecast value starts on Column B.

The weekly user defined forecast spreadsheet includes some extra information as compared to the monthly forecast. The monthly forecast upload option is the easier of the two to manage.

Create a spreadsheet with the following information. Leave the column headers in the file so DemandCaster will know what date buckets to apply the forecast against. The two formats are shown in the image below.

The table columns are as follows:

1. Column A - Item Number: Item number being forecasted
2. Column B - Type: Enter the value 2 to define a location specific forecast. If DRP is not enabled, column B should not be included.
3. Column C - Loc. Code: The location the forecast is being applied. If DRP is not enabled, column C should not be included.
4. Column D - LSL - Lower Stocking Limit: This is the customer provided minimum level of stocking. Select "Select Customer Minimum Safety Stock" in item options to enable.
5. Column E - USL - Upper Stocking Limit: Used for information purposes only at this time. DemandCaster will calculate the upper stocking limit.
6. Column F - Past Due: This is the current stock level at your customer. This value goes into DemandCaster's past due row which is why it is called past due.
7. Column G - ? - Week to be forecasted: The number of weeks to be forecasted can be as far out in the future as required. Use the Sunday of each week as the beginning of the weekly forecasted period.

Once the spreadsheet is complete, save as a tab delimited text file (.txt) with the name userdefinedforecast.txt and then zip and upload.

Once uploaded run a new requirement plan for the item(s) using User Defined Forecast as the consumption type.

The Type and Location Code are included in columns B and C.

The Type and Location Code ARE NOT included. The LSL value starts on Column B.