Last updated on SEPTEMBER 15, 2016
Applies to:Oracle Communications Billing and Revenue Management - Version 22.214.171.124.0 and later
Information in this document applies to any platform.
***Checked for relevance on 22-May-2014***
We are facing issue in the custom fields that start with PIN_FLD.
For one of our custom Opcodes, we have provided the xsd to AIA team containing the custom fields in input flist. We have custom fields with a name starting with ESN_FLD_xxx as well as PIN_FLD_xxx.
The JCA Adaptor is able to parse the ESN_FLD fields but is not able to parse the PIN_FLD_xxx custom fields and is throwing an error.
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