Change Of BDOM Not Working As Expected For Annual Frequency Customers (Doc ID 2186012.1)

Last updated on SEPTEMBER 24, 2023

Applies to:

Goal

On Oracle Communications Billing and Revenue Management (BRM) Applications 7.5.0.0.0 version, Subscription Management, it is observed that Change of BDOM (billing day of month or accounting day of month) is not working as expected for Annual (billing) Frequency customers.

Consider a scenario where a business supports monthly, quarterly, semi-annual and annual billing frequency and all BDOMs. When a customer changes his BDOM, the behavior is different for Monthly and Annual frequency customers.

Test scenario -- Monthly Frequency:

1) Created a customer with parent-Non-paying child hierarchy on 08/17/2016.
2) BILL_WHEN = 1 and ACTG_CYCLE_BDOM = 1 . Current cycle = 08/17/2016 to 09/01/2016 , Next bill cycle = 09/01/2016 to 10/01/2016.
3) Change the BDOM of the customer to 10 from customer center.
4) BILL_WHEN remains same as 1 and ACTG_CYCLE_BDOM = 10.
5) Current cycle remains same as 08/17/2016 to 09/01/2016 and Next bill cycle changes to 09/01/2016 to 10/10/2016.

Test scenario -- Annual Frequency:

1) Created a customer with parent-Non-paying child hierarchy on 08/17/2016.
2) BILL_WHEN = 12 and ACTG_CYCLE_BDOM = 1 . Current cycle = 08/17/2016 to 08/01/2017 , Next bill cycle = 08/01/2017 to 08/01/2018.
3) Change the BDOM of the customer to 12 from customer center.
4) BILL_WHEN remains same as 12 and ACTG_CYCLE_BDOM = 12.
5) Current cycle changes as 08/17/2016 to 08/12/2017 and Next bill cycle changes to 08/12/2017 to 08/12/2018.

The expected behavior is that the current cycle remains the same as in case of Monthly customers and only the next cycle should change.

The default behavior of long and short billing cycles is used and no customization is done to alter the behavior.

Solution

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