Last updated on JULY 02, 2014
Applies to:Oracle Communications Billing and Revenue Management - Version 184.108.40.206.0 to 220.127.116.11.0 [Release 7.5.0]
Information in this document applies to any platform.
During CMT migration, a billinfo object is created both for account level and service level. Hence, there is a billinfo object for every service record.
The billinfo_t.ar_billinfo_obj_id0 and billinfo_t.parent_billinfo_obj_id0 for service record will be stamped with account level billinfo poid. This is working as expected.
However, the bill_t table is not correctly updated after the CMT import step. The bill_t.ar_billinfo_obj_id0 and bill_t.parent_billinfo_obj_id0 for service record must be stamped with account level billinfo poid, but this is not happening. Insteadn stamping happens with the billinfo_obj_id0 of its own record (i.e. service level billinfo_id0).
Please find the enclosed screenshots.
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