My Oracle Support Banner

JCA Adapter Throws Error If The POID Of Migrated Accounts Has Extra Space (Doc ID 1931848.1)

Last updated on OCTOBER 04, 2023

Applies to:

Oracle Communications Billing and Revenue Management - Version and later
Information in this document applies to any platform.



JCA adapter is throwing errors when an opcode is invoked  on migrated accounts :

Example : When invoking PCM_OP_CUST_SET_STATUS with the following input, below error occurred in JCA:


<PCM_OP_CUST_SET_STATUS_inputFlist xmlns:op="" xmlns:="" xmlns:brm="" xmlns="">
<brm:POID> /account 148449796 0</brm:POID>
<brm:PROGRAM_NAME>Test Integration</brm:PROGRAM_NAME>
<brm:SERVICE_OBJ> /service/test 148449804 0</brm:SERVICE_OBJ>


Error :


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) , while 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?



To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!

In this Document

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.