Forecast Columns Getting Dropped From SALES Data

(Doc ID 2066576.1)

Last updated on MARCH 08, 2017

Applies to:

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


On : version, Technical

check_fore_series procedure is dropping the FORE_x columns from sales_data table.

check_fore_series procedure should only drop the wrong fore_x columns, not all fore_x columns.


In engine manager log file, bellow error may show up:

ERROR Table SALES_DATA is missing the following columns: FORE_32_OUTLIER@NUMBER(20,10) NULL@FORE_32@NUMBER(20,10) NULL@FORE_31_OUTLIER@NUMBER(20,10) NULL@FORE_31@NUMBER(20,10) NULL@FORE_30@NUMBER(20,10) NULL@FORE_30_OUTLIER@NUMBER(20,10) NULL

The issue can be reproduced at will with the following steps:
1. Log into Business Modeler .
2. Create a new engine profile with profile_forecasts_versions = 5 .
3. Check that the corresponding fore_x columns were created in sales_data table .
4. Run engine.
5 Check the missing columns from sales_data table.

The issue has the following business impact:
Due to this issue, users cannot create new engine profile in production as forecast column could get dropped affecting engine run.


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