My Oracle Support Banner

Commsprocessfulfillmentorderbillingaccountlistebf Is Not Propagating the Fault Properly Back to OSM (Doc ID 2773068.1)

Last updated on MAY 21, 2021

Applies to:

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



For the SyncCustomer flow in Application Integration Architecture (AIA) - Order to Cash (O2C) Process Integration Pack (PIP) (version 12.2.1):

  1. Once Siebel or Billing and Revenue Management (BRM) throws any fault, then CommsProcessBillingAccountListEBF BPEL handles the fault, any of the catch fetches the fault and then sends it back to CommsProcessFulfillmentOrderBillingAccountListEBF.
  2. When CommsProcessFulfillmentOrderBillingAccountListEBF receives back the fault in the response, the fault goes to any of the catch blocks. Neither of them are propagating properly the fault, so that ProcessFOBillingAccountListRespOSMCFSCommsJMSProducer pushes the message accordingly to the response queue, back to Order and Service Management (OSM).


Just to add more details, the business flow being executed is the one explained below:

Expected behavior: the fault details and the correlation are replied fine from CommsProcessFulfillmentOrderBillingAccountListEBF to OSM SAF.
So overall, once there is a failure from Siebel or BRM, it is expected that Order and Service Management (OSM) receives back the fault so that it will be analyzed there.


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.