Extending the Data Model so that the Refund Event References the Original Event it Refunds
(Doc ID 1643700.1)
Last updated on MARCH 29, 2019
Applies to:Oracle Communications Billing and Revenue Management - Version 18.104.22.168.0 and later
Information in this document applies to any platform.
The Billing and Revenue Management (BRM) application will refund charges in various situations*. When that happens, the BRM software generates a "refund" event, that has a negative balance impact.
*for instance, but not limited to : when a new Discount is purchased, BRM refund the original discount for the remainder of the cycle and calculates the new charges for the new discount)
The following note explains in more detail the one situation where a new Discount is purchased. It also describes a possible workaround that would not require a software fix, but that would not cover any other refund situation:
As of version 7.5 PS8, BRM nowhere references the "original" event from the "refund" event in any field of the event as a storable object.
That information would be useful for instance if one would want - through customization - to remove that refund event and use corrective billing to correct the original event instead. This may be an option to generate a corrective bill instead of showing a refund item on the subscriber's bill. That is only one possible scenario why it would be necessary to recover the original 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