Last updated on OCTOBER 17, 2016
Applies to:Oracle Communications Billing and Revenue Management - Version 184.108.40.206.0 and later
Information in this document applies to any platform.
On Oracle Communications Billing and Revenue Management (BRM) Applications 220.127.116.11.0 version, Subscription Management, the below problem is observed during Siebel - AIA - BRM Oracle stack implementation.
When the users update the address of the customer from CRM, it leads AIA to call the opcode PCM_OP_CUST_UPDATE_CUSTOMER to modify the address followed by the second opcode PCM_OP_CUST_SET_STATUS. As per AIA calling both opcodes is an OOTB behavior.
Here it is observed that for some accounts with several child non-paying accounts (in this case is 234 child accounts with Pay_type = 10007, and one is in inactive status, the rest are active) , the PCM_OP_CUST_SET_STATUS opcode takes unusually very long time and the session times out AIA and fails to update the address.
This opcode works fine in PS2 environment while it gets hanged in PS14 environment. The exactly same account is tested in both environments and find a difference in behavior.
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