Service's Status Is Not Changed Throughout Lifecycletransition Utility
(Doc ID 2738292.1)
Last updated on DECEMBER 23, 2020
Applies to:Oracle Communications BRM - Elastic Charging Engine - Version 126.96.36.199.0 and later
Information in this document applies to any platform.
In the current scenario (Parent - Child (Service) hierarchy), it was observed that service status is not changed on BRM side throughout the LifeCycleTransition utility.
On the 1st service activation, its status is set to 101 (Installed) and after a successful topup, it should be set to 102 (Active) on both BRM and ECE (Billing and Revenue Management and Elastic Charging Engine).
During the tests, it was observed that service's status is changed on ECE only, but not on BRM.
step 1: Create a Parent account;
step 2: Create a Service (Child) account -> service state is 101 installed;
step 3: Check service state on ECE and BRM -> state is 101;
step 4: Run external topup request -> topup request is success;
step 5: Check service state on ECE -> state is 102;
step 6: Check service state on BRM -> remains 101 installed, even if the balance is updated with the correct top up amount.
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