Data In Payload Tables Has A Discrepancy With RPM_FUTURE_RETAIL Table
Last updated on JULY 07, 2017
Applies to:Oracle Retail Price Management - Version 14.1 and later
Information in this document applies to any platform.
Data in payload tables has a discrepancy with RPM_FUTURE_RETAIL table.
Steps To Recreate:
1. Create parent item/zone level price change (2 zones and 1 parent item) - 50% markup .
2. Create transaction level item (202431060) exception - 60% markup.
3. Create location exception (7201 - belongs to zone 3, 7117 - belongs to zone 1) - 40% markup.
As expected system outline conflict check for 40% markup because there is 60% markup but we noticed that for item 202431062 and location that are on exception there are no records in payload table - the change with 50% markup for this items was not communicated.
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