Last updated on MARCH 08, 2017
Applies to:Oracle Demantra Demand Management - Version 7.1 and later
Information in this document applies to any platform.
On 7.1 in Production:
Webserver requires a restart whenever a key parameter like max_sales_date moves as the result of a
new data load
Client would like it to act more like a regular user update where the change is seen immediately.
The issue can be reproduced at will with the following steps:
1. Load new demand (ex. for a new week or month) and log into the Demantra worksheet. The new
data is not reflected there
The issue has the following business impact:
Due to this issue, clients don't see the freshest data loaded into the system
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms