Last updated on MAY 13, 2016
Applies to:Oracle Communications Billing and Revenue Management - Version 188.8.131.52.0 to 184.108.40.206.0 [Release 7.4.0 to 7.5.0]
Information in this document applies to any platform.
JCA adapter is throwing errors when an opcode is invoked on a migrated accounts:
<PCM_OP_CUST_SET_STATUS_inputFlist xmlns:op="http://www.portal.com/schemas/BusinessOpcodes" xmlns:="http://xmlns.oracle.com/ProcessFulfillmentOrderBillingBRMCommsSubprocess" xmlns:brm="http://xmlns.oracle.com/BRM/schemas/BusinessOpcodes" xmlns="http://xmlns.oracle.com/BRM/schemas/BusinessOpcodes">
<brm:POID>0.0.0.1 /account 148449796 0</brm:POID>
<brm:SERVICE_OBJ>0.0.0.1 /service/test 148449804 0</brm:SERVICE_OBJ>
Exception occured when binding was invoked.
Exception occured during invocation of JCA binding: "JCA Binding execute of Reference operation 'PCM_OP_CUST_SET_STATUS' failed due to: Error calling opcode: PCM_OP_CUST_SET_STATUS, exception execOpcode.
The opcode invocation fails within the JCA adapter and it never reaches the BRM Connection Manager.
This issue is happening only for accounts migrated through conversion manager(CMT) , invoking opcode from JCA on a newly created account is working fine.
One observation is that , for all the migrated accounts the POID contains extra spaces between its subfields.
Also, if the above input data is used in a testnap and invoking the same opcode is working fine in testnap.
Is this a limitation in JCA adapter that extra spaces on POID field not allowed?
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