Auto Trigged Billing Concept Is Restricted To Accounting Cycle
Last updated on SEPTEMBER 15, 2016
Applies to:Oracle Communications Billing and Revenue Management - Version 18.104.22.168.0 to 22.214.171.124.0 [Release 7.3.0 to 7.5.0]
Information in this document applies to any platform.
Per documentation, when config_billing_delay=0 (pin.conf in CM and pin_billd folders) and AutoTriggeringLimit=2, if the billing for the previous cycle has not occurred and the billing for the next cycle is due in the next two days, then billing for the previous cycle is auto-triggered within these two days.
The issue here that when the billing cycle is two months and config_billing_delay = 0 & AutoTriggeringLimit = 2, then the billing for previous cycle is auto-triggered during the first of the two months bill cycle instead of being triggered during two days prior to next bill cycle.
Consider following scenario for a clear picture :
- Set config_billing_delay = 0 & AutoTriggeringLimit = 2, which means auto-trigger billing is disabled and overridden by AutoTriggeringLimit = 2.
- 11 Jan : Create account with a two-month billing cycle and DOM = 1. Billing cycle for this account is 11th Jan to 01st March. Lets call it bill_cycle_1.
- 01 Mar : Do not perform billing for the account. This means, it is expected that the billing for bill_cycle_1 should be triggered two days prior to the next bill cycle, i.e., 2 days prior to 01st May.That means, billing for bill_cycle_1 should be triggered during 29th or 30th April.
- 17 Apr : Purchase a deal containing purchase fees for example. Notice that the billing is triggered for bill_cycle_1 while it is expected not to.
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