CMT: Specifying AR_BILLINFO Reference While Creating Non-paying Child Account (Doc ID 2110913.1)

Last updated on MAY 04, 2016

Applies to:

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

Goal

The user is migrating the accounts using the CMT from a legacy system. The following is the scenario and steps:

Using CMT:
Step1: Created dummy Parent account with 2 billinfos.
Step2: Created non-paying child account with 2 billinfos.

Parent xml file :

                           <ABinfo payInfoRefId="200105">
                                             <ACDom>1</ACDom>
                                             <ActgType>I</ActgType>
                                             <ANxt>2015-12-25T01:22:15-07:00</ANxt>
                                             <CrtT>2015-06-10T01:22:15-07:00</CrtT>
                                             <BlWn>1</BlWn>
                                             <BlSgmnt>xxx</BlSgmnt>
                                             <PTyp>xxx</PTyp>
                                             <BISta>xxx</BISta>
                                             <BillStat>xxx</BillStat>
                                             <BillInfoId>Default</BillInfoId>
                              </ABinfo>
                              <ABinfo payInfoRefId="200105">
                                             <ACDom>1</ACDom>
                                             <ActgType>I</ActgType>
                                             <ANxt>2015-12-25T01:22:15-07:00</ANxt>
                                             <CrtT>2015-06-10T01:22:15-07:00</CrtT>
                                             <BlWn>1</BlWn>
                                             <BlSgmnt>xxx</BlSgmnt>
                                             <PTyp>xxx</PTyp>
                                            <BISta>xxx</BISta>
                                             <BillStat>xxx</BillStat>
                                             <BillInfoId>Default</BillInfoId>
                              </ABinfo>

Child xml file :
                              <ABinfo global="true" spnrCnt="1" spnreeCnt="0" elem="1" parentElem="2351813">
                                             <ACDom>01</ACDom>
                                             <ActgType>B</ActgType>
                                             <ANxt>2004-07-26T01:22:15-07:00</ANxt>
                                             <BlWn>1</BlWn>
                                             <BlSgmnt>xxx</BlSgmnt>
                                             <PTyp>xxx</PTyp>
                                             <BISta>xxx</BISta>
                              </ABinfo>
                              <ABinfo global="true" spnrCnt="1" spnreeCnt="0" elem="1" parentElem="2360008">
                                             <ACDom>01</ACDom>
                                             <ActgType>B</ActgType>
                                             <ANxt>2004-07-26T01:22:15-07:00</ANxt>
                                             <BlWn>1</BlWn>
                                             <BlSgmnt>xxx</BlSgmnt>
                                             <PTyp>xxx</PTyp>
                                             <BISta>xxx</BISta>
                              </ABinfo>

pin_cmt -import -file <xxxx.xml> <id>

After the above steps, the parent account got created with two billinfo objects as expected with proper ar_billinfo objects. But the child account is created with two bill info’ s as well and the ar_billinfo objects both are pointing to the first billinfo object of the parent.

For example:

Step1: created dummy Parent account with 2 billinfos.  
           Account_No: Parent
           Billinfo_poid1: 1111,  AR_Billinfo_poid1: 1111
           Billinfo_poid2: 2222,  AR_Billinfo_poid2: 2222
           In this case, both poid_id0 and ar_billinfo_obj_id0 of BILLINFO_T table are same.

Step2: created non-paying child account with 2 billinfos.
           Account_No: Non_Paying_Child
           Parent_account_No: Parent
           Billinfo_poid1: 3333,  AR_Billinfo_poid1: 1111
           Billinfo_poid2: 4444,  AR_Billinfo_poid2: 2222

The above is for the normal account creation observation in the BRM system

In CMT, the actual result is:
Non_Paying_Child, 3333, 1111
Non_Paying_Child, 4444, 1111

The expected result should be:
Billinfo_poid1: 3333,  AR_Billinfo_poid1: 1111
Billinfo_poid2: 4444,  AR_Billinfo_poid2: 2222

 

Solution

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms