Additional calculation levels in the new ‘Forecast Automation Profiles’ app

[Former Member]

Dear All,

This is a question about additional calculation levels in the new ‘Forecast Automation Profiles’ app.

In a recent PoC we found the best Forecasting level to be either Product-CustomerGroup or even Product itself.

And to facilitate the picking of the correct Forecast Model I intended to use the new ‘Forecast Automation Profiles’ app. In general, this works fine and stores the results in attribute TIMESERIESPROPERTY, albeit on ProdLocCust-level.

But when trying to leverage the additional calculation levels in the app (i.e. by aggregating to CustomerGroup, Location and Product), I am not able to pick any additional attribute (I had created additional ones on the according levels) to store the results.

Question: could it be that the app is currently hardcoded to attributes of MDT SourceCustomer? And therefore only works on planning levels with that specific MDT? Is it possible to add an attribute to – let’s say – PRODUCT and make it visible to the app?

Thanks and regards

Kai Wipfler

[rainer_moritz · Accepted solution]

Hi Kai,

my guess is that your other attribute into which you want to write the time series property is defined too short. The attribute need to have a lenght of 100 characters minimum.

Hope this helps.

Best regards,

Rainer

[Former Member]

Thanks Rainer, but as I had taken a copy of TIMESERIESPROPERTY the length was the original NAVCHAR 120.

Has anyone ever used the additional caclulation levels successfully? Using an attribute not attached to MDT SourceCustomer?

Thanks a lot, Kai.