My Oracle Support Banner

Store Information On Rejected Requests (Doc ID 2387442.1)

Last updated on MARCH 21, 2019

Applies to:

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


On Oracle Communications Elastic Charging Engine(ECE), version, Rating business logic

Actual behavior:

Customer’s Revenue assurance and Quality assurance team require ECE/BRM system to register unsuccessful calls to enforce integrity of processed data.
Session control function requires all rejected usage requests to be logged in order to properly enforce revenue assurance, enable customer service, support service quality efforts.

Current ECE + BRM behavior:

Current implementation does not persist event information for unsuccessful calls. A solution is needed allowing storage of all incoming requests regardless of the rating result; possibly events to be generated not only for success scenarios.
Reason code is registered in current solution for all on-going sessions – what seems to be partially satisfying the requirement for calls failing on update requests.

Expected behavior:

System should register all sessions that are being rejected without successful initialization.




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.