Problems With Service Inactivation Backdated For Cycle Forward Event - Missing Refund
Last updated on SEPTEMBER 26, 2016
Applies to:Oracle Communications Billing and Revenue Management - Version 184.108.40.206.0 to 220.127.116.11.0 [Release 7.2.1 to 7.3.1]
Information in this document applies to any platform.
This problem can occur on any platform.
Checked for relevance on 26-Apr-2012
While testing, found when backdating inactivation of a service there is a portion of the refund for cycle forward event that doesn't have balance impact. This portion of time corresponds to the close bill period.
Steps To Reproduce:
1. Create an account on Jul 4th with effective_t for Apr 10th (backdate creation) and DOM 23
2. Bill it on Jul 4th
3. Inactivate the service with effective_t Jun 20th (still on Jul 4th)
4. Verify that the refund event that goes from Jun 20th to Jun 23rd (DOM) doesn't have balance impact associated
5. Verify that the refund event that takes the complete open period (Jun 23rd to Jul 23rd) is OK
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