My Oracle Support Banner

Billinfo Object at Service Level is Not Correctly Mapped on Importing Through CMT (Doc ID 1683478.1)

Last updated on MARCH 13, 2019

Applies to:

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


If for an account there are multiple services and Billinfo objects created at service level, as per below example:

1 billinfo object at account level
3 billinfo objects at service level

ar_billinfo_obj_id0 and parent_billinfo_obj_id0 fields for the service level object will hold the value of billinfo.poid_id0 of the account_level object.

This is working fine when the file loaded is for a few accounts. However, when we load the file having accounts in bulk (eg: more than 500 accounts), the billinfo object at the service level does not map the ar_billinfo_obj_id0 and parent_billinfo_obj_id0 fields correctly. Some random number is mapped in this field instead.




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.