Issues with Changing a Group Account for a Policy
(Doc ID 2522720.1)
Last updated on DECEMBER 03, 2019
Applies to:Oracle Health Insurance Enterprise Policy Administration - Version 22.214.171.124.0 and later
Information in this document applies to any platform.
On : 126.96.36.199.2 version, Processing
Three issues have been identified with changing a group account for a policy on release 3.18.3
1) Contract Period end date on a policy changes when saving the change of group account but then is set back to what it originally was during validation.
2) A new collection setting record is created but the previous record end date is not closed off. We have seen this work correctly in 2.17.3
3) When reverting a policy back to a previous version after an error has occurred on the policy, the TEC_IND_LAST_VERSION is not re-set to 'Y' and the policy cannot be found from the application screen.
Workaround: Users will need to manually capture the end date of the policy collection setting when changing the group account (i.e. when a new collection setting is automatically created).
Expected Behavior: When a new collection setting is automatically created after changing the group account, the previous record should have an end date loaded. this will prevent a system error and mitigates the risk of the policy not being found should the user revert the policy to a previous version whilst there is still an error on the policy
GEN-TMVL-011: The "Policy Collection Setting" with start date "01/01/2019" overlaps in time with a "Policy Collection Setting" that has start date "01/10/2017"
Policies will not be able to be retrieved via the application should the users revert back whilst there is an error on the policy
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