Last updated on JUNE 28, 2013
Applies to:Oracle Communications Billing and Revenue Management - Version 18.104.22.168.0 and later
Information in this document applies to any platform.
*** Checked for relevance on 28-June-2013 ***
If we launch the rerating during the delayed billing period, the /event/adjustment and the new /event are not attached to the same /bill, because the effective_t is equal to the current cycle start + 1 second. The effective_t of the /item/adjustment of the /event...fees/cycle_forward is equal to the created_t.
Set delayed billing = 1 day. Account with DOM the 5th of month.
5th of November, one cycle fees (15€) is applied and billed.
5th of December, one cycle fees (15€) is applied.
5th of December at 15:00:00, we launch the rerating until the 5th of November.
The current billing cycle is from the 5th of November to 5th of December.
There is 4 /event generated (2 for rerated the fees of the 5th Nov, 2 for the 5 Dec) :
- for 5th Nov :
1 /event/adjustment ~/item/adjustment with effective_t 5th Nov 00:00:01
1 /event/.../fees/cycle_forward ~/item/adjustment with effective_t 5th Dec 15:00:00
- for the 5 dec : /event/adjustment and /event/../fees/cycle_forward associated to a /item/cycle_forward with effective_t = NULL.
We do the billing on 6th December, on the bill, we have :
- the original /event/.../fees/cycle_forward for the 5th Dec
- the 2 rerated /event associated to the /event of the 5th Dec
- the /event/adjustment for the rerating of the 5th Nov
The /event/.../fees/cycle_forward ~/item/adjustment with effective_t 5th Dec 15:00:00, is not taken in the bill of the 5th Dec (cycle 5th Nov -> 5th Dec)
We will have this missing /event on the bill of the 5th Jan (cycle 5th Dec -> 5th Jan).
This is a defect, as it's not acceptable to have the rerated events split within different bills.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms