Price Change Fails in RPM With "ORA-00001: Unique Constraint Violated" Error When the PRICE_CHANGE_ID Sequence Reaches Its Maximum
Last updated on AUGUST 17, 2016
Applies to:Oracle Retail Price Management - Version 13.1.3 to 220.127.116.11 [Release 13.1]
Information in this document applies to any platform.
In Retail Price Management (RPM) 13.1.3.x, price changes fail with the below error when the PRICE_CHANGE_ID sequence reaches its maximum.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms