Cycle Interval For Products Are Not Applied Correctly When Backdated. (Doc ID 1549744.1)

Last updated on OCTOBER 13, 2014

Applies to:

Oracle Communications Billing and Revenue Management - Version 7.4.0.0.0 to 7.4.0.1.0 [Release 7.4.0]
Information in this document applies to any platform.

Goal

Customer has customized the time interval for applying cycle forward fees for products in the opcode PCM_OP_SUBSCRIPTION_POL_SPEC_CYCLE_FEE_INTERVAL .

As per requirement, customer have multiple bill cycles and need to set the time interval of the cycle forward fees from 1st -1st of every month. This is irrespective of the DOM even if the DOM is 5th of the month. This customisation is working for normal scenarios but not working for backdated scenarios.

For Example: Lets say on April 1st customer is trying to purchase a product backdated to 25th Jan, then the cycle events are expected to be

25th Jan-1st Feb
1st Feb – 1st March
1st March -1st April

but the actual result is :
25th Jan-5th Feb
5th Feb – 5thMarch
5th March -1st April
 

Solution

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