My Oracle Support Banner

Worksheet Max_sales_date Not Reflected when it's changed in BM or Load Process (Doc ID 1561403.1)

Last updated on FEBRUARY 03, 2019

Applies to:

Oracle Demantra Demand Management - Version 7.3.1.4 and later
Information in this document applies to any platform.

Symptoms

On : 7.3.1.4 version, LoadData

ACTUAL BEHAVIOR
Set last_date_backup and max_sales_date to current week's date.
In QA instance it doesn't show effect on worksheets unless we restart the web server.
But same works fine in DEV instance without restarting the web server.

EXPECTED BEHAVIOR
QA instance --to show effect on worksheets disregarding the web server restart.

STEPS
The issue can be reproduced at will with the following steps:
-- loading future/forecast data based on POS in t_src_sales_tmpl in sdata4 column.
-- loading historical data (based on Invoice) in actual-qty column.
-- run ep_load_main, After ep_load_main completes we are resetting two dates from Business Modeler.

BUSINESS IMPACT
It is not possible in actual production system to restart web server every time we load data.

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Symptoms
Cause
Solution
 Checking if the notification was received by the application server
  Checking that the network is functioning, the AppServer is configured correctly to accept connections, and that the AppServerURL is set right
 If using customized data load process, please ensure that you run EP_LOAD_MDP_LEVEL after any change is made to the max_sales_date so that the application sever is notified of the change
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.