Last updated on SEPTEMBER 21, 2016
Applies to:Oracle Communications Billing and Revenue Management - Version 184.108.40.206.0 to 220.127.116.11.0 [Release 7.3.1]
Information in this document applies to any platform.
***Checked for relevance on 06-Oct-2013***
Disabling auto-triggered billing is not working in case an adjustment is done in the next billing cycle. It is fine for other events like product purchase or session events but in case there is any adjustment in any level account/item/event , the triggered billing is generating bills for the crossed bills cycles. The configuration's done to disable auto triggered billing are
config_billing_delay to 0.
Please specify if this could be disabled for adjustment events.
Steps To Reproduce:
Purchase the product after one billing cycle and applying adjustment on the same date as below:
* customer creation date:-26 Sept. 2009
* product purchase date:-27 Oct. 2009
* Adjustment date:-27 Oct 2009(got billed after this)
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