My Oracle Support Banner

ACCOUNTING_OFF Generates A Flushed CDR Considering ActiveReservation Rather Than ConsumedReservation (Doc ID 2116311.1)

Last updated on MARCH 23, 2019

Applies to:

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


On : version, Rating business logic

Steps followed to reproduce issue:

1. Balance cache snapshot before the test run:

2. Processed INITIATE with session id FLUSH_Test03:

a. It created entry in ActiveSession cache with INITIATE operation .
b. It updated Balance cache with {reservedBalance=0.90},{activeReservation=0.90},{consumedReservation=0}

3. Processed UPDATE with same session id :
a. It updated the ActiveSession cache with UPDATE operation
b. It updated Balance cache with reservedBalance=1.80},{activeReservation=0.90},{consumedReservation=0.90}

4. Processed another UPDATE request with same session id and incremented sequence number:
a. It updated the ActiveSession cache with new sequence number
b. It updated Balance cache with reservedBalance=2.70},{activeReservation=0.90},{consumedReservation=1.80}

5. Ran the script to invoke ACCOUNTING_OFF
a. It removed entry from ActiveSession cache for session id FLUSH_Test03:
b. It created a CDR with event_bal_impacts_t of “.9”  this should not be .9, but it should be 2.70
c. It updated the balance cache with “.9” addition to the current balance:


Flush CDR is always getting generated with activeReservation amount and not consumedReservation.




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

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