Customer Name is Renamed and Again Collected into Demantra Running Shipment & Booking History Collections, a Duplicate row is Created for the Same Customer.
(Doc ID 1312493.1)
Last updated on NOVEMBER 06, 2019
Applies to:Oracle Demantra Demand Management - Version 220.127.116.11 and later
Information in this document applies to any platform.
Every time there is an EBS, or LEGACY, Change in the name of the customer and run Shipment & Booking history collections , Duplicate Customers are getting created in Demantra.
1) Run Shipment & Booking History Collections to collect data into Demantra.
2) Modify the name of one of the customer, for which data has been collected into Demantra, in EBS.
3) Run Shipment & Booking History Collections to collect data into Demantra again.
A new Customer entry gets created in Demantra, resulting in Duplicate Customer.
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