My Oracle Support Banner

AIA - Aborted Instance Leaves Inactive Resequencing Groups (Doc ID 2766090.1)

Last updated on MARCH 01, 2022

Applies to:

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


 In Application Integration Architecture (AIA) - Order To Cash (O2C) - Synchronize Fulfillment Order - Billing Account Business Flow, it was observed that in case a business error occurs when interfacing with Billing and Revenue Manager (BRM), then CommsProcessBillingAccountListEBF aborted automatically the instance in the Business Process Execution Language (BPEL) flow (refer to screenshot below).


As a result:
1. Business Flow instances are aborted and cannot be retried/aborted by console:


2. Aborted Instances leave Inactive Resequencing Groups:



The impact of the above is the following:
1. Inactive resequencing groups cannot be cleared because the instance cannot be aborted/retried since it was aborted from Enterprise Business Flow (EBF) code.
2. Because of the inactive resequencing group, subsequent orders on the same account remain running because manual intervention is required on the resequencer.

Qn: What is the procedure to clear the Inactive Resequencing Groups?


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.