My Oracle Support Banner

RPM_CONFLICT_QUERY_CONTROL_SEQ Not Being Used in Seed Data to Populate RPM_CONFLICT_QUERY_CONTROL (Doc ID 2385693.1)

Last updated on AUGUST 30, 2018

Applies to:

Oracle Retail Price Management - Version 16.0.1 and later
Information in this document applies to any platform.

Symptoms

RPM 16.0.1

The sequence RPM_CONFLICT_QUERY_CONTROL_SEQ is not being used in seed data script that populates
RPM_CONFLICT_QUERY_CONTROL (rpm-db/install_scripts/rpm_conflict_query_control_seed_data.sql)
and after the product installation this sequences is still in value 1 for conflict_query_control_id while it should be at 13.

Cause

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
Symptoms
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.