My Oracle Support Banner

Billing Batch Behaving Abnormally While Creating Bill For Loan Accounts, Created Duplicate Bills (Doc ID 2597977.1)

Last updated on OCTOBER 15, 2019

Applies to:

Oracle Utilities Customer Care and Billing - Version 2.3.1 and later
Information in this document applies to any platform.

Symptoms

On : CCB 2.3.1 version, BI - Billing

ACTUAL BEHAVIOR
---------------
Billing batch behaving abnormally while creating Bill for loan accounts, created duplicate bills
In production, during Nightly Billing batch ran with a business day in APRIL although a manually completed bill exists but as previous bill was generated manually, there was no bill cycle code, so next bill was generated by billing batch.


EXPECTED BEHAVIOR
-----------------------
For Loan accounts Billing batch does not create a duplicate bill for a bill already generated manually.

STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. Removed Bill after date and Frozen bill segment exist that was created by Billing Batch (Loan Bill segment from March to May)
2. Billing batch (CM-TBIL2) was submitted with business date in APRIL
3. Billing batch didn’t created a new bill and ignored Account id.
  a.During Replication,When trying to bill, billing batch ignored as a Complete bill created by Billing batch (Bill id) already exist and bill cycle code of previous bill matches with current bill cycle code
  b.In production, during Nightly of 16th when Billing batch ran with date in April business day although a manually completed bill exists but as previous bill was generated manually, there was no bill cycle code, so next bill was generated
  by billing batch
4. To bypass above condition, we changed status of Bill to X from backend
5. Billing batch (CM-TBIL2) was submitted with business date in APRIL
6. Billing batch didn’t created a new bill and ignored Account id, due to below condition
  a.During Replication,When trying to bill, billing batch ignored this account as a frozen loan bill segment (Bseg id) already exist as billed for the bill cycle schedule.
  b.In production, during Nightly Billing batch ran with a business day in APRIL although a manually completed bill exists but as previous bill was generated manually, there was no bill cycle code, so next bill was generated
  by billing batch.

Changes

 

Cause

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
Symptoms
Changes
Cause
Solution
References


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