My Oracle Support Banner

Billing Suppressed Account Does Not Use The Custom Sequence,Which Results In Generation Of Duplicate Bill (Doc ID 1529479.1)

Last updated on FEBRUARY 19, 2019

Applies to:

Oracle Communications Billing and Revenue Management - Version to [Release 7.4.0]
Information in this document applies to any platform.


We created a custom sequence ABCD_BILLNO.
The initial header_num of this new sequence is the same as the header_num for OOTB sequence PIN_SEQUENCE_TYPE_BILL_NO.

In fm_bill_pol_spec_billno.c, fm_bill_pol_spec_billno(), we are using this custom sequence to populate the bill_no. Since we have 4 schemas, we are incrementing the sequence by 4 for every bill.

Also, we know that OOTB sequence always gets incremented by one during billing.
So, lets say while run billing once for an account and your starting sequence is say 1000000400 for both sequence.
If you run billing the following values will be there for the custom sequence after billing:

                custom             OOTB
Billing1 : 1000000404: 1000000401
Billing2 : 1000000408: 1000000402
Billing3 : 1000000412: 1000000403
Billing4 : 1000000416: 1000000404 (Lets say this is a suppressed bill).

So, after the 4th billing, there will be two accounts having the same bill_no (1000000404) in the DB (although one bill is not finalized as its suppressed) since the during the billing 4, account never went to the function fm_bill_pol_spec_billno(), as it got suppressed, its bill_no got populated using the OOTB sequence which was at that time 1000000404 (a duplicate) and not the custom sequence.




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.