Last updated on SEPTEMBER 26, 2016
Applies to:Oracle Communications Billing and Revenue Management - Version 188.8.131.52.0 to 184.108.40.206.0 [Release 7.4.0]
Information in this document applies to any platform.
*** Checked for relevance on 07-11-2015 ***
The sequence PIN_SEQUENCE_TYPE_BILL_NO is not generating continuous sequence for BILL_NO's. The problem happened during the execution of billing for 6002 accounts in production environment. The sequence started in billing process is 7660, it was continuous until 7902, and then the next BILL_NO was 13819 and so on.
The BILL_NO generated must be sequential as it is a requirement.
Is there a parameter that needs to be set on the environment?
Why can this sequence be modified in billing process?
Currently, the /data/sequence PIN_SEQUENCE_TYPE_BILL_NO has 19986. It is correct according to the last bill generated, but this is the second time this problem happened and the user had to correct the BILL_NO manually.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms