Issue Reading Integer Based Profile Fields from BRM
Last updated on SEPTEMBER 27, 2017
Applies to:Oracle Communications Convergent Charging Controller - Version 6.0.1 and later
Information in this document applies to any platform.
In Oracle Communications Convergent Charging Controller (OC3C) there is an issue when reading integer based profile fields sent by Oracle Communications Billing and Revenue Management (BRM) inside a Control Plan.
As an example we are trying to compare received profile value with "1", as part of a profile branching comparison, but the "1" value is converted to 16777216 before comparison.
When converted into a string value first, the issue is not occurring.
See following debug lines representing the issue:
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