My Oracle Support Banner

Deal Explode Batch Does Not Remove Exclusions from Existing Deal (Doc ID 2688578.1)

Last updated on JULY 14, 2020

Applies to:

Oracle Retail Merchandising System - Version 13.0.4.7 and later
Information in this document applies to any platform.

Symptoms

When batch 'Deal Explode' it is used, exclusions are not removed from an existing deal.
The deal explode batch program (deal_explode_sql.DEALEX_PROCESS) only applies exclusions to new deals.
If the deal is existing, the exclusions will not be applied.
For example, if it is set a deal for department(dept) 100 and exclude dept/class 100/1, when the deal is first exploded, items from dept 100/class 1 will be excluded. However when a new item is added to this class, it will be added to the deal.

The issue can be reproduced with the following steps:

  1. Setup a new receipt based Bill-Back Rebate (BBR) deal in RMS(Retail Merchandising System) for a given department that excludes a class in the department:type = promotional, increase active date = vdate(virtual date of the system) + 1 day, billing type = BBR.
  2. Approve the deal.
  3. Run the nightly batch (dealex-pre, dealex and dealex-post).
  4. Confirm records were added to the DEAL_ITEM_LOC_EXPLODE table for the given department excluding the exclusion class.
  5. Advance the vdate.
  6. Add a new item to the exclusion class.
  7. Run the nightly batch (dealex-pre, dealex and dealex-post).
  8. Confirm records were added to the DEAL_ITEM_LOC_EXPLODE table for the exclusion class.

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
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.