Last updated on NOVEMBER 02, 2017
Applies to:Oracle Communications BRM - Elastic Charging Engine - Version 126.96.36.199.0 and later
Information in this document applies to any platform.
Checked for relevance on 2-Nov-2017.
The user has tried implementing the same logic of user data request into pre-rating extension module and there was no profile value in the extension.
The use case was about accessing UDR data in pre-rating extension, for read only. Based on the existence of profile values, the user wanted to manipulate other rating fields, the business use case required to validate profile existence for CALLED_TO number in pre-rating extensions.
Hence, the user needed to retrieve customer and product details of "CALLED_TO" number, there was no need to fetch "CALLED_TO" which info is already present.
The expected logic:
1. get the CALLED_TO from payload
2. post an UDR with "CALLED_TO" as input
3. get the profile name and not the value of "CALLED_TO" account
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