My Oracle Support Banner

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

Last updated on SEPTEMBER 15, 2020

Applies to:

Oracle Communications Billing and Revenue Management - Version 7.5.0.0.0 and later
Information in this document applies to any platform.

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

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
Purpose
Troubleshooting Steps
 Currently, this DisableRatingProductCheck registry entry commented out in the user's registry. What is the default value for this entry?
Would setting the DisableRatingProductCheck entry to TRUE help in any way achieving the behavior we are looking for?
 
What could be the possible effects of setting the DisableRatingProductCheck registry entry to TRUE?
 
In order to make the postpaid subscriber (in case of CUST_A) not to have any product associated to the event type /event/delayed/session/telco/gsm/abc_voice, the user has set the status of the product that is associated with delayed usage event type to inactive in PURCHASED_PRODUCT_T and the registry parameter DisableRatingProductCheck to TRUE and processed a batch usage CDR.
FCT_Account has not raised any error and also created CUSTOMER_DATA block for the A_NUMBER with out PURCHASED_PRODUCTS information.
It is the FCT_PreRating that raised the error "ERR_ASS_CBD_NOT_FOUND". Is it correct behavior?
References


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