UsedServiceUnit With ReportingReason=QUOTA_EXHAUSTED Handling

(Doc ID 2378925.1)

Last updated on APRIL 09, 2018

Applies to:

Oracle Communications BRM - Elastic Charging Engine - Version and later
Information in this document applies to any platform.


On : version, Balance Management

In the below scenario,Why ECE interpreted ReportingReasons from CCR.MSCC Update-2 different than from Update-3?
First UsedServiceUnit.ReportingReason=QUOTA_EXHAUSTED(3) looks like it was omitted by ECE but second was treated as Final event it was QUOTA_EXHAUSTED?




Still valid quota 1049600-787980=261620

Update-2 and 3gpp-reporting-reason=3 (Quota Exhausted)

Still valid quota 261620+261620-261620=261620

Update-3 and 3gpp-reporting-reason=3 (Quota Exhausted)



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