Orders Fallout(on subsequent transactions update/usage) when a particular transaction failed and customer was in locked state in ECE
(Doc ID 2694697.1)
Last updated on DECEMBER 04, 2023
Applies to:Oracle Communications BRM - Elastic Charging Engine - Version 220.127.116.11.0 and later
Information in this document applies to any platform.
Billing and Revenue Management(BRM) received a multiple fulfill billing request to disconnect services on the specific account. In this case there is one CUST_SET_STATUS to disconnect say play_1 service and at next second there is another call to disconnect a Voice over IP(VoIP) service.
So here, the multiple transaction on same account is having problem and the sequence are detailed below:
1) For the first transaction to cancel the Play_xyz service, The ECE_PUBLISH_EVENT is invoked at Jun 16, 2020 02:48:02.890640000 IST.
2) The ECE_PUBLISH_EVENT received a response from ECE after 30 Seconds (may be a timeout), which is at Jun 16, 2020 02:48:32.895854000 IST.
In the meantime, there is another transaction on the same account to cancel VoIP service and which has failed with “Customer is In Transaction :: Retry required”. Because for this transaction, The ECE_PUBLISH_EVENT has happened .
Request sent to Elastic Charging Engine(ECE) : Jun 16, 2020 02:48:03.128166000 IST.
Failed Response received : Jun 16, 2020 02:48:03.483482000 IST.
Issues when the processing time is high during update Request.
In this case, the second transaction failed with status as “CUSTOMER_IN_TRANSATION”, due to ongoing update request transaction on the same account.
There were fallouts(on subsequent transactions update/usage) when a particular transaction failed and customer was in locked state in ECE.
Impact: This is resulting in order fallout's and issues in any other BRM to ECE transaction.
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