Validity periods after changing the BDOM is not consistent
(Doc ID 2865953.1)
Last updated on MAY 10, 2022
Applies to:Oracle Communications Billing and Revenue Management - Version 22.214.171.124.0 and later
Information in this document applies to any platform.
Create account [8th Nov] with Billing Day Of Month (BDOM) as 5
Move PVT to 15th Nov and modify BDOM to 20
Expected the balance group aligned
1) 8th Nov to 5th Dec
2) Expected: 5th Dec to 20th Dec [ Actual: 5th Dec to 5th Jan]
Tried to Run Billing on 5th Dec
Below are the sub-balance validities after each step
After account creation on 8th Nov
08-NOV-2021 01:00:00 05-DEC-2021 01:00:00
05-DEC-2021 01:00:00 05-JAN-2022 01:00:00
Move PVT to 15th Nov and modify bdom to 20
ACTG_FUTURE_T will be set to Dec 20
This will take effect from next cycle hence no change to existing MCF's and validities. There is no issue here. It is the product behavior.
Bill run on 5th Dec
05-JAN-2022 01:00:00 20-Jan-2022 01:00:00 = This aligns with the new CF event created and is the right behavior
(currently issue is here, Valid To is getting set to 20-Feb)
Bill run on 20th Dec
20-JAN-2022 01:00:00 20-Feb-2022 01:00:00 = This is current behavior and is the correct behavior.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document