Demantra Prediction_status Update Logic Should Consider Quantity_form Parameter Value for the Corresponding Batch Engine Profile (Doc ID 2028564.1)

Last updated on MARCH 08, 2017

Applies to:

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

Symptoms

On : 7.3.1.3 version, Technical

ACTUAL BEHAVIOR
---------------
Proport procedure does not consider quantity_form parameter . As a result, the the system is updating the combination as dead (prediction_status=99) if history for that item is 0 though it has the demand .

EXPECTED BEHAVIOR
-----------------------
Proport procedure should consider the quantity_form parameter instead of history when setting the combination as active or dead.

STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. Connect to demantra schema using some sql tool like SQL Developer.
2. Execute proport procedure.
3. Check the demand and the prediction_status of that combination.

BUSINESS IMPACT
-----------------------
The issue has the following business impact:
Due to this issue, the system is setting up the combination as dead and it doesn't generate the forecast for this combination. This is happening in production instance.

Cause

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