Payload Table is Not Updated Correctly when Clearance is Created with Exception
Last updated on JULY 07, 2017
Applies to:Oracle Retail Price Management - Version 14.1.2 and later
Information in this document applies to any platform.
Payload table is not updated correctly when Clearance is created with item and location exceptions.
Steps To Recreate:
1. Create clearance on parent/zone level, 30%off. Press Apply (do not approve)
2. Create location exception for store 1311, 40%off from line that was created as an outcome from 1.
3. Create transaction exception for 100040005 40% off from line that was created as an outcome from 1.
4. select all 3 lines that were created and press approve.
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"
Check the RPM_CLEARANCE_PAYLOAD table.
Notice that the item/loc that did not made into payload is the one on which we have created the transaction exception clearance and location on which location exception is not created. i.e., item 100040005 and loc 1321 is missing.
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