Last updated on JUNE 19, 2017
Applies to:Oracle Communications Billing and Revenue Management - Version 22.214.171.124.0 and later
Information in this document applies to any platform.
This article clarifies the below queries about the billing cycle start date and end date used in the invoice processing on Oracle Communications Billing and Revenue Management(BRM), 126.96.36.199.0 versions.
Question 1: Consider the below scenario:
1. Feb19 -> create account DOM 19, purchase cycle forward product, bill now. NOTE: bill 1 has amount of 125.80
2. Mar19 (DOM) -> cycle forward events were generated. NOTE: Bill 2 is not yet generated because of 17-day delayed billing period.
3. Mar20 -> create 1st payment of 125.80
4. check customer center -> payment 125.80 allocated to bill 1 on Mar20
Bill 1 due is now 0.
5. Mar21 -> create 2nd payment 62.90
This is not allocated yet since there is no bill with due (bill 1 has due = 0)
6. Apr5 -> run billing on the delayed billing period
Bill 2 generated.
Bill 2 amount = 62.90
7. check customer center -> payment 62.90 allocated to bill 2 on Apr5 (POST_BILLING)
Bill 2 due is now 0.
Here the issue is that when generating the invoice for bill 2, there is no payment included in the invoice. Checking the "Step Search" used by the invoice process it was found that for bill 2 the range of dates used to look for items to be included in the invoice is from Feb 19 to Mar 19. It seems that it follows the start_t and end_t of the bill.
Question 2: From the search event flist below (used by fm_inv_make_invoice), where does the values of PIN_FLD_CREATED_T in argument 7 and 8 come from?
STEP_SEARCH event search flist:
Question 3: Although the effective_t can be changed by customization, what value range should be used for that, considering that a payment can be done anytime and can be allocated on any bill anytime?
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