Error Spawning Client Activities by Policy Activities if Spawn Date = Eff. Date of Policy Activity
(Doc ID 2465897.1)
Last updated on SEPTEMBER 20, 2019
Applies to:Oracle Insurance Policy Administration J2EE - Version 10.2.0.30 and later
Information in this document applies to any platform.
On : 10.2.0.30 version, Activity
There is a problem with the spawning of Client level activities by Policy activities if the Spawn Date is the same as the Activity Effective Date of the Policy activity. There is a message that the Spawned Transaction Effective Date cannot be before the Current Transaction Effective Date.
Unable to change the Processing Order of the Client activity (GroupEFTUpdate) because if a Policy activity spawns this activity and changes the amount for one of the Policies on the Group Bill, would like the Client activity to process before the GroupEFTBankDraft activity (another Client activity) runs and actually debits the bank account for the money. If changed the Processing Order of GroupEFTUpdate to be later than any of the Policy activities that spawn it, it would then also be later than GroupEFTBankDraft, which is one of the last activities in terms of Processing Order (on purpose).
As in V8, a Policy level activity should be able to spawn a Client level activity on the same date. The code should take into account not only the Effective Date and Processing Order but also the parent entity of the activity.
Prevents Policy activities (such as Underwriting Change or Anniversary) which can change the amount of the Premium on a policy from being able to update the Premium amount in AsListBillField. This can result in an incorrect List Bill being generated or an incorrect amount being debited in the case of a Group EFT client.
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