WriteDefaultAllocation

Allocations define how money is applied to a policy.  The WriteDefaultAllocation business rule instructs the system to write/copy the default allocations, which are pre-defined funds, to the AsAllocation table for both policy and plan levels.

The allocation specified in this business rule is used if no other allocation instructions are given or if transaction processing dictates that all funds are deposited into a certain fund or set of funds.

This business rule allows an activity to insert/update default allocation records.  It is also used to control and recognize only positive allocations and ignore the negative allocations for all the source funds.  

The effective date column can be set in AsAllocation table via this business rule when the new allocation records are written/copied.  

This business rule can be used with any transaction (like RebalanceStart, InitialPremium, SystematicWithdrawalStart, etc.) that performs fund allocations.

It is customary to establish a level default allocation.  

WriteDefaultAllocation Elements/Attributes
Element/Tag Attribute Definition Element/Attribute Value and Description

<WriteDefaultAllocation>

The opening and closing tag of the WriteDefaultAllocation business rule.

 

 

 

 

IF

Optional attribute; ="String"

Defines a condition to determine whether to execute this business rule. If the condition is satisfied, an allocation record is created as specified in the configuration; otherwise no record is created.

Note: If the IF condition is specified in both the <Allocation> and <WriteDefaultAllocation>tags, the condition in the <Allocation> tag takes precedence.

<Allocation>

Required/ Repeatable element:

This element is used to define the list of funds that should be available for allocations. Repeated for each Future or Activity Schedule Allocation to be created for the target policy. Refer to the Allocation elements for details about the <Allocation> element and the available options.

 

 

 

IF

Optional attribute: ="String"

Defines a condition to determine whether to execute this business rule. If the condition is satisfied, an allocation record is created as specified in the configuration; otherwise no record is created.

Note: The IF condition in the <Allocation> tag takes precedence over the IF condition in the <WriteDefaultAllocation>tag.

<From>

Required element:

This element is used to specify the level of allocation to which a policy level allocation should be changed.

 

Required Element value:

Activity - Indicates that the activity level allocations should be used to change the policy level allocation.  

 

POSITIVEONLY

Optional attribute:

This attribute determines whether to update Policy or Plan level allocations with both positive and negative allocations of the source funds.

Yes - Indicates that only positive allocations of a Fund should be written to the Policy or Plan level allocations.

No - Indicates turn off functionality. Allocations written for the policy on the AsAllocation table will be for both positive and negative.

<AllocationTypeCode>

 

Required element:

Indicates the target level allocation (Policy) where allocations should be changed.

 

Required Element value:

AllocationTypeCode - Indicates the Allocation Type from AsCodeAllocationType that should be updated with the activity or segment level allocations.

Ex:

01 - Plan Default

02 - Future Allocations (Policy level)

09 - Rebalancing Program

11 - Systematic Withdrawal

14 - DCA Funds

 

TYPE

Optional attribute:

="Policy"/"Plan"/"Program" - This attribute is to provide the capability of storing default allocations other than 02 (Policy default).

Note: If the <Allocation TypeCode> element value is specified as 02 then this TYPE attribute is optional. Otherwise, the TYPE attribute should be present to specify the allocation types other than Policy default allocations.

  ProgramGUID

Optional attribute: when Type="Program". Specifies the ProgramGUID to which the Allocation has to be updated.

MathVarible/Activity Fields(Activity: <FieldName>)

Note: When the TYPE="Program" and if the transaction is linked to a program, then ProgramGUID is not required (it will take the ProgramGUID from context).

 

EFFECTIVEDATE

Optional attribute: ="Field/MathVariable"  

This attribute is used to save the new allocations along with the EffectiveDate in the AsAllocation table. If this attribute is not used, then a null value is stored in the EffectiveDate column of the AsAllocation table.

 

XML Example

<WriteDefaultAllocation>
<From >Activity</From>
<AllocationTypeCode TYPE="Policy">09</AllocationTypeCode>
</WriteDefaultAllocation>

XML Schema

<WriteDefaultAllocation>
<Allocation>
<From POSITIVEONLY="[Yes|No]">[Activity|Segment]</From>
<AllocationTypeCode TYPE="[Plan|Policy|Program]" EFFECTIVEDATE="[MathVariable]" 
ProgramGUID="[MathVariable/Contextvariable]">[AllocationTypeCode]</AllocationTypeCode>
</Allocation>
</WriteDefaultAllocation>

 

 

 

 

 

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