My Oracle Support Banner

BRM-ECE Transaction Errors Are Not Handled Properly In RODOD Setup (Doc ID 2583780.1)

Last updated on OCTOBER 26, 2020

Applies to:

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


In a RODOD (Oracle-Rapid Offer Design and Order Delivery) implementation with Elastic Charging Engine (ECE) and Billing and Revenue Management (BRM) that is integrated with Siebel using Oracle Application Integration Architecture (AIA) there is an issue that whenever an error occurs in ECE, BRM is not relaying the error which occurred in ECE, back to AIA (which is required to create fallout and subsequently a trouble ticket in Siebel).

Steps to reproduce:

  1. Create account in RODOD end to end with a discount having validity for 3 months.
  2. Bill the account for 1st month.
  3. Bill the account for 2nd month.
  4. Bill the account for 3rd month.
  5. Bill the account for 4th month (discount is expired at this time).
  6. Cancel the service which has a discount which is active but expired in BRM.
  7. Cancellation of service failed, since discount is not present in Customer cache in ECE (since discount is expired).

    Below is error in ECE log:

  8. There is no fault/error response from BRM to AIA and as a result there is no trouble ticket created in Siebel (AIA will be able to create a trouble ticket whenever there is a fault in transaction).







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.