Last updated on SEPTEMBER 05, 2013
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.
Issue is clarified that AMT is not considering the billinfos in AR hierarchy during account migration.
Steps to reproduce:
1). Create account1 with BI1 and service1 (BI=Billinfo)
2). Create account2 with BI2 and service2
3). Create account3 with BI3 and BI4 and service 3 and Service4
4). Update account1 to create billinfo relationship as BI1 is parent of BI3 of account3.
5). Update account2 to create billinfo relationship as BI2 is parent of BI4 of account3.
6). Put the migration request for account1
6a). Update account_search config with poid of account1
6b). Create job using the account search config
6c). Enable job with job id generate in step 6b
6d). Start amt controller
6e). Check the job status to confirm the migration is successful
7). Check the list of migrated objects
Expected result: AMT should migrate account2 and account3 and all the objects referenced by account2 and account3
Actual result: Only account1 and its referenced objects are migrated
Note: Service can be any service type(/service/ip) and accounts are created by Customer Center and other activities have been performed using opcode via testnap. It is generic issue, occurs across the system.
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