Cycle Period Split Upon Rate Change Due To Date Range Validity (Doc ID 2507202.1)

Last updated on AUGUST 23, 2024

Applies to:

Goal

A product with a rate plan that has a date range rate tier as below:

 Tier 1: From 0 to 01/03/2018 : 58.06 Euros ( DD/MM/YYYY)
 Tier 2: From 01/03/2018 to 0: 60.08 Euros ( DD/MM/YYYY)

 Scenario:
 1. On 21/01/2018, a subscriber purchases a cycle forward product linked to the rate plan above with Billing Day of Month 21.
 2. On 21/02/2018, Billing is performed.

 Output:

 The cycle forward fee for period 21/02/2018 to 21/03/2018 is split into 2 periods as shown below:
 21/02/2018 to 01/03/2018: 58.06 Euros * (8/30 days) = 15.48
 01/03/2018 to 21/03/2018: 58.06 Euros * (20/30 days) = 38.71

From the above, the period is split into 2 distinct periods due to the rate change. However, both apply the same price (58.06) due to the end date of both events being 21/02/2018. This results in the final charge being 54.19, but the expected charge is 58.06. The split is done inside fm_subscription_cycle_utils.c due to the config of the rateplan. However, since default settings for charging of the event is used, the event end date should be considered, which is = start date = 21/2.

1. Why is this split happening since both impacts apply the same rate?
2. How can one eliminate this split from happening?
 

Solution

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.