My Oracle Support Banner

EVENT_BILLING_TAXES_T Non-unique Records (Doc ID 1304041.1)

Last updated on FEBRUARY 21, 2019

Applies to:

Oracle Communications Billing and Revenue Management - Version 7.4.0.0.0 and later
Information in this document applies to any platform.

Symptoms

Consider the below scenario:

In the BRM database, expect records to be unique based on identifiers: poid_id0 or obj_id0 or combination obj_id0 and rec_id. This assumption is used to uniquely identify data that shall be loaded from BRM to data warehouse (DWH). In case DWH already downloaded the unique record, it is not downloaded in future runs.

During test found that customized table EVENT_BILLING_TAXES_T has non-unique key combination obj_id0, rec_id (see below). Because of this, merge into the target table in DWH failed. 

With testnap:

Changes

 

Cause

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
Symptoms
Changes
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.