Fm_inv_make_invoice_add_taxes Cores When Multiple Balance Impact For Taxes Occur In The Input Flist (Doc ID 1372871.1)

Last updated on OCTOBER 08, 2024

Applies to:

Symptoms

fm_inv_make_invoice_add_taxes opcode cores in two scenarios:

1. When billed event level dispute is raised including taxes
2. When usage CDR is loaded including taxes (default tax_supplier)

Replication Steps:

SCENARIO 1. Invoicing cores when Billed Event Level Dispute raised:

• Configure flat taxation (say 19.6%) in the taxcodes_map file (say "TAX1") present in sys/cm/.
• Enable the taxation_switch (3) in the cm's pin.conf
• Create a customer with any simple plan that has cycle forward product associated with the taxcode "TAX1" and billing time taxation is enabled
• Load default tax_supplier file
• Bill the customer
• Raise an event level dispute on the billed event .
  Dispute should be including TAX. Do not settle the dispute.
• Run billing for next month
• Run invoicing -- It cores here.

SCENARIO 2: When usage CDRs are also taxed along with cycle and purchase fees:

• Configure flat taxation (say19.6%) in the taxcodes_map file (say "TAX1") present in sys/cm/.
• Enable the taxation_switch (3) in the cm's pin.conf
• Create a customer with any simple plan that has cycle forward product and delayed event session product associated with the taxcode "TAX1" and billing time taxation is enabled
• Load default tax supplier file
• Modify the event_t.ctl file to include the constant TAX_LOCALES
• Make sure the TAX_LOCALES matches the tax supplier configuration
• Load the usage through pin_rel to the DB
• Bill and invoice the customer -- Invoicing cores here
  
  

Changes

Cause

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.