My Oracle Support Banner

RerateObj for Backout Events is Missing for Rerated One Time Charge Events (Doc ID 2639681.1)

Last updated on FEBRUARY 24, 2020

Applies to:

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


The issue is that rerateObj for backout events are missing for rerated OTC (one time charge) events while it is expected that rerateObj field for backout events should be populated with the POID (Portal Object Identifier) of the newly generated (rated) event.

Steps to reproduce:

Note: in a simple scenario where the purchase of deal is done on current date (and there is no deferred purchase plus setting dates back to current date), the issue is not present, that is, the rerate_obj_id0 field in the backout event is populated with the POID of the newly created purchase fees event.


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.