Last updated on SEPTEMBER 02, 2016
Applies to:Oracle Communications Billing and Revenue Management - Version 126.96.36.199.0 to 188.8.131.52.0 [Release 7.5.0]
Information in this document applies to any platform.
When a subscriber purchases a new Discount for a Cycle Charge, the Billing and Revenue Management (BRM) software generates a "refund" event with a negative balance impact to refund the discounted charge (applied for the first discount) for the rest of the cycle before it calculates the new discount charge for that same period, but taking into account the first and the second Cycle Fee discounts.
This creates an extra - negative - cycle event which does not have any reference to the original event. There is no Out Of the Box (OOB) straightforward way to recover the original event POID from the refund event.
This note is about explaining a possible workaround applicable only in the situation where the refund event is generated following the subscription to a new discount. This workaround will not be applicable to situations where BRM generates a refund event.
Example scenario :
- Create an account
- Create a service
- Purchase a product using: PCM_OP_SUBSCRIPTION_PURCHASE_DEAL, the first Cycle event is created : this is the "original" event
BRM OOB 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.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms