Last updated on SEPTEMBER 21, 2016
Applies to:Oracle Communications Billing and Revenue Management - Version: 220.127.116.11.0
Information in this document applies to any platform.
If the product was future dated during the purchase of the product in 6.2SP1 and then upgraded to 7.3.1 the expected PURCHASED_PRODUCT_CYCLE_FEES_T record is generated when cycle_fees is executed on the date specified for product start.
If the product was future dated after the purchase was completed in 6.2SP1 and then upgraded, the PURCHASED_PRODUCT_CYCLE_FEES_T record is not generated until the account is billed.
At time of billing the product generates a cycle_fees record with a charged_from_t field value of the purchased_start_t value. The related charged_to_t field value is populated with the new billing cycle end date. This results in a long billing cycle period for charge calculations of the product involved and means that the product was not billed during the current bill, meaning no charges for that product and it does not appear on the invoice for that billing cycle. The product will bill in the following cycle and generate pro-rated charges for the long billing period defined in the PURCHASED_PRODUCT_CYCLE_FEES_T table.
This does not match the actions of an account which is modified to future start after purchase in the 7.3.1 release.
In 7.3.1 if the product is purchased on the account and then modified to future date, it updates the charged_from_t and charged_to_t field values remain as the actual purchase date of the deal and the current billing cycle end date respectively.
This results in date display on the invoice not matching the actual product active date range.
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