My Oracle Support Banner

Adding New Fields Under FCT_DuplicateCheck Is Not Validating with Old Data in IFW_DUPLICATECHECK_* Tables (Doc ID 2156575.1)

Last updated on APRIL 01, 2019

Applies to:

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

Symptoms

Consider this Scenario:

  1. With below fields under FCT_DuplicateCheck:
    SearchKey = DETAIL.A_NUMBER
    1 = DETAIL.BASIC_SERVICE
    2 = DETAIL.B_NUMBER
    3 = DETAIL.USAGE_CLASS
    4 = DETAIL.ASS_GSMW_EXT.CALL_REFERENCE

  2. Add 2 new fields under FCT_DuplicateCheck as per Business requirement:
    5 = DETAIL.ASS_GPRS_EXT.PORT_NUMBER
    6 = DETAIL.CHARGING_START_TIMESTAMP

     

Actual result:
==========
After these new changes deployed, FCT_DuplicateCheck is not rejecting a duplicate CDR; instead, the duplicate CDR's are getting rated and loaded into DB.

Expected result:
============
DuplicateCheck module should consider the two new fields added and at the same time be backward compatible so that it can validate against the old data processed with 4 fields and reject the duplicate CDR.



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.