Complex Promotion Created or Modified Is Not Getting Published to ORPOS (Doc ID 2135847.1)

Last updated on MAY 20, 2016

Applies to:

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

Symptoms

A complex promotion created or modified in Retail Price Management (RPM) is not getting published to Oracle Retail Point-of-Service (ORPOS).


Steps to Reproduce:

  1. In RPM_SYSTEM_OPTIONS set DO_NOT_RUN_CC_FOR_CP_APPROVAL to 1 and CC_DIRECT_PAYLOAD_POPULATION to 1.
  2. Choose a parent having a few child items. Range only the child items to few stores.
  3. Run RPM New Item Location (NIL) batch.
  4. Create a threshold promo for the item in step 2 at zone level and promo start day as tomorrow.
  5. Note that entries are made in RPM_PROMO_DTL_PAYLOAD, RPM_PRICE_EVENT_PAYLOAD, and RPM_PROMO_LOCATION_PAYLOAD tables; but no entries appear in RPM_PROMO_ITEM_LOC_SR_PAYLOAD.
  6. Run RPMtoORPOSPublishBatch.
  7. Query RPM_ORPOS_COMPLX_PROMO_PUBLISH for the promo created in step 4 and note that there are no entries.
  8. Run Price Event Execution (PEE) and PEE-RMS batches.
  9. Advance vdate to next day.
  10. Change the end date for the promo.
  11. Note that entries are made in RPM_PROMO_DTL_PAYLOAD, RPM_PRICE_EVENT_PAYLOAD, and RPM_PROMO_LOCATION_PAYLOAD tables; but no entries appear in RPM_PROMO_ITEM_LOC_SR_PAYLOAD.
  12. Run RPMtoORPOSPublishBatch.
  13. Query RPM_ORPOS_COMPLX_PROMO_PUBLISH for the promo created in step 4 and note that there are no entries.

 

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