Last updated on SEPTEMBER 22, 2016
Applies to:Oracle Retail Price Management - Version 13.1.7 and later
Information in this document applies to any platform.
When cancelling a large promotion component, that many promo details remain in Pending Cancel state with the end_date set to (end of) vdate, but the rpm_promo_item_loc_expl.detail_end_date is not updated (it remains set to the original promotion end date).
This results in subsequent promotions failing conflict checking because they "overlap" with the *cancelled* promo.
Steps to Reproduce
The issue can be reproduced at will with the following steps:
1. Create two promotion components/details, one for many item-locs and one for a single location.
2. Approve, run PEE, PEERMS
3. Cancel the promotions before the rpm_promo_dtl.end_date. Note that promo detail is in Pending Cancel state and end_date of promo detail is trunc(vdate).
4. Note that rpm_promo_item_loc_expl.detail_end_date for the large promotion is still set to the original end date, while the detail_end_date for the small promotion is trunc(vdate).
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