RPM_CONFLICT_QUERY_CONTROL_SEQ Not Being Used in Seed Data to Populate RPM_CONFLICT_QUERY_CONTROL
Last updated on APRIL 18, 2018
Applies to:Oracle Retail Price Management - Version 16.0.1 and later
Information in this document applies to any platform.
The sequence RPM_CONFLICT_QUERY_CONTROL_SEQ is not being used in seed data script that populates
and after the product installation this sequences is still in value 1 for conflict_query_control_id while it should be at 13.
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