Cycle Tax Event Associated with Wrong Cycle_tax Item Leading to Corrupted Bill
(Doc ID 2191573.1)
Last updated on AUGUST 16, 2018
Applies to:Oracle Communications Billing and Revenue Management - Version 22.214.171.124.0 to 126.96.36.199.0 [Release 7.5.0]
Information in this document applies to any platform.
On BRM 7.5PS14, migrated from 7.3.1
The testing account has 2 billinfo and several services. During the billing process, the pin_bill_accts attached an old /item/cycle_tax (from the previous cycle) to some of the new /event/billing/cycle/tax events.
From the cm.pinlog, it seems that the op_bill_item_assign (BRM internal PCM_OP_BILL_ITEM_ASSIGN opcode) attached an old /item/cycle_tax to the /event/billing/cycle/tax event instead of creating a new /item/cycle_tax. However, the selected /item object is not related to the same /bill, /billinfo, and /balance_group.
This issue is not happening on the 7.3.1 environment, and a new /item/cycle_tax is always created with correct information.
How and why the internal op_bill_item_assign is selecting an existing /item/cycle_tax instead of creating a new one?
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document