New Item created through Create Similar Product (NPI) in Demantra doesn't create a new Item in ASCP
(Doc ID 1269157.1)
Last updated on FEBRUARY 26, 2019
Applies to:Oracle Demantra Demand Management - Version 7.3.0 and later
Information in this document applies to any platform.
***Checked for relevance on 11-Sept-2012***
=== ODM Question ===
Q1. We have found that the Demantra Create Similar Product (NPI) method doesn't create a new DKEY_ITEM but instead uses the Source Item's DKEY_ITEM. What this means is that since the Source Item is the only one with a INVENTORY_ITEM_ID in ASCP then even though the Source Item no longer has a Final Forecast > 0 that it still gets the Forecast value uploaded to it in ASCP. This is because the Target Items created in Demantra, through the Create Similar Product process, do not have an unique Inventory_Item_id to otherwise receive this Final Forecast > 0.
Should the Create Similar Product process also create a new DKEY_ITEM value and then also there should be a process in the Upload Forecast workflow that recognizes that the Inventory_Item_Id value doesn't yet exist in ASCP and create it?
Or should the best practice continue to that the item to be loaded from EBS to Demantra and then the user choosing this item_code since that also ensures that the Inventory_Item_Id for this Target Item exists in ASCP (one of the normal rules for the MSD_DP_SCN_ENTRIES_DENORM table to receive a record from Demantra)?
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