My Oracle Support Banner

Using Event Attributes to Define Impact Categories (Doc ID 2724453.1)

Last updated on NOVEMBER 03, 2020

Applies to:

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

Symptoms

From the document of Using Event Attributes to Define Impact Categories: https://docs.oracle.com/cd/E16754_01/doc.75/e16711/prc_rate_impact_cat.htm#BRMPR566, BRM matches the numbers in the rate plan selector with the telephone numbers. Since only country codes are used, all calls from each country match the numbers in the rate plan selector. For example, ”3372621234” matches ”33.”

Steps tested:
-------------------
0. The impact categories were loaded for each country call.
1. Commit usage product which uses a RPS.
2. Create account.
3. Purchase usage product.
4. Call load_session with the input flist:

Note:
BRM = Billing and Revenue Management.
RATING_STATUS 21 = NO_MATCHING_SELECTOR_DATA.

Changes

 

Cause

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
Symptoms
Changes
Cause
Solution
References


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