Incorporation Of Sequence Checking In Recycled Files
Last updated on SEPTEMBER 15, 2016
Applies to:Oracle Communications Billing and Revenue Management - Version 220.127.116.11.0 and later
Information in this document applies to any platform.
This problem can occur on any platform.
The CDRs generated are having a sequence number generated from the switch. This Sequence number is being mapped to HEADER.SEQUENCE_NUMBER field of EDR container. Sequencer check is enabled in the output section of Rating Pipeline so that the rating statistics file wise can be captured in the table IFW_SEQLOG_IN. Now the same statistics is required to be captured for the Recycled CDR file. How can that be achieved. For the Recyled CDR file the HEADER.SEQUENCE_NUMBER value is coming as zero.
-- Steps To Reproduce:
- A Normal CDR file ,say with 1180 records for NM is rated by Rating Pipeline. Some CDR's (say 80) got rejected and redirected to SuspenseCreateOutput stream in SuspenseManager Format.
- The Suspensed CDR's is loaded in the BRM database using the SUSPENSED REL LOADER
- Now on Recycling of this suspensed CDR's the status of the CDR's in the suspensed_usage_t table changes from 0 to 1 indicating that they have been recycled.
- The Recycled file generated is having 0 in HEADER.SEQUENCE_NUMBER field in EDR container.
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