Clearance End and New Clearance Result in Incorrect RIB Messages: RPM_PRICE_EVENT_PAYLOAD Table Contains a MOD Message Instead of a CRE Message
(Doc ID 1619123.1)
Last updated on APRIL 19, 2017
Applies to:Oracle Retail Price Management - Version 13.2.4 to 13.2.8 [Release 13.2]
Information in this document applies to any platform.
In Oracle Retail Price Management (RPM) 13.2.x, we find that when creating a new clearance after resetting an existing clearance, the RPM_PRICE_EVENT_PAYLOAD table contains a MOD message, CLRPRCCHGMOD, for the new clearance.
It should be a CRE message.
Steps to Reproduce:
- Log in to RPM.
- Navigate to Clearances > Create Clearance screen.
- Create an open ended clearance (without reset date) at parent/zone level and approve it.
Note that a CRE message is generated in the RPM_PRICE_EVENT_PAYLOAD table.
- When the above clearance is in executed state, add the reset date as vdate from Maintain Clearance screen.
Note that a CRE message is generated for the reset date.
The status in RPM_CLEARANCE_RESET table is ‘approved’. It should have been changed to ‘executed’ as the emergency reset is done for today.
- Create another future dated clearance for the same parent/zone and approve it.
Note that a MOD message is generated. It should be a CRE message.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!