Adding New Fields Under FCT_DuplicateCheck Is Not Validating With Old Data In IFW_DUPLICATECHECK_* Tables
Last updated on JULY 28, 2016
Applies to:Oracle Communications Billing and Revenue Management - Version 184.108.40.206.0 to 220.127.116.11.0 [Release 7.4.0 to 7.5.0]
Information in this document applies to any platform.
On : 18.104.22.168.0 version, Pipeline Manager
Adding new Fields under FCT_Duplicatecheck is not validating with old data in IFW_DUPLICATECHECK_* tables
- Cust had 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
- Added 2 new fields under FCT_DuplicateCheck as per Business requirement.
5 = DETAIL.ASS_GPRS_EXT.PORT_NUMBER
6 = DETAIL.CHARGING_START_TIMESTAMP
- Observation : After these new changes were deployed, FCT_DuplicateCheck is not rejecting a duplicate CDR as expected, instead the duplicate CDR's are getting rated and loaded into DB.
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
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