Time Series Based Forecast Consumption vs Customer Sourcing

[Former Member]

Dear IBP Experts

In our current IBP setup, we work with a demand planning part that is focused on Product - Customer Levels. The final Consensus forecast is then 'sourced' via the standard Customer Sourcing setup in order to achieve Dependent Customer Demand on Prod-Loc-Cust Level. Then we use the S&OP Unconstrained Heuristic. We are now looking into the Forecast Consumption logic, but we have difficulties to combine this with our Customer Sourcing Logic.

Theoretically, we would work in following way:

1. Source the demand on product-customer level via Customer Sourcing in order to have forecast also on location level.

2. Perform Forecast Consumption on product-location level

3. Run the Heuristic.

However, this currently does not seem possible as the Heuristic (step 3. always performs Custom Sourcing again).

Any recommendation on how to use Forecast Consumption in our case?

Kristof

[former_member242371]

Hello Kristof,

You can run forecast consumption as Independent calculation instead of using it with heuristic.

First run heuristic to calculate dependent demand at location using customer sourcing and then perform forecast consumption run to calculate the net output open forecast at location.

Thanks,

Rohit

[Former Member]

Hello Rohit,

Thanks for your reply. I agree with that, but after consuming the forecast, we want to run the Supply Heuristic on the Total Demand, so on the output of the Forecast Consumption. But we cannot 'deactivate' customer sourcing, so this will be recalculate the dependent demand, which will then be used by the heuristic. So the open orders that consume the forecast are not taken into account in the supply heuristic. It would be great if customer sourcing was not reperformed each time when running the heuristic.

Best regards

Kristof

[former_member242371]

Hi Kristof,

One way i could think of is to calculate total open demand using forecast consumption and copy it into INDEPENDENTDEMAND and run heuristic.

Thanks,

Rohit