Last updated on SEPTEMBER 19, 2016
Applies to:
Oracle Communications Billing and Revenue Management - Version 7.3.1.0.0 to 7.3.1.0.0 [Release 7.3.1]Information in this document applies to any platform.
Symptoms
As documented, it is default behavior of OBRM that changing the status of the parent account in a hierarchy changes the status of all subordinate accounts and it cannot be prevented.
But, termination (closure) of parent account is not triggering sub-ordinate account termination.
Scenario:
1> Create a parent account.
2> Create a non-paying (subordinate) account under parent account.
3> Suspend the non-paying (subordinate) account manually.
4> Terminate the parent account manually.
Actual Result - Only parent account terminated, but non-paying (subordinate) account is still in suspended state.
Expected Result - Both parent and non-paying (subordinate) accounts should terminate on termination of parent account.
Cause
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