CMT - Multi-Schema UNIQUNESS_T, AU_UNIQUENESS_T And UNIQUNE_ACCT_NO_T Use System Date Value
(Doc ID 1597267.1)
Last updated on MARCH 23, 2019
Applies to:Oracle Communications Billing and Revenue Management - Version 220.127.116.11.0 to 18.104.22.168.0 [Release 7.5.0]
Information in this document applies to any platform.
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.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document