Why Insert Into EVENT_BILLING_TAX_CYCLES_T Causes Billing Incomplete

(Doc ID 1057343.1)

Last updated on SEPTEMBER 26, 2016

Applies to:

Oracle Communications Billing and Revenue Management - Version to [Release 7.3.1]
Information in this document applies to any platform.
***Checked for relevance on 01-Apr-2013***
Checked for relevance on 8-Jun-2015.


When the user runs billing against a production size DB, they are not able to get billing to complete. They noticed that the following query seems to be impacting performance very heavily:

INSERT INTO event_billing_tax_cycles_t
  (start_t, end_t, currency, bill_vat, bill_obj_db,
  bill_obj_id0, bill_obj_type, bill_obj_rev, rec_id, obj_id0 )
  (:start_t, :end_t, :currency, :bill_vat, :bill_obj_db,
  :bill_obj_id0, :bill_obj_type, :bill_obj_rev, :rec_id, :obj_id0 )

If the user switch the following entry in the cm pin.conf, to not apply taxes, billing runs fine:

billing runs fine.

# taxation_switch
# Specifies whether taxation should be enabled/disabled in Portal.
# 0 - Taxation is disabled
# 1 - Enable real-time taxation
# 2 - Enable cycle-time taxation
# 3 - (Default) Enable both real and cycle time taxation
# Note: Disabling taxation will disable the following entries:
# tax_valid - Address and VAT validation
# tax_return_loglevel - Specify how messages from tax engine are logged
# tax_return_juris - Specify if taxes should be summarized by juris level
# include_zero_tax - Include zero tax amounts into event's tax juris
# cycle_tax_interval - Specify if subords' taxes are rolled to parent
- fm_bill taxation_switch 0


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