My Oracle Support Banner

Release Of Oracle Communications BRM Elastic Charging Engine (ECE) Version 11.3 Patch Set 1 (Doc ID 2181465.1)

Last updated on JULY 23, 2018

Applies to:

Oracle Communications BRM - Elastic Charging Engine - Version 11.3.0.0.0 to 11.3.0.0.0 [Release 11.3.0]
Information in this document applies to any platform.

Details

Oracle Communications Billing and Revenue Management Elastic Charging Engine 11.3 Patch Set 1 (11.3.0.1.0) is released on 12 September 2016.

This announcement lists the enhancements and fixes delivered in Elastic Charging Engine 11.3 Patch Set 1. 

Patch ID: <Patch 24489027>

Note: This patch set works with the following releases:

 

Key Enhancements

Enhanced Notifications

With this patch set,

Also, the following ECE notifications now include operation type and its corresponding sub types to indicate when the notification is triggered –  

 

Streaming of Rated Events

With this patch set, you can stream rated events to an external system with the help of a custom plugin. For more information, see BRM Elastic Charging Engine Implementation Guide.

 

Suspense Handling with BRM Gateway

With this patch set, ECE now supports a suspense queue to collect any failed updates through the BRM Gateway.

 

Offline Processing Enhancements

ECE now supports suspending offline usage charging requests for an account for which the billing has been delayed and triggering billing for the same, so that those usage charging requests can be correctly processing after the billing is complete.

 

Virtual Time Support

ECE with this patch set allows updating the current date and time for testing purposes only.

 

Summary of fixes to customer-reported tickets delivered in 11.3 Patch Set 1:

SR Number

Bug Number

Issues Fixed

3-12189891421

22812011

Concurrent access to the accounts which share the same balance was failing with errors.

3-12545233491

23201547

If you created a custom business event (for example, CustModify), which included a preconfigured business event (for example, ProductModifyEvent), triggering the custom business event was not considering the preconfigured business event.

3-12557104791

23201553

23201556

The ProductPurchaseEvent event was not getting updated properly in ECE.

3-12514667881

23208355

23208356

While updating the customer balances, the Customer Updater failed with errors when decimal value range was encountered.

3-12660130741

23260275

Customer-level discount sharing was failing with errors.

3-12554866671

23289852

When a billing-time discount was configured, the tax calculation for discounting was incorrect.

3-12733546691

23333898

The threshold breach notification data had exponential values for the threshold amount and it was impossible to identify whether the breach was due to fixed or percentage threshold.

3-12523309331

23480353

23480366

When ECE nodes were restarted, the pricing loader was taking a longer time to load data into the ECE cache.

3-12726200401

23482770

ECE was throwing exceptions while rating the events for the accounts for which distribution offers (charge sharing offers) were configured.

3-12702149501

23538076

ECE was considering the quantity (cascading) discount mode for applying discount.

3-12758588241

23554720

Subscribe-Notifications-Requests (SNRs) were not getting generated for voucher top-up.

3-12592944241

23577007

23577011

While processing the update requests, the Customer Updater rejected the events such as AccountStatusUpdate and UpdateServicesEvent with an error.

3-12593681301

23579599

23621595

23621596

When ECE nodes were restarted, some unnecessary metadata, pricing and configuration data were loaded into BRM. This was impacting the product catalog maintained in CRM.

3-10690047251

23593123

23593126

After a telephone number of a subscriber was changed to a new number, if any usage request was received with the new number for a date earlier than the date the telephone number was changed, ECE processed the usage request instead of displaying an error.

3-12647332091

23621579

23621581

When a product was cancelled, an unexpected threshold breach notification was generated.

3-12897304221

23748630

Generation of custom notifications by using the post-charging extension was failing with an error.

3-13094525201

24384621

When partial billing was enabled for an account, the External Manager (EM) Gateway was throwing error at the time of billing.

3-12824633391

24408141

24408148

The EM Gateway was returning an invalid error code for some of the errors.

3-13165129691

24445290

If an account was created first and later the service and product was added to the account, Spending-Limit-Request (SLR) for that account was ignored with an error.

This has been fixed.

3-12557552201

24477811

Active or consumed reservations were not removed even after the specified expiry time.

This has been fixed.

 

 

 

Actions

 

Contacts

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
Details
Actions
Contacts
References

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