My Oracle Support Banner

Unable to Migrate both Paying and Non-paying Child Accounts in the Same XML through Pin_cmt. (Doc ID 2037970.1)

Last updated on APRIL 20, 2023

Applies to:

Oracle Communications Billing and Revenue Management - Version and later
Information in this document applies to any platform.


On : version, Conversion Manager

On migrating the Child Accounts through pin_cmt, observing below issues:

Case 1:

On giving both paying and non-paying billinfo in Child XML, pin_cmt is throwing a parsing error as it expects parent reference(i.e,parentElem for paying Billinfo) because payParenRef tag is given in the XML.

Error in pin_import:

Case 2:

After making correction as per above case, if parentElem is given for paying Billinfo, then import will happen properly,however it is observed that payinfo_obj_id0 is getting populated as 0 for the two billinfo objects.

Case 3:

The above two cases are about the child xml. When in parent, if try to load a paying (say B1) and non-paying (say B2) billing profiles, we observe that the PAYINFO_OBJ_ID0 is populated in both B1 and B2. However, only B1 should have this entry populated and not B2. The payinfo object of B1 has been populated in B2 as well - which is wrong as it means that one payinfo object has two billing profiles.




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.