My Oracle Support Banner

Few Price Changes Remain in Worksheet Status With Conflicts (Doc ID 2887161.1)

Last updated on JANUARY 04, 2024

Applies to:

Oracle Retail Pricing Cloud Service - Version 19.3 and later
Information in this document applies to any platform.

Symptoms

When huge number of emergency price changes at zone level are processed through induction batch, few price changes remain in worksheet status with conflicts.
This happens intermittently.

ERROR
---------------
"plsql_conflict_checking_error"

Error in logger_logs:
"ORA-00001: unique constraint (RMS01.RPM_FRB_UK1) violated"

Steps to Recreate:

  1. Create price change induction file with huge number of price changes at zone level.
  2. Run Pricechangeinjection batch with above file.
  3. Notice that few price changes remain in worksheet status with conflicts.
      "plsql_conflict_checking_error"
    Error in logger_logs:
      "ORA-00001: unique constraint (RMS01.RPM_FRB_UK1) violated"

Changes

 

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
Changes
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.