Need To Consider Credit Limit During Event Based Charging(Stop Accounting)
Last updated on SEPTEMBER 15, 2016
Applies to:Oracle Communications Billing and Revenue Management - Version 126.96.36.199.0 to 188.8.131.52.1 [Release 7.3.0 to 7.3.1]
Information in this document applies to any platform.
Checked for relevance on 17-Jan-2014
-- Problem Statement:
During stop accounting BRM does not consider credit limits. This is fine for session events. But
for occurrence events like SMS/Ring tone purchase, the request(direct debit) gets mapped to stop
accounting opcode, which doesn't check for the credit limit. This results in credit exposure.
Created a product without setting "override credit limit" flag And created account using it.This account had a balance of 1 SR and I passed a event which would be charged 2 SR. Ideally this event should be rejected without any balance impact. But it consumed 1 SR and returned rating status 24 (Credit limit exceeded).
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