Emergency Clearance with Item and Location Exceptions Behaves Differently than Clearance created at Future Dates (Doc ID 2253907.1)

Last updated on APRIL 24, 2017

Applies to:

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

Goal

Why Emergency Clearance with item and location exceptions behaves differently than clearance created on future date?

Case 1: Clearance created at vdate

1) Create clearance on parent/zone level, 30%off. Press Apply (do not approve)
2) Create location exception for store 4020 40%off from line that was created as an outcome from 1.
3) Create transaction exception for 210951704 40% off from line that was created as an outcome from 1.
4) select all 3 lines that were created and press approve.
5) Notice that all 3 price events are in Executed status.


Case 2: Clearance created at Vdate +1

1) Create clearance on parent/zone level, 30%off. Press Apply (do not approve)
2) Create location exception for store 4020 40%off from line that was created as an outcome from 1.
3) Create transaction exception for 210951704 40% off from line that was created as an outcome from 1.
4) select all 3 lines that were created and press approve.
5) Notice that the first 2 price events are in Approved status and the transaction exception moved to 'Worksheet' status.
It shows a conflict "An approved clearance for the item/location/date already exists"
 

Solution

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