FCT_Account Is Not Creating CUST_B Data Block If The Called Number Is A Prepaid Subscriber
(Doc ID 1990988.1)
Last updated on APRIL 01, 2019
Applies to:Oracle Communications Billing and Revenue Management - Version 184.108.40.206.0 and later
Information in this document applies to any platform.
On : 220.127.116.11.0 version, Pipeline Manager
The user has a specific Rating rules for calls between 2 subscribers.
To apply these specific Rating rules during Batch Rating, the user leverages the FCT_Account module to populate the CUST_B data block if the called number is a subscriber found in the BRM database and then have a custom iRule to populate a specific USAGE_CLASS value used in Usage Scenario Mapping if the CUST_B data block is populated.
This customization works fine if the called number is a postpaid subscriber but not if it is a prepaid subscriber.
In Batch Rating Pipeline, when processing a CDR with called number corresponding to a prepaid subscriber, the FCT_Account module does not create the CUST_B data block. The account dump created by passing the semaphore dump_portal_act_data.reg contains the prepaid subscribers details, which proves that the data is accessible by the Pipeline, but the FCT_Account is not identifying the prepaid subscriber that exists in BRM database and so not creating the CUST_B data block.
Here are the steps to reproduce the issue:
1. Configure the IFW_ALIAS_MAP to tell the Pipeline to populate both the CUST_A and CUST_B data blocks based on the A_NUMBER and B_NUMBER.
2. Create a postpaid subscriber (OBJECT_CACHE_TYPE = 2)
3. Create a prepaid subscriber (OBJECT_CACHE_TYPE = 1)
4. Process a CDR through the Pipeline for a call between the postpaid subscriber and prepaid subscriber
5. Check that the Pipeline populates the CUST_A and CUST_B data blocks in the EDR with the postpaid subscriber data and the prepaid subscriber data.
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