My Oracle Support Banner

Demantra Notify App Server Program Is Not Changing The Worksheet Date (Doc ID 2822145.1)

Last updated on NOVEMBER 27, 2021

Applies to:

Oracle Demantra Real-Time Sales and Operations Planning - Version 12.2.7 and later
Information in this document applies to any platform.

Symptoms

On : 12.2.7 version, Procedures,

ACTUAL BEHAVIOR
---------------
The max_sales_date parameter is not reflected in the worksheets, after running an workflow that should update max_sales_date parameter and execute Notify procedure to refresh the application server cache.
 

EXPECTED BEHAVIOR
-----------------------
The max_sales_date parameter should be reflected in the worksheets results.

STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. Log into Demantra Local Application.
2. Go to Workflow Manager
3. Run an workflow that updates max_sales_date parameter value and execute Notify procedure.
4. Open an worksheet.
The history period is not matching with the new modified max_sales_date parameter.

 

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
References


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