Custom Bi-annual Event Is Rated As Monthly When Set To Expire In One Cycle
Last updated on SEPTEMBER 26, 2016
Applies to:Oracle Communications Billing and Revenue Management - Version: 188.8.131.52.0 to 184.108.40.206.0
This problem can occur on any platform.
A multiple cycle event (either it's the out of box event, like Quarterly_Cycle_Forward, Annual_Cycle_Forward event , or a custom event like Bi-annual_Cycle_Forward event) is rated as monthly when setting to expire in one cycle at the deal level. When the product is set never to expire it rates correctly. When it is set to expire in one cycle it displays cycle_start_dates and cycle_end_dates as only ONE month.
Steps performed to see this problem:
1. Create a product with an Annual_Cycle_Forward event
2. Attach it to a deal. Modify the deal in "Deal Specification" window, mark the product to expire in ONE CYCLE in the cycle section.
3. Purchase the deal for an account
4. Use event browser, highlight the Cycle_Forward Fee event , View -> Event Details and examine the Cycle_Forward Fees event's cycle_start and cycle_end dates. The interval is only one month instead of one year.
Same problem applies to Bi-annual product.
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