Last updated on MAY 18, 2015
Applies to:Oracle Communications Billing and Revenue Management - Version 184.108.40.206.0 to 220.127.116.11.0 [Release 7.4.0]
Information in this document applies to any platform.
Towards the end of the parent billing, the bill objects of the subordinates are updated for setting DUE_T, BILL_NO, etc. BRM uses the balance group locking mechanism (or account locking when using less granular locking) whenever an object related to the balance group (or account) is updated.
In this case, the object is /bill. (This consistent mechanism is used in order to NOT allow random objects (bill, service, item, etc.) to be locked in different orders across processes resulting in deadlock scenarios).
Thus, the subordinates are locked during updates to their bill objects. This only happens towards the end of parent billing, but in one customer scenario they have a large number of subordinates as well as some custom operations during the billing, resulting in subordinates getting locked for an extended period of time.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms