My Oracle Support Banner

While Creating New Billing Profile (Bill Unit) We Are Getting Error Billing Segment Id Does Not Match (Doc ID 1085859.1)

Last updated on JUNE 13, 2018

Applies to:

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


Business Requirement: An account should be able to move from prepaid TO POSTPAID BILL UNIT AND VICE VERSA. Also a prepaid bill unit should have the accounting day of month as the date on which it was created and a post paid bill unit should have 10th as accounting day of month.

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?


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.