CMT - Multi-Schema UNIQUNESS_T, AU_UNIQUENESS_T And UNIQUNE_ACCT_NO_T Use System Date Value (Doc ID 1597267.1)

Last updated on SEPTEMBER 19, 2016

Applies to:

Oracle Communications Billing and Revenue Management - Version 7.5.0.0.0 to 7.5.0.0.0 [Release 7.5.0]
Information in this document applies to any platform.

Symptoms

For a multi-schema setup in BRM, for the tables UNIQUENESS_T, AU_UNIQUNESS_T, UNIQUE_ACCT_NO_T, CREATED_T and EFFECTIVE_T, values are getting populated based on system date, upon data migration through CMT.

Impact is that rating fails, as these dates are not in-sync with the ACCOUNT_T, CREATED_T and EFFECTIVE_T values.

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