Retail Price Management(RPM) Populates Inconsistent Approve Id in Clearance Tables
Last updated on JUNE 21, 2016
Applies to:Oracle Retail Price Management - Version 14.1 and later
Information in this document applies to any platform.
This article will be updated as official patch information becomes available.
For clearance with a reset date, RPM updates RPM_CLEARANCE.APPROVAL_ID as RPM login user id. But RPM_CLEARANCE_RESET.APPROVAL_ID is populated with database schema id.
Steps to reproduce:
1. Create a new clearance with reset date.
2. Approve it.
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