Benefit Split Calculations

When Benefit Split is configured, OIPA will calculate the value of the final allocation, which is an allocation element or a merged FinalAllocation element. The final allocation value is written to AsAllocation if it differs from the input specified in the Allocation element.

Important   If existing active Benefit Split records exist when new ones are calculated, then the status of the existing records is changed to Deleted. This is the case anytime a new benefit split record is created (through Calculate General or an attached rule).

Variable Benefit

If the variable benefit is greater than 0 and benefit funds exist for variable parent funds then OIPA calculates each final parent fund (fund type 02) allocation and divides it by the sum of all variable final allocations to determine the variable benefit fund allocation.

The variable benefit fund allocation is multiplied by the variable benefit to determine the variable benefit fund amount.

The sum of the variable benefit amounts must equal the VariableBenefit element value.

All fund unit values will be as of the specified EffectiveDate. If values do not exist for the specified date, then OIPAwill look up the last known unit values. If no unit values exist for the benefit fund, a system error is displayed.

Fixed Benefit

If the fixed benefit is greater than 0 and the fixed benefit fund is configured then OIPA assumes a fixed benefit ration of 100%. The fixed benefit fund allocation is multiplied by the fixed benefit to determine the fixed benefit fund amount.

The sum of the fixed benefit amounts must equal the FixedBenefit element value.

AsBenefitSplit records (type 05) are created by the benefit fund based on relation elements, (AIR, M&E, account codes, etc.). The variable benefit fund amount is divided by the benefit fund unit value (as of the BenefitSplit EffectiveDate) to determine the benefit units. The fixed benefit fund amount is passed directly to BenefitSplit and no benefit units are calculated.

Benefit Split Error Messages

If benefit funds do not exist for all variable parent funds based on relation logic, then a business error message will display.

If the FixedBenefit is greater than 0 and no FixedBenefitFund element exists or it has a null value, then a business error message will display.

If more than one benefit fund is found for each parent then a system error (stack trace) is displayed.

     
Copyright © 2017, Oracle and/or its affiliates. All rights reserved. About Oracle Insurance | Contact Us