Skip Headers
Oracle® Communications Billing and Revenue Management Upgrade Guide
Release 7.5

E16723-09
Go to Documentation Home
Home
Go to Table of Contents
Contents
Go to Feedback page
Contact Us

Go to previous page
Previous
Go to next page
Next
PDF · Mobi · ePub

12 Notification Event Changes from BRM 7.3.1 to BRM 7.4

This chapter provides upgrade impact information for Oracle Communications Billing and Revenue Management (BRM) 7.3.1 to BRM Release 7.4. It describes the notification event changes that affect your BRM system, and what you must consider when you upgrade from 7.3.1 to 7.4.

For information on planning your upgrade implementation, such as setting up your development and test environments, see "About Upgrading BRM Releases".

Changed Notification Events

Table 12-1 lists all notification events that were modified between BRM 7.3.1 and BRM 7.4.

Table 12-1 Changed Notification Events

Changed Notification Event Description

/event/notification/threshold

The following fields were added to the PIN_FLD_BALANCES substruct:

  • PIN_FLD_CURRENT_BAL: The current balance after the amount was impacted. Applicable only when applying balance impacts.

  • PIN_FLD_CREDIT_FLOOR: The baseline for calculating percentage for threshold triggers. Credit floor does not enforce any limits on current balance.

  • PIN_FLD_CREDIT_LIMIT: The limit for this resource. Current balance cannot exceed this limit unless the current balance is affected by a limit override rate or manually adjusted by a CSR.

  • PIN_FLD_CREDIT_THRESHOLDS_FIXED: A list of separated threshold amounts, in ascending order, to trigger when the resource balance crosses a boundary when the value is increasing.

  • PIN_FLD_EVENT_TYPE: The type of event against which this notification was raised.

  • PIN_FLD_CALLING_NUMBER: The originating phone number of the call. Usually, this is the MSISDN number, but can be different (for example, in a calling card scenario). This is also called the A number.

  • PIN_FLD_CALLED_NUMBER: The destination number of the call. This is also called the B number.

The following fields were added to the PIN_FLD_THRESHOLDS array:

  • PIN_FLD_ALERT_TYPE: The threshold's alert type: Limit (1), or Percent Threshold (2), or Floor (3), or Fixed Thresholds (4).

  • PIN_FLD_REASON: The reason for this breach. It can be (0x01) Upward Breach, or (0x02) Downward Breach, or (0x04) Upward Reset, or (0x08) Downward Reset, or (0x10) Indeterminate.

/event/notification/threshold_below

The following fields were added to the PIN_FLD_BALANCES substruct:

  • PIN_FLD_CURRENT_BAL: The current balance after the amount was impacted. Applicable only when applying balance impacts.

  • PIN_FLD_CREDIT_FLOOR: The baseline for calculating percentage for threshold triggers. The credit floor does not enforce any limits on current balance.

  • PIN_FLD_CREDIT_LIMIT: The limit for this resource. Current balance cannot exceed this limit unless the current balance is affected by a limit override rate or manually adjusted by a CSR.

  • PIN_FLD_CREDIT_THRESHOLDS_FIXED: A list of separated threshold amounts, in ascending order, to trigger when the resource balance crosses a boundary when the value is increasing or decreasing.

  • PIN_FLD_EVENT_TYPE: The type of event against which this notification was raised.

  • PIN_FLD_CALLING_NUMBER: The originating phone number of the call. Usually, this is the MSISDN number, but can be different (for example, in a calling card scenario). This is also called the A number.

  • STRING PIN_FLD_CALLING_NUMBER: The destination number of the call. This is also called the B number.

The following fields were added to the PIN_FLD_THRESHOLDS array:

  • PIN_FLD_ALERT_TYPE: The threshold's alert type: Limit (1), or Percent Threshold (2), or Floor (3), or Fixed Thresholds (4).

  • PIN_FLD_REASON: The reason for this breach: (0x01) Upward Breach, or (0x02) Downward Breach, or (0x04) Upward Reset, or (0x08) Downward Reset, or (0x10) Indeterminate.