Last updated on AUGUST 04, 2017
Applies to:Oracle Insurance Policy Administration J2EE - Version 10.1.2.0 and later
Information in this document applies to any platform.
On : 10.1.2.11 version, Activity
Users have a case where there is a pending "Termination" activity on a policy and another pending "MoneyIn" activity on a Group Customer.
When processing the MoneyIn activity on the GroupCustomer, another activity is spawned using activity sequencing with processImmediate = "Yes" (ApplyEmployerBilledplanPremium)
However, since there is already a pending Termination activity on the policy, it tries to process the pending Termination activity first which is correct.
The issue occurs when it finishes processing the Termination and doesn't attempt to process the ApplyEmployerBilledPlanPremium.
Users looked through the AsActivitySequenceTask table and found the ErrorXML that tells us that both sequences have trouble acquiring the lock.
The assumption is that they are competing somehow and not letting the other one go through.
Finally, the processing finishes but The MoneyIn on the Account is in ActivitySequenceError status (72),
so is the Termination on the Policy but the ApplyEmployerBilledPlanPremium is still in status code 02 (AsActivity table).
Activities using activity sequence should completely process regardless of competing pending activities
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