Duplicate Check Does Not Work While Recycling Suspended EDR
(Doc ID 1063882.1)
Last updated on MARCH 14, 2023
Applies to:Oracle Communications Billing and Revenue Management - Version 220.127.116.11.0 and later
Information in this document applies to any platform.
Duplicate check functional module is not working while recycling the suspended EDR. Consider the following scenario where the issue can be reproduced :
1. Process an EDR with value 'AAA' in DETAIL.A_NUMBER (which is the search key in FCT_DuplicateCheck module) and '1234' as timestamp. EDR was processed successfully and loaded in DB.
2. Process an EDR with a value 'XYZ' in DETAIL.A_NUMBER and '1234' as timestamp. This file got suspended as XYZ is not a valid customer login. Load the suspended file using pin_rel.
3. In Suspense Management Center , edit the event mentioned in step 2 to make DETAIL.A_NUMBER as 'AAA' and recycle it. This EDR gets processed and a rated output file was generated.
Expected : As duplicate check was configured in this rating pipeline as the second function plugin after FCT_PreSuspense, one would expect that this EDR should get rejected as duplicate.
Following is the configuration in DuplicateCheck module used in the above example;
ModuleName = FCT_DuplicateCheck
SearchKey = DETAIL.A_NUMBER
1 = DETAIL.B_NUMBER
2 = DETAIL.CHAIN_REFERENCE
3 = DETAIL.BASIC_SERVICE
} # End of Fields
} # End of Module
} # End of DuplicateCheck
4. Now process an EDR mentioned in Step 1 again, with the same A_Number and timestamp 1234 ; it is getting rejected as Duplicate, as expected.
Note : A_NUMBER was just an example, but one could have other business cases where they might require the duplicate check to work on such recycled EDRs.
How can we achieve this requirement ?
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