The Provided Reset Date Must Be After All Clearance Item Effective Dates
(Doc ID 2943993.1)
Last updated on APRIL 21, 2023
Applies to:
Oracle Retail Price Management - Version 14.1.3 and laterInformation in this document applies to any platform.
Goal
While trying to remove Items/Locations from the Clearances (reset Clearance activity), and when those Items/Locations have an approved Clearance for a future effective date, RPM throws the error "The provided Reset Date must be after all Clearance item Effective Dates" mapped to CLEARANCE_RESET_DATE_BEFORE_LAST_EFFECTIVE_DATE in the RPM_MESSAGES.PROPERTIES file.
What is the reason behind this rule/limitation? You create many Clearances for future dates based on historical sales during the same period/season and suggestions from Data Scientists and Machine Learning models. However, when you need to remove items/locations from your active Clearances, you cannot do that because of the error. So why shall RPM mix or compare future Clearances with active Clearances to end up in a conflict? What's the benefit of doing so?
Solution
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
Goal |
Solution |