Price Injector Batch Ignores The Secondary Zone Record Based On Area Diff Strategy (Doc ID 2217504.1)

Last updated on JULY 05, 2017

Applies to:

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

Symptoms


When creating a price change on Area diff strategy at primary zone with two effective dates for a single item. At secondary zone the price change event is created for one of the future date ignoring the other date.

The issue can be reproduced at will with the following steps:

  1. Define a area differential strategy for one department
  2. Insert 2 future Price changes in the staging tables for one item that belongs to department from steps 1, for primary zone define in the area diff strategy
  3.  Run the injector batch to load the Price changes, both PCs are processed, but for secondary zone only one price change is generated


Changes

 

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