Fct_Account Is Not Creating Cust_B Data Block If the Called Number Is a Prepaid Subscriber (Doc ID 1990988.1)

Last updated on MAY 02, 2023

Applies to:

Purpose

 On :  7.5.0.6.0 version, Pipeline Manager

An 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 Billing and Revenue Management (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 not creating the CUST_B data block.

STEPS
-----------------------
Here are the steps to reproduce the issue:
1. Configure IFW_ALIAS_MAP to tell the Pipeline to populate both the CUST_A and CUST_B data blocks based on 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 Pipeline for a call between postpaid subscriber and prepaid subscriber.
5. Check that Pipeline populates CUST_A and CUST_B data blocks in the EDR with the postpaid subscriber data and the prepaid subscriber data.

Troubleshooting Steps

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.