Base Override Data Needs To Be Re-Entered When New Combinations Are Created. The application should automatically re-proportion the initial DC level override to the new Ship Tos
(Doc ID 1331606.1)
Last updated on AUGUST 23, 2019
Applies to:Oracle Demantra Demand Management - Version 7.3.0 and later
Information in this document applies to any platform.
Q1. Users enter base over ride data at an aggregated level (ex. Distribution Center by Item) in a worksheet and then let Demantra proportion the base over ride data down to lowest levels (ex. Ship To). After sales history is collected and new item-location combinations are collected now reflecting that new Ship To locations are now selling that item, do we need to re-enter the base over ride data in order to get the new combinations included in the override originally done at the Distribution Center (DC) by Item level?
If the answer is yes then is there a work around available for this to avoid re-entry of data?
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document