Unique Constraint Violation While Importing Transition Objects on PDC
(Doc ID 2738282.1)
Last updated on DECEMBER 24, 2020
Applies to:Oracle Communications Pricing Design Center - Version 220.127.116.11.0 and later
Information in this document applies to any platform.
In the current scenario, the transition objects cannot be imported from a legacy PDC system (Pricing and Design Center) into a test environment, because of an unique constraint violation.
Customer is not using internal ids and there are no duplicates in the xml file.
The following parameters were used with ImportExportPricing tool: "-import, -ignoreID, -ow, -pricing, transitions.xml, -url, t3://<
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