Last updated on MARCH 08, 2017
Applies to:Oracle Communications Billing and Revenue Management - Version 188.8.131.52.0 to 184.108.40.206.0 [Release 7.4.0]
Information in this document applies to any platform.
***Checked for relevance on 10-SEP-2014***
Checked for relevance on 08-Mar-2017.
After upgraded to BRM 7.4 PS16, the BRM JCA Adapter on SOA 11g stopped working with custom fields.
NOTE: All OPCODE callers without custom fields worked successful. All these calls with custom fields on SOA 10g worked fine.
The user has followed the workaround as suggested in the <Note 1329651.1> "Problem In BRM JCA Adapter "Org.Xml.Sax.Saxparseexception:Field 'XXX' Not Found In BRM", but it did not help.
The user has recompiled the customfields.jar with BRM JDK and recompiled the source classes with SOA JDK (same JDK version 1.6 on the BRM system and SOA system), but this was still not working.
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