BRM Does Not Calculate Refund For A Charge Event Which Corresponds To Rate Change Period
Last updated on AUGUST 24, 2016
Applies to:Oracle Communications Billing and Revenue Management - Version 126.96.36.199.0 and later
Information in this document applies to any platform.
1.Issue occurs for a MRC product with multiple rate tiers for change in rate (For e.g.A deal having $0.0 till 30/3/2015 and from 31/3/2015 a rate of $30.00)
2.When backdated purchase is performed after the rate change date and with purchase effective date prior to rate change date (for e.g. for D000355 purchase on 04-Apr-2015 with effective date as 04-Mar-2015).
3.The charge event generated for rate change period has a flag set as 8389888 (i.e. 0x800500 which is 0x800000 + 0x500 i.e. PIN_RATE_FLG_RATE_CHG + 0x500).
4.Now during backdated cancellation with effective date prior to rate change date, BRM is not generating the refund event for the charged event which corresponds to rate change period (i.e. the event mentioned above). in this context , the backdated cancellation was effective from 04-Mar-2015.
5.It was found that during cancellation BRM executes a search to get charged events eligible for refund using a search flist which is not considering events having cycle flag set as 8389888.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms