My Oracle Support Banner

Adding New Non-payee Account Under Payee Account Deletes the Existing Child Account From the Group_billing_group_members (Doc ID 2034084.1)

Last updated on NOVEMBER 01, 2023

Applies to:

Oracle Communications Billing and Revenue Management - Version to [Release 7.5.0]
Information in this document applies to any platform.


On : version, Customer Registration

In Production, when creating a new non-payee child account to an existing payee account/hierarchy, the existing child account got deleted from group_billing_members_t table.
This must be something to do with group_t.count and group_billing_members_t.rec_id.  This issue is observed for migrated accounts (through Conversion Management Tool (CMT)) only.

The existing child account should not be deleted when creating new non-payee child account to an existing payee account/hierarchy.

STEPS as observed
1) CMT created child accounts entries in group_billing_members_t table are with rec_id begins 1,2,3,....
2) When creating child account through Customer Center or opcode, the rec_ids will be 1,3,5,7,...

After migration, if new non-payee account is getting created on migrated hierarchy, it is trying to use existing rec_id for the new child and old account is removed from group_billing_members_t table.
The child accounts are moved out from parent account, this results in billing issues.





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

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