Regular Price Change Fails Conflict Checking Instead Of Resetting Clearance As Expected
(Doc ID 2850478.1)
Last updated on NOVEMBER 01, 2023
Applies to:
Oracle Retail Pricing Cloud Service - Version 19.3 and laterInformation in this document applies to any platform.
Symptoms
On : 19.3 version, Pricing - Price Changes
With RPM_PE_CONFIG_OPTIONS.RESET_CLR_WITH_PRICE_CHANGE = 1, you observe that a newly created price change fails conflict checking and remains in worksheet status
The issue can be reproduced at will with the following steps:
1. Confirm RPM_PE_CONFIG_OPTIONS.RESET_CLR_WITH_PRICE_CHANGE = 1 (checked)
2. Identify item/loc with current clearance state = Executed
3. Confirm no other Regular Price Change with effective date > effective date of Clearance exists
4. Create Regular Price Change for item/loc in Step 1 where effective date of PC > CLR
5. Approve Regular Price Change
6. Note that Regular Price Change fails conflict checking
Changes
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 |
| Changes |
| Cause |
| Solution |
| References |