Last updated on SEPTEMBER 19, 2016
Applies to:Oracle Communications Billing and Revenue Management - Version: 22.214.171.124.0
Information in this document applies to any platform.
Solution Implemented: When a account is created with a prepaid bill unit, it is assigned the default Billing Segment Id “0” to it. Now, when another bill unit is added to the account, which is a post paid bill unit, Billing Segment 110 is assigned to to it, where Billing Segment 110 is defined for a DOM = 10.
Issue: The existing prepaid bill unit has Billing Segment as 0, and the new post paid billing unit has Billing Segment as 110. Because of this, we are not able to add the new post paid bill unit to this account as it gives an error saying: “Billing Segment Id does not match”.
If this is a product constraint, is there a business reason behind that constraint and what could be an alternative approach to create new bill units with a different DOM?
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