Last updated on MARCH 08, 2017
Applies to:Oracle Demantra Demand Management - Version 12.2.2 and later
Information in this document applies to any platform.
Customr is on 12.2.2
2.2.2 11 0 06-NOV-13
12.2.2 11 0 08-JAN-14
12.2.2 11 0 12-MAR-14
They mention that after installation, they did the following
Upgrade_to_cal_month.main(null,null) was run to split dates
Inputs was checked to see that new days were added and they were.
All history and forecast data was loaded from scratch and it followed the new inputs dates
EngineScaleInput was set to Yes
Causals were marked be scaled (Scale Causals)
They have noticed that when the first day of the month is not a monday (the first day of the week in a weekly model) the Worksheet miscalculates the dates.
Ex: If the today's date is 1 April 2014 and the Worksheet is configured to use Calendar Month time period and Specify Relative to Today Time window is 0 before and after, the worksheet will show results for March 2013. The Worksheet must recognize that the 1st of April falls in April 2014 so it must show April 2014 results.
This does not happen for Time Window 6 before and after. Since 1 Sep 2014 is a Monday the Worksheet shows the correct results of September 2014.
First day of the week: Monday
Splitting programs were used during installation to use Calendar Month
Everything works correctly at Lowest level, Calendar Month level etc. just that they notice this problem in these first weeks.
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