My Oracle Support Banner

ORA-30926 Received When Running Price Event Execution (PEE) Batch for Emergency Price Change in Chunk Mode (Doc ID 2080016.1)

Last updated on FEBRUARY 03, 2019

Applies to:

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

Symptoms

In Oracle Retail Price Management (RPM) 13.2.6, when attempting to run PriceEventExecutionBatch, the following error occurs when there are 2 fixed price changes with the same effective date:


Steps to Reproduce:

  1. Create item (ITEM_LEVEL = 1, TRAN_LEVEL = 2)
  2. Create SKUs
  3. Range SKUs to locations
       IMPORTANT: Make sure that SKU * Location > RPM_BATCH_CONTROL.THREAD_LUW_COUNT * RPM_SYSTEM_OPTIONS.CONFLICT_CHECK_CHUNK_FACTOR (com.retek.rpm.app.bulkcc.service.ChunkConflictCheckAppService)
  4. Approve item parent
  5. Run NewItemLocBatch
  6. Create emergency price change at parent/zone level
  7. Approve emergency price change
       IMPORTANT: Make sure RPM_PRICE_CHANGE.EFFECTIVE_DATE >= PERIOD.VDATE - RPM_SYSTEM_OPTIONS.PRICE_CHANGE_PROCESSING_DAYS
  8. Create another emergency price change at parent/zone level for the same day as the one created in the previous 2 steps.
  9. Approve emergency price change
  10. Run PriceEventExecutionBatch

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.