DoBenefitSplitChange Attached Rules Do Not Default BenefitUnits To Zero Anymore
(Doc ID 2293337.1)
Last updated on AUGUST 02, 2017
Applies to:Oracle Insurance Policy Administration J2EE - Version 10.2.0.27 and later
Information in this document applies to any platform.
Prior to patch 10.2.0.28, when using DoBenefitSplitChange (Switch mode in AutoTransfer for example), the fixed fund had BenefitUnits = 0.000000
Using patch 10.2.0.28 the same situation gives BenefitsUnits = null
This is problematic since BenefitUnits = null make the Exchange Activity Screen (actually the method that load the ActivityBenefitsplit) to crash when intitiated with the following error:
Caused by: java.lang.NullPointerException
... 54 more
Suggestion is to make sure to default the BenefitUnits to 0 instead of null in the DoBenefitSplitChange attached rules
Tested with 10.2.0.28
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!