Pin_cmt - Bal_grp_bals_t Not Populated By Pin_cmt Tool In Case Of An Existing Balance.
Last updated on MARCH 06, 2018
Applies to:Oracle Communications Billing and Revenue Management - Version 18.104.22.168.0 and later
Information in this document applies to any platform.
bal_grp_bals_t is not populated by pin_cmt tool in case of an existing balance.
When migrating the balances/subbalances via the pin_cmt application, the tool does not create the bal_grp_bals_t object in case there is already some entry for the particular balance_group. This causes inconsistency between three tables: bal_grp_t -> bal_grp_bals_t -> bal_grp_sub_bals_t.
The infranet.cmt.deleteExistingBalances is set to false, so there is a scenario when some balances already exist under the particular balance_group.
1. Load the account via CMT tool (there are no balances/sub balances at this point)
2. Load balance, sub balance with resource_id = x (correspoding bal_grp_bals_t and bal_grp_sub_bals_t are created successfully)
3. Load balance, sub balance with resource_id = y (only the bal_grp_sub_bals_t is created - the bal_grp_bals_t dat file for sql loader is empty)
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