Getting Inconsistent Approval IDs on Clearance Tables (Doc ID 2182818.1)

Last updated on SEPTEMBER 19, 2016

Applies to:

Oracle Retail Price Management - Version 14.1.2 and later
Information in this document applies to any platform.

Symptoms

For a clearance with a reset date, approval_id is updated on RPM_CLEARANCE table as the RPM login user id, whereas on the RPM_CLEARANCE_RESET table it provides the database schema id.

The approval_id should be consistent all across the clearance tables.

Steps to Reproduce:
1. Create a new clearance with reset date.
2. Approve it.
Note the approval_id in the RPM_CLEARANCE and the RPM_CLEARANCE_RESET tables.

Changes

 

Cause

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