My Oracle Support Banner

Collections is Changing the Billing_state to 1 If Executed For an Account With a Skipped Bill Cycle (Doc ID 2902155.1)

Last updated on JANUARY 10, 2024

Applies to:

Oracle Communications Billing and Revenue Management - Version and later
Information in this document applies to any platform.


The collections process is changing the billing_state to 1 if it is executed for one or more accounts which have one or more skipped bills (billing was not run for one or more months).
For example: An account was billed in August 1st 2022, the billing process was not executed for September 1st. On October 1st, collections process is executed without running billing, the billinfo's billing_state field is being updated to 1 and bills are not generated for the account. Also, the collection actions are not executed.

The expected behavior is that the account remains billing monthly as always. Also, the test done in 7.5 environment shows that the billing_state is not being changed, so all the bills prior to collections run are being generated.

The issue can be reproduced at will with the following steps:
1. Oct 10 - Create account
2. Nov 2 - Execute billing
3. Dec 2 - Execute collections

See that the account enters collections (5 days after due date).
There are 2 collections actions:
a. penalty - 7 days after due date
b. inactivate account 18 days after due date. These actions are not getting executed, billing_status = 1, account = active.
No bill is generated.


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

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