My Oracle Support Banner

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 and later
Information in this document applies to any platform.


Prior to patch, when using DoBenefitSplitChange (Switch mode in AutoTransfer for example), the fixed fund had BenefitUnits = 0.000000

Using patch 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
  at com.adminserver.pas.uip.ActivityDetailUip.loadActivityBenefitsplit(
  at com.adminserver.pas.uip.ActivityDetailUip.processTransactionChange_aroundBody4(
  at com.adminserver.pas.uip.ActivityDetailUip.processTransactionChange_aroundBody5$advice(
  ... 54 more

Suggestion is to make sure to default the BenefitUnits to 0 instead of null in the DoBenefitSplitChange attached rules

Tested with


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

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.