Billing Triggered for DOM Changed Account when Pin_cycle_fees Executed (Doc ID 2141581.1)

Last updated on JULY 01, 2016

Applies to:

Oracle Communications Billing and Revenue Management - Version 7.5.0.0.0 to 7.5.0.0.0 [Release 7.5.0]
Information in this document applies to any platform.

Goal

1. Billing is getting triggered for DOM changed account when pin_cycle_fees executed.
    pin_cycle_fees utility is triggering billing for only DOM changed bill profiles even if auto-trigger billing is disabled.
   
    The expectation is that only cycle charges are applied and bills are not generated for these accounts.

    However, for accounts with DOM change, billing is triggered along with cycle charges. For accounts which do not have DOM change, it is only triggering cycle charges.

    Steps to reproduce:

             pin_cycle_fees -regular_cycle_fees -start 04/17/16 -end 04/18/16


2. Please suggest if there is any way to disable billing in this scenario completely.

3. What if one wishes delaying the billing not disabling it, even if cycle charges are getting applied?

Problem is that there can be chances that complete bill run for specific DOM is delayed due to some reason. In this case auto-triggering of the billing may mess-up the complete reconciliation and pre billing process for that DOM.

Solution

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