The Balance State Branch (BSB) Node Exits as "Balance Expired" Erroneously

(Doc ID 1371113.1)

Last updated on NOVEMBER 10, 2011

Applies to:

Oracle Communications Network Charging and Control - Version: 4.4.0 and later   [Release: 4.4 and later ]
Information in this document applies to any platform.

Symptoms

The BSB (Balance State Branch) node in a Control Plan can be used to decide the logic to perform based on the Cash Unit Balances and Wallet Status for a particular CLI.

It is found under the CCS Wallet palette group, if configured, in the ACS Control Plan Editor.  Here is an example of how the node can be configured in the Control Plan:

The BSB node can erroneously take the Balance Expired exit which can lead to incorrect logic being performed.

This article will explain the different causes and either provide solutions or suggest when a solution will be available.

Changes

1). The expireAtMidnightTZ parameter was enabled in the eserv.config file on the VWS' (Voucher and Wallet Servers).

BE.beVWARSExpiry.expireAtMidnightTZ = "NZ"


2). The BSBCheckBalanceTypes parameter was configured to a non-Cash Unit Balance Type for the ACS (Advanced Control Services) Customer which matches the Subscriber being checked on the SLC (Service Logic Controller).

BSBCheckBalanceTypes = [
{
acsCustomerId = 1
balTypeIds = [1,2]
}
]

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms