Forecast

Field

Description

Forecast consider

Based on SAP Business One standard: Low priority in requirement coverage calculation, customer orders are subtracted.

Like planned customer order: The same priority is given for the forecast in requirement coverage calculation as for the customer orders. Issues of customer orders are not subtracted, forecasts from the past are always considered.

Choosing this option hides all additional options for the forecast calculation, because these have no  consequence anymore. If in an older version of beas at special forecasts "all" was entered, this is now interpreted as "like customer order".

Note:

If in a sales order, the "consume forecast quantity" switch was disabled, there is no offset against existing customer orders.

Pre call time for forecasts

An average delivery time can also be specified in work days for forecasts.

Requirement in the period

Descending: Apply a percentage of the requirement on the remaining days.

Constant: Requirement is always the total quantity.

Ignore past: Requirement is applied to the first day of period.

Example: Today is 25th November of 2016 and there are 2 forecasts, one by week and second one by month. Quantity for both forecast are 100 Pieces.

An MRP executed today provides the following results.

Calculation By Week:

Descending: Quantity = 42,85. We apply a % of pending days. Complete week days are 7, pending days are 3 (Today is Friday 25) then 3(days) * 100(Pieces) / 7(days)

Constant: Quantity = 100. We can execute the MRP each day of the week, the result is the full quantity.

Ignore past: Quantity = 0. Quantity is considered only on the first day of period (In our example day 21 of November, first day of the week).

Calculation By Month:

Descending: Quantity = 20. We apply a % of pending days. Complete month days are 30, pending days are 6 (Today is friday 25) then 6(days) * 100(Pieces) / 30(days)

Constant: Quantity = 100. We can execute the MRP each day of the week, result is the full quantity.

Ignore past: Quantity = 0. Quantity is considered only on the first day of period (In our example day 1 of November, first day of the month).

Consider past

Open sales orders in the past are offset against forecasts.

Consider delivered customer orders

Consider partially delivered or fully delivered sales orders in the current period.

Consumption method

The customer orders are deducted from the forecasts. The behavior is configured here.

Total time range: The planned requirement is first deducted from the oldest forecast (backward – forward) The entire time range applies.

Definable time range: The behavior can be further configured. The options "Direction", "Days Backward" and "Days Forward" are shown for this purpose. Depending on the direction specified, the customer order quantity is deducted from either the first or last forecast. Only the "Customer order delivery date" period less the number of calendar days (forward and backward) is considered. For the time range, an average delivery time is not deducted from the delivery date or the forecast requirement date.

The setting is configured using SAP > Administration > System Initialization > General Settings > Inventory > Planning

Activated "Consumption forecast" means "Definable time range".

Deactivated "Consumption forecast" means "Entire time range".

This behavior can be deactivated by specifying the forecasts, and therefore solved in a different way than in SAP.

Direction

Specifies the direction in which the forecasts should be reduced. Only visible if consumption method was activated as "Definable time range".

Days forward, days backward

Specifies the period from the delivery date of the customer order during which the forecasts should be reduced. Only visible if consumption method was activated as "Definable time range".