Brm 7.3.1: Cmt Does Not Create Multiple Billinfo Objects
(Doc ID 1258655.1)
Last updated on FEBRUARY 03, 2019
Applies to:Oracle Communications Billing and Revenue Management - Version 126.96.36.199.0 and later
Information in this document applies to any platform.
Checked for relevance on 19-July-2012
CMT does not allow associating service balances with different /billinfo objects. All service balances are associated with the default billinfo object that belongs to the /account object.
In some use cases, accounts must have multiple balance groups so that different balances can be linked to different bills.
Also, One should be able to associate each balance group with a different /billinfo object, for example, when a customer decides to pay for those services by credit card instead of invoice.
Each /billinfo may also have one different /payinfo object related to it.
CMT does not allow doing this, which is not compatible with the BRM 7.3.1 data model.
To conclude CMT must permit creating:
- multiple /billinfo objects
- link between one /balance_group object and its correspondent /billinfo object
- link between one /billinfo object and its correspondent /payinfo object
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