Service Login Identifier Not Getting Updated In ECE Cache
(Doc ID 2931509.1)
Last updated on MARCH 01, 2023
Applies to:Oracle Communications BRM - Elastic Charging Engine - Version 126.96.36.199.0 and later
Information in this document applies to any platform.
When Service Login Identifier is changed from Billing Care by using REST API [/bcws/webresources/v1.0/services/serviceprofile], it was observed that login is not updated on ECE Cache.
The issue can be reproduced at will with the following steps:
1.Open any account in billingcare:
2.Customize to update profile information .
3.After updating the customize fields, one should be calling one billing care REST API to update service login.
4.Now the issue is, after calling REST API, login identifier get updated in PIN Database(DB) but not in ECE Cache.
The service login identifier should get updated in ECE cache
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