Dying Time Increase Not Causing Prediction_Status To Equal 1 (Doc ID 1926002.1)

Last updated on JUNE 05, 2017

Applies to:

Oracle Demantra Predictive Trade Planning - Version 12.2.2 to 12.2.2 [Release 12.2]
Information in this document applies to any platform.

Symptoms

12.2.2 in Production and Test

PROBLEM
-------------
After modifying the dying_time parameter to 208 weeks (longer than sales_data history), it was expected that NO mdp_matrix combinations would have a prediction_status = 99 (Dead combination).
If a combination has never been shipped (Quantity_Form never > 0), then it is expected that the combination be "Too Young" not "Dead".
Please advise how to eliminate "dead" combinations from the Demantra model where shipments never > 0. They should be "Too Young"

STEPS
--------.
Records exist in sales_data, but actual_quantity (and thus Quantity_Form result) is never > 0. These combinations are "Dead" in stead of "Too Young" as expected.

 

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