My Oracle Support Banner

CommunicationsCustomerPartyEBSV2Resequencer will be Terminated for BRM Binding Fault to Release the Blocked Account ID (Doc ID 1596173.1)

Last updated on FEBRUARY 22, 2019

Applies to:

Oracle Communications Order to Cash Integration Pack for Oracle Communications Order and Service Management - Version 11.3 to 11.3 [Release 11.3]
Information in this document applies to any platform.


11.3 Communications Process Integration Pack

Current Behavior
In SyncCustomer Flow, SyncCustomerPartyListBRMCommsProvABCSImpl gets failed when a binding fault/technical error from BRM is received, THEN
   - the response flow will send the fault to CommsProcessBillingAccountListEBF and CommsProcessFulfillmentOrderBillingAccountListEBF and these 2 EBFs are Terminated without any further termination
   - At the same time, as part of Global transaction the rollback fault from SyncCustomerPartyListBRMCommsProvABCSImpl is sent to resequencer mediator CommunicationsCustomerPartyEBSV2Resequencer and will be in Recovery Needed state (pending for manual intervention and allows for a resubmition, BUT EBF is already in terminated state, THUS not allowing to recover successfully)

This behavior leads to associated Account ID(group_id) being in Blocked state

Expected Behavior
There shouldn't be a Account ID(group_id) in Blocked state
  For Binding fault from BRM - All the EBFs and Resequencer should be in terminated State
  For Remote Fault from ProvABCS/BRM - All EBFs in Faulted state and Resequencer in Failed (Recover Needed) state

This behavior will ensure the fault can be handled properly.


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.