InjectorPriceEventBatch Reports Invalid Number of Clearance Resets Being Created

(Doc ID 2177045.1)

Last updated on SEPTEMBER 14, 2016

Applies to:

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

Symptoms

The issue described in this document is known to Oracle, and a fix already scheduled for future release.
This article will be updated as official patch information becomes available.

When running the InjectorPriceEvent batch, the process reports an incorrect number of clearance resets being made.


Steps to Reproduce:

  1. Create and Approve an emergency Zone A Level Clearance for VDATE with no Reset Date or Out of Stock Date defined.
  2. On day+1: Create and Approve an emergency Zone A Level Clearance RESET for VDATE using the Price Injector Batch.
  3. On day+2: Create and Approve another emergency Zone A Level Clearance with no Reset Date or Out of Stock Date defined.
  4. On day+3: Create and Approve an emergency Zone A Level Clearance RESET for VDATE using the Price Injector Batch.
  5. Check Price Injector report, which shows an invalid number of clearance resets.  Also, the previous clearance resets have the wrong status - "Approved" instead of Executed.

Cause

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