Calculate Dependent Demand Where From A Null %

(Doc ID 1608555.1)

Last updated on DECEMBER 18, 2017

Applies to:

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


On : 7.3.1 version, DM-Gen

When a part has no history the calculate dependent demand workflow (calculate history planning percent) updates the planning percent history with "null" instead of zero (0). This behavior drives incorrect calculation of dependent demand series.

An example is where we replaced null with zero and re-ran the dependent demand workflow.
The child demand was appropriately reset to zero to align with the parent. Else, the null allows the child to carry demand despite no history of the parent.

This is an apparent critical logic fault and needs to be resolved for proper dependent demand forecast.
Either a null should be treated as a zero or a zero should be presented from the workflow.

The issue can be reproduced at will with the following steps:
1. Run the Calculate Dependent Demand workflow
2. Check the output

The issue has the following business impact:
The null allows the child to carry demand despite no history of the parent, thus causing excess inventory for the child items


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