Demantra Not Respecting Engineoutputthreshold Parameter Setting
Last updated on SEPTEMBER 08, 2016
Applies to:Oracle Demantra Demand Management - Version 7.3.1 and later
Information in this document applies to any platform.
We are trying to validate the EngineOutputThreshold parameter setting. While we have setup the value of this parameter to 50%, even forecast changes which are less than 50% are being written, while this parameter should force retainment of old forecast values for such cases.
1) Steps to Reproduce
1. Setup engine parameter "EngineOutputThreshold" to 50%.
2. Now make small changes to history using overrides, save changes and run engine in batch mode.
3. Expected result is forecast value remains as old value, as history volume changes are small comapred to the threshold set.
Why the forecast going up or down even below threshold setup is being written to Demantra’s Sales_data table and is being shown as forecast to users.
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