In Delayed Billing Case The Custom Usage Items Not Getting Created For The First Bill (Doc ID 752974.1)

Last updated on SEPTEMBER 26, 2016

Applies to:

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

Symptoms

During Account Creation, all the usage items related to that account are pre-created in item_t table with bill poid and next bill poid respectively with that account's billinfo. (As we use delayed billing). When we observe the database the two items of same poid type is created to the next bill and the first bill is not having any usage items. Exception is only one usage item (item type item/datah/intldna) that is correctly created.

Steps To Reproduce:

Set delay billing to 8 days
1. Create an account on May 11, and purchase Plan 1 and the billing cycle of the first cycle is May 11 to June 11.
2. Move pin virtual time to June 11 0500am and purchase a new plan (/service/ldap), with a new service in customer center
3. Change the pin virtual time to June 19th 1200
4. Run the pin_bill_day
5. The bill for May 11 - June 11 will be released, but it will include the /service/ldap which is not expected to have in the first bill, although it do not charge any price in bill. It can be seen in Customer center -> Balance tab-> Bill Details page.


Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms