Why is RPM Conflict Check Process Not Auto Clearing CC Tables for Batches?

(Doc ID 2371184.1)

Last updated on MARCH 15, 2018

Applies to:

Oracle Retail Price Management - Version 14.0.3 to 14.0.4 [Release 14.0]
Information in this document applies to any platform.

Goal

In RPM 14.0.3, RPM conflict check process is not populating AUTO_CLEAN_IND to 1 for Injectorpriceeventbatch, LocationMovebatch and few other batches.
Is there a specific reason for excluding them?
 

Solution

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