RefreshPosDataBatch Does Not Populate Reset Date for Clearance Payload
Last updated on APRIL 18, 2016
Applies to:Oracle Retail Price Management - Version 13.2.6 and later
Information in this document applies to any platform.
In Oracle Retail Price Management (RPM), the RefreshPosDataBatch does not populate clearance payload with a reset date.
Steps to Reproduce:
1. Create clearances with reset date.
2. Approve the clearances.
3. Payload tables are populated in tables RPM_PRICE_EVENT_PAYLOAD and RPM_CLEARANCE_PAYLOAD.
4. Now run refreshPosDataBatch with a future date before the reset date.
5. Notice that RPM_CLEARANCE_PAYLOAD is populated only for the clearance record having Effective date; the second record having reset date as effective date is not populated.
After approval – it should populate 2 records, one for clearance with effective date and the other with clearance reset date as effective.
Due to this issue, Oracle Retail Point of Service (ORPOS) does not receive a reset date.
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