NPI Does Not Preserve Item Hierarchy
(Doc ID 1618115.1)
Last updated on APRIL 02, 2019
Applies to:Oracle Demantra Demand Management - Version 12.2.1 and later
Information in this document applies to any platform.
On : 12.2.1 version, Worksheet
If we use NPI method to create a new product that is already present in Demantra T_EP_ITEM table, we find out that the process does not preserve item hierarchy: for example for level Item description that is just above level Item. When we use method "Create similar product" using a Target Code of an item present in T_EP_ITEM, we find that the item gets "created" under the member of level Item description that includes the original item from which the method was invoked, and not the member of Item description that is actually parent of the Target Code item.
Target Item created with NPI to maintain its original hierarchy across all items tables.
The issue can be reproduced at will with the following steps:
1. create a new item with a specific Item description
No history was loaded for this new item
2. Launch NPI method "Create similar product"
3. check the data
The new item gets item hierarchy of item from which the method was launched, so it does not maintain its original hierarchy.
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