Demantra - Redefining Item Code After NPI Step
(Doc ID 1567897.1)
Last updated on SEPTEMBER 09, 2023
Applies to:
Oracle Demantra Demand Management - Version 7.3.0 to 12.2.1 [Release 7.3.0 to 12.2]Information in this document applies to any platform.
Goal
The user leverages NPI functionality to create new "fictive" products, which are not in source system Data yet, and analyze their forecast.
Then the new product is put into production, manufactured and sold to clients, so there is the necessity of associating the product code of this real new item, to the product code of the "fictive" item created through NPI, in order to effectively import the newly available history data (that refers to the new real product code) and still have the forecast.
Is there a Best-Practice to achieve this goal? is it sufficient to change product code simply with and Edit method to update the fictive item code with the new real item code?
Solution
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
| Goal |
| Solution |