Suspend EDRs Whole File Forcibly
(Doc ID 2665440.1)
Last updated on MAY 13, 2020
Applies to:Oracle Communications Billing and Revenue Management - Version 220.127.116.11.0 and later
Information in this document applies to any platform.
In a CDR file, if a record gets suspended among the records having a common identifier, all the remaining records in that file should also be suspended forcibly.
Below is the sample of CDR file format:
CDR1: Account1|Y|Z|REC4 -> Valid record and would be rated successfully.
CDR2: Account11|Y1|Z1|REC4-> Valid record and would be rated successfully.
CDR3: Account2|Y2|Z2|REC1 -> Valid record and would be rated successfully.
CDR4: Account3|Y3|Z3|REC2 -> Valid record and would be rated successfully.
CDR5: Account1|Y4|Z4|REC4 -> Invalid record and would be suspended by FCT modules in the pipeline.
The requirement is, if the CDR with field value REC4 is suspended due to invalid customer data, for example, CDR5 gets suspended, the other CDRs (CDR1, CDR2) with field value REC4 should also be suspended forcibly, but not the other CDRs (CDR3, CDR4) that are not having the field value REC4.
In the rating Pipeline, ALL_RATE_ONLINE1, the user has added FCT_BatchSuspense as the first module and processed a CDR file with multiple records and one of them gets suspended by FCT_MainRating. It is observed that only one record is suspended, not the entire file.
Oracle Communications Billing and Revenue Management (BRM) documentation does not have enough information about the functionality of this module.
Please suggest how to implement this requirement and share example where and how to use the fct_batch_suspense..
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