Issue in Moving an Existing Account to a New Account Heirarchy
(Doc ID 2022737.1)
Last updated on AUGUST 16, 2018
Applies to:Oracle Communications Billing and Revenue Management - Version 220.127.116.11.0 to 18.104.22.168.0 [Release 7.5.0]
Information in this document applies to any platform.
Qn1: There is an issue in moving an existing account to a new Account Hierarchy when both the accounts are residing in different database schemas.
The above scenario can be replicated using Customer Center and also by using opcode "PCM_OP_CUSTCARE_MOVE_ACCT".
There are 2 customer Accounts with the below structure:
Account1 -->Billinfo1 --> Service1(MSISDN along with its own Balance Group).(Lies in Schema 7)
Account2 -->Billinfo2 --> Service2(MSISDN along with its own Balance Group).(Lies in Schema 2)
Try to move account2 in hierarchy under account1 using PCM_OP_CUSTCARE_MOVE_ACCT, and this will throw a TRANS_ALREADY_OPEN error.
Note that this is a Rapid Offer Design and Order Delivery (RODOD) implementation and the opcode is being invoked by Oracle Fusion Middleware ( FMW).
Qn2: What is the alternative mechanism by which one can achieve the desired results?
Qn3: How can one move an account into the new schema? Is there some API or utility to do this?
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