(Doc ID 2299243.1)

Last updated on AUGUST 21, 2017

Applies to:

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


When engine is aggregating history data from item level to an aggregate product hierarchy level for
forecasting there is no UOM conversion happening resulting in reflecting of wrong forecast

So if history is being aggregated to a parent level where the parent member
has items with different base UOMs, then the aggregated number won't be
correct unless the quantities are converted to a common UOM.
While in a worksheet, user has the ability to specify the display unit. The
same is not available in engine
The requirement is that demantra handles different UOMs and engine should
take UOM in account instead of all items stored in unified units.

Demantra does not identify different items with different UOM,So UOM
conversion is not getting considered during generating statistical forecast.



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