2.3.10 Activity: Create Demand Forecast - Nothing happens

zarrpac

Hi there,

for Baseline forecast:

IF 'SYS01 Time Settings By Week'.'1st Forecast Year?' THEN 'DAT03 Historic Volumes'.'Offset Volumes for 1st Forecast Year' ELSE OFFSET (Default Forecast, -52, 0)

This formula seems right and it's the same thing I've seen from the solutions offered in the forum.

But nothing happens.

Also, for DAT03 Historic Volumes why am I getting 176,744? From the examples ive seen here the volumes are around 50-60?

Thanks.

Prajjwal88

Hi @zeebuggy ,

The issue seems to be with the current formula you're using for Baseline Forecast. Since you've already calculated the first forecast values for FY20, for the 1st Forecast Year, you should pull the values from DAT03. For subsequent years (FY21 and beyond), the forecast should be based on the Default Forecast line item (which considers growth %).
Corrected formula for Baseline Forecast:
IF 'SYS01 Time Settings By Week'.'1st Forecast Year?' THEN 'DAT03 Historic Volumes'.Offset Volumes for first forecast years ELSE OFFSET(Default Forecast, -52, 0)

Additionally, the main issue is due to the formula in your DAT03 module for Offset Volumes. The current formula is incorrectly forecasting values when it is the 1st Forecast Year because of an extra "NOT" condition.
Corrected formula for Offset Volumes for first forecast years:
IF 'SYS01 Time Settings By Week'.'1st Forecast Year?' THEN OFFSET(Volumes, -52, 0) ELSE 0

I hope this will solve your Issue.

Prajjwal88

Hi @zeebuggy ,
You need to check the dimensions of the source module line items in DAT03 Historic Volumes. As you can see, a subsidiary view has been created for both line items.

To resolve this, go to the Blueprint View and check the 'Applies To' and 'Time Scale' settings. They should be set as follows, (If you're still stuck after verifying these settings, kindly share a screenshot of the Blueprint View)

I hope this helps.

zarrpac

Hi Prajwl88,

Thanks for the response.

Nothing happens still.

DEM03 Demand Forecast

Also, why am I getting the wrong data from the datahub

THe import should have populated it with this data:

Thanks again.

Prajjwal88

Hi @zeebuggy ,

In the screenshot you attached, I noticed that in DAT03 for the Volume line item, the ‘Applies To’ setting is blank instead of a dash (-).

The dash indicates that the line item follows the same dimensions as the module, whereas removing it excludes those dimensions. This means that P3 SKU and Accounts are currently not applicable for the Volume line item.

To resolve this, you can add the dash back in the ‘Applies To’ setting and then re-import the data to get the correct values. Similarly, you need to add the dash in the DEM03 module as well to ensure consistency in dimensions.

Hope this helps.

zarrpac

Hi Prajjwal88,

Thank you, it worked!

But now the problem is nothing comes up for the DEMO03 Demand Forecast

I used this for the Baseline Forecast:

IF NOT 'SYS01 Time Settings By Week'.'1st Forecast Year?'THEN    LAG(Default Forecast, 52, 0, STRICT) ELSE    'DAT03 Historic Volumes'.Offset Volumes for first forecast years

And also this:

IF 'SYS01 Time Settings By Week'.'1st Forecast Year?' THEN 'DAT03 Historic Volumes'.Offset Volumes for first forecast years ELSE OFFSET(Default Forecast, -52, 0)

Growth rate: 'DEM02 Volume Growth Rates by Week'.Growth %[LOOKUP: 'SYS08 SKU Details'.Product Family]

Default Forecast: Baseline Forecast * (1 + Growth Rate %)

Initial Demand Forecast: ROUND(Default Forecast, 0, UP)

I don't know what I'm doing wrong.

Thanks!

zarrpac

Hi,

Just an update. I was able to make it work:

But nothing is generated for FY21?

What's wrong with my formula?

Thanks!

zarrpac

Hi Praj,

I changed the formula to your suggestions but the problem is it's not working:

and for the baseline forecast

I used the same formula as you suggested before but changed and experimented with different combinations and when I added the "NOT" it worked in pulling the historical data.

Thanks!

zarrpac

Hi Praj,

I figured it out

My SYS01 Time Settings was set to month

I wasted hours and this was the only problem 😅

Thanks for your help! It's greatly appreciated. 😊

thomas8927eva

Make sure 'SYS01 Time Settings By Week'.'1st Forecast Year?' is returning TRUE for the weeks you’re expecting to shift, and verify there’s actual data in Default Forecast for the OFFSET to pull. For the large number in DAT03, double-check your data import and summary settings—chances are you’re aggregating over multiple items or have mapped data incorrectly, leading to inflated volumes. myaccountaccess.com login