EDRs Discarded Through Custom Iscript are Sent to Suspense Stream Instead of DevNull
Last updated on MARCH 23, 2017
Applies to:Oracle Communications Billing and Revenue Management - Version 18.104.22.168.0 to 22.214.171.124.0 [Release 7.5.0]
Information in this document applies to any platform.
Our network equipment generates CDR files that contain records for home prepaid subscribers, home postpaid subscribers and subscribers roaming on our home network.
Out of these CDR files only records for home postpaid subscribers need to be rated by the batch rating pipeline.
Records for home prepaid subscribers and subscribers roaming on our home network need to be discarded by the batch rating pipeline and should not be loaded as suspended usage.
Records for home prepaid subscribers are identified by looking at the object_cache_type on the subscriber's account in the BRM database.
Records for subscribers roaming on our home network are identified by not finding the subscriber in BRM database.
In order to discard records for home prepaid subscribers and subscribers roaming on our home network we implemented 2 custom iScripts that set a custom warning message on the EDR and sets the DETAIL.DISCARDING field to "1".
We then configured the FCT_Reject module in the batch rating pipeline registry as follows in order to send the EDRs that need to be discarded to the DevNull output stream:
However, with this implementation EDRs that are discarded are still being written into the suspense usage output file and would be loaded into the BRM database by SEL to be recycled.
Why EDRs that are discarded through custom iScripts are still being written into the suspense usage output file while we specified in the registry to send them to the DevNull output stream?
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