Issue With AssignFinancialEntry During Cycle Processing.
(Doc ID 2749370.1)
Last updated on FEBRUARY 05, 2021
Applies to:Oracle Insurance Policy Administration J2EE - Version 18.104.22.168 and later
Information in this document applies to any platform.
On : 22.214.171.124 version, MICC Transfer to TSC
Issue with AssignFinancialEntry during Cycle Processing. When cycle processes activities that use the AssignFinancialEntry element when it is building the AsFinancialEntry records it sometimes does not use the correct REMOVEDFROMFINANCIALENTRYGUID, this happens both when cycle is running in DEV and PROD mode. The issue is the REMOVEDFROMFINANCIALENTRYGUID that is being used in some entries does not link to the same policy where the money is being removed from, i.e. The ActivityGUID and the EntityGUID (PolicyGUID for us) do to link to the same policy. This issue happens with every time cycle process activities that use AssignFinancialEntry but it does not always happen on the same policys every time. if you process an Activity that uses AssignFinancialEntry from the OIPA UI it build the DB records correctly.
When cycle processes activities that use AssignFinancialEntry it correctly builds the AsFinancialEntry records.
The issue can be reproduced at will with the following steps:
1) Advance the system date to May 30th, 2020 currently April 28th 2020
2) Process Policy level cycle in either DEV or PROD mode
2a) Note: modified the asc_PopulatePolicyCycle to only process policies where Systematic Withdrawals happen to narrow down the scope of what is processed.
3) After you processes cycle you can run the attached query as well, it will identify all the activities where the described issue has occurred. The query at the bottom of the file can be used to get the PolicyNumber from the first query to show the mismatch.
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