AMT Fails To Update Uniqueness_t And Au_uniqueness_t Tables

(Doc ID 1369893.1)

Last updated on JULY 27, 2017

Applies to:

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


On Oracle Communications Billing and Revenue Management(BRM), version, the Account Migration Manager(AMT) Utility fails to update 'uniqueness_t' and 'au_uniqueness_t' tables.

Consider the following scenario, where tow accounts are created in hierarchy.

They share discounts and AMT successfully recognizes them as group.

However in the output for the Query: "select batch_type from job_batch_amt_t" give result "2", unfortunately uniqueness_t is still not updated.


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