Last updated on SEPTEMBER 08, 2016
Applies to:Oracle Demantra Demand Management - Version 7.3.1 to 12.2 [Release 7.3.0 to 12.2]
Information in this document applies to any platform.
Demantra: Engine forecast produces different results in two consecutive runs without any changes. Basically, one of the forecast, first run, are extremely low compared to the second forecast run. This scenario has been seen twice already.
The issue is caused by the following setup: ResetForeVals = All can not be used with EngineOutputThreshold>0 at the same engine profile.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms