Purpose: Use this screen to define the Forecasting system control values. These values control the calculations used on the Inventory Status & Projection Report (ISRP)
# of Days in Forecasting Period (B96)
Enter the number of days in a forecasting period. You can enter 1 or a 7. If you enter 1, forecast activity will be captured daily. If you enter 7, forecast activity will be captured on a weekly basis.
Forecasting Period Description (B97)
Enter a description of the forecasting period (day or week). The system uses this description on screens and reports. This is a 10-position, alphanumeric field. It is a required entry.
# of Forecasting Periods (B98)
Enter the number of forecasting periods (from 1 to 99) that the system will store. For example, if the number of days in your forecasting period is 7, the number of forecasting periods you could store would be 52. Or, you might not want to collect forecasting data for the entire year, maybe only for 48 periods for example. This is a 2-position, numeric field. It is a required entry.
Note: You cannot enter a number larger than 99.
# of Periods to Collect Daily Data (C01)
Enter the number of forecasting periods for which the system should track daily activity, in addition to tracking forecasting data by period. You can specify that daily data should be collected for all periods, for none, or for any specified number of periods. This allows you to view (through an inquiry function) the activity for each day within a forecasting period. This is a 2-position, numeric field. It is an optional entry.
For example, if you have defined a forecasting period as 7 days for 50 periods, you can specify that for the first three weeks, (in this case periods), the system should track the data by day as well as by week. You may have an offer with a 50 period cycle, but since the first three periods are the most active, you might want to collect daily data for those three periods.
First Day of a Forecasting Period (B99)
Enter the day that begins the forecasting period. If you are tracking daily activity (the # Of Days in Forecasting Period is 1) then this value must be *ANY. Otherwise, one day of the week must be chosen. This is a 3-position, alphanumeric field. It is a required entry.
Valid entries are:
• *ANY = Daily activity
• MON = Monday
• TUE = Tuesday
• WED = Wednesday
• THU = Thursday
• FRI = Friday
• SAT = Saturday
• SUN = Sunday
If you use the Forerunner IF/SO Interface (EFOR, DFOR), you should set this field to MON.
Note: The Forerunner IF/SO interface is not currently implemented.
Forecasting Order Category #1 (B94)
Enter the description of this order category, for example, mail, phone, or any code that meaningfully describes the category for which you want to collect forecast data. This is a 10-position, alphanumeric field. It is a required entry.
Order categories are used to compare in forecast projections (on screens and reports) the number of orders and dollars that are received for each period of the forecast by the order category.
Forecasting Order Category #2 (B95)
Enter the description of this order category, for example, mail, phone, or any code that meaningfully describes the category for which you want to collect forecast data. This is a 10-position, alphanumeric field. It is a required entry.
Order categories are used to compare in forecast projections (on screens and reports) the number of orders and dollars that are received for each period of the forecast by the order category
# of Periods to Offset Returns (C06)
Enter the number of forecasting periods that returns should be offset in the forecast. If you enter a number in this field, returns will not be posted to the period in which they are received, but will be posted to the offsetting period you indicate.
The posting period for returns is determined by this calculation:
Current period
- Number of periods to offset returns
Period number to which the return is posted
For example, if you specified 2 periods, then any returns which occurred in period 5 would be applied against orders which were received in period 3.
Enter the number of forecasting periods that will be added to an item's due date to determine when the item should be re-ordered. This information is used on the Inventory Status and Projection Reports to identify items that you anticipate will go out of stock before the demand for the item is met (as determined in the forecast).
Periods to Use Expected Return % (D27)
(Periods to Use Expected Return Percentage): Enter the number of periods to use the Expected return % defined in the SKU/Offer or Item/Offer table for calculations on the Inventory Status and Projection reports.
After this time has passed, the system will use the actual percentage of returns posted for an offer on the Inventory Status and Projection reports.
The calculation to determine the actual return percentage is:
Actual Return Percentage = Units Returned ÷ Units Sold
Note: The Units Returned value in this calculation includes the number of units exchanged.
Periods to Use Projected Units (H91)
This field indicates whether to use the Projected units from the item/offer or SKU/offer as the Projected units for an item/SKU on the Inventory Status & Projection Report (ISRP). You might want to use the projected units from the item/offer or SKU/offer if it is too early in the offer to produce a valid forecast based on the units that have actually been ordered.
Important: In order for the report to use the Projected units from the item/offer or SKU/offer, you must select the Use projected units field at the Select Class/Sold Out/Curve Overrides Screen when you generate the report.
When the projected units defaults from item/offer or SKU/offer: The report uses the Projected units from the item/offer or SKU/offer on the report only if:
• the current period of the curve is less than or equal to the Periods to Use Projected Units system control value, and
• the Use projected units field is selected at the Select Class/Sold Out/Curve Overrides screen, and
• the % complete based on the curve is zero, or
• there is no demand for the item/SKU (the actual units ordered is zero)
Example: |
curve is 0% complete system control value = 1 current period = 1 actual units ordered = N/A Use projected units is selected Result: projected units: from SKU/offer |
|
curve is 10% complete system control value = 1 current period = 1 actual units ordered = 0 Use projected units is selected Result: projected units: from SKU/offer |
When projected units is calculated: In any other situation, the projected units for an item on the report will use the following calculation:
(Actual units ordered * 100) / % complete
Example: |
curve is 10% complete system control value = 1 current period = 1 actual units ordered = 5 Use projected units is selected Result: projected units: regular calculation (5 units * 100) / 10 percent complete = 50 |
When the projected units will be zero: The projected units for an item on the report will be zero whenever the report uses the calculation described above, but the % complete or the actual units ordered are zero.
Example: |
curve is 10% complete system control value = 1 current period = 1 actual units ordered = 0 Use projected units not selected Result: projected units: zero |
The following table summarizes the determination of the projected units field on the report if you select the Use projected units field:
% complete based on curve |
Current period compared to system control value |
Projected units calculation |
0 |
less than (or equal to) |
Projected units from SKU/offer or item/offer |
0 |
greater than |
0: (actual units ordered * 100) / % complete of 0 |
greater than 0 |
less than (or equal to) |
If the actual units ordered is greater than 0: (actual units ordered * 100) / % complete |
If the actual units ordered is zero: projected units from SKU/offer |
||
greater than 0 |
greater than |
(actual units ordered * 100) / % complete (if the actual units ordered is 0, the Projected units will be 0 |
If you leave this system control value set to zero, the report will never use the Projected units from the item/offer or SKU/offer; instead, it will always use the calculation described above. However, if either the actual units ordered or the Percent complete is zero, the Projected units on the report will also be zero.
