Logic in BAL_GRP_T_MAPPING_TABLE_T.SQL Script Sets REALTIME_CNTR To 0 During BRM Upgrade From 6.5 To 7.3
Last updated on MARCH 26, 2018
Applies to:Oracle Communications Billing and Revenue Management - Version: 220.127.116.11.0
Information in this document applies to any platform.
Checked for relevance on 09-July-2011
During BRM upgrade from 6.5 to 7.3, the logic in the BAL_GRP_T_MAPPING_TABLE_T.SQL script sets REALTIME_CNTR to 0. REALTIME_CNTR should be set to the max rec_id of the corresponding sub-balances.
The source of the problem is that the REALTIME_CNTR is not aligned with the maximum rec_id of the sub-balances. If REALTIME_CNTR is left set to 0, it is possible that existing sub-balances are overwritten. For example, if a resouce's sub-balance has index 2 before the upgrade. During the upgrade the REALTIME_CNTR is set to 0. So after the upgrade during billing when a new sub-balance is created, it will have index 2 (rec_id = REALTIME_CNTR+2) which will overwrite the existing sub-balance with index 2.
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