Rerating Uses Wrong Event Quantity
(Doc ID 2616233.1)
Last updated on DECEMBER 06, 2019
Applies to:Oracle Communications BRM - Elastic Charging Engine - Version 18.104.22.168.0 and later
Information in this document applies to any platform.
During the rerating for a data event, it was observed that the final charges for data usage is incorrect as the rerating process looks for BYTES-UP-LINK instead of NetQuantity, while it is expected that after rerating the new charges should be based on NetQuantity and produce correct charges.
This discrepancy was observed in following two test scenarios:
- Session updated with 10 MB and terminated with 0 MB
In this case the bytes-up-link is 0 MB and net-quantity is 10 MB, and while rerating, as it is looking for bytes-up-link, only back-out events are generated and the new rerated events are not generated.
- Session updated with 10 MB and terminated with 10 MB
In this case the bytes-up-link is 10 MB and net quantity is 20 MB, and while rerating, as it is looking for bytes-up-link, rerating is performed for 10 MB instead of 20 MB.
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