You are here: Configuration > Funds > ReassignAllocations Rule

Oracle® Insurance Rules Palette 9.4.1.0 E23637_01

# Reassign Allocations Rule

The ReassignAllocations business rule is used to override existing activity allocations. This is useful when the end user is not allowed to select allocations or with automated activities where the user is not involved in an on-line experience with the activity. Allocation records are created when this business rule is processed. The Allocation records contain the funds the money is moving into or out of.

This should be used in lieu of configuring Allocation elements. Even if allocations tags are configured and selected in an activity, the attached ReassignAllocation business rule's configuration takes precedence and applies money according to the business rule. This situation should be avoided.

The Assignment Type when using ReassignAllocations should be a type that expects allocations to direct the money movement, such as Apply or FullWithdrawal. An assignment type like ApplyByFund is expecting a fund specification and is not appropriate with ReassignAllocations.

This business rule must be attached (overridden) at the transaction level. There is no visual editor in the Rules Palette, so it will need to be configured in XML.

## XML Syntax

<ReassignAllocations>

<From>SELECT SQL statement </From>

<To> SELECT SQL statement</To>

</ReassignAllocations>

Identify where money comes from and where it goes.

- The <From> tag is used to specify an allocation that moves money out of funds. This tag is not necessary when money is always moving into funds. For example, a Premium transaction is always moving into funds and not out of funds.

- The <To> tag is used to specify an allocation that moves money into funds. This tag is not necessary when money is always moving out of funds, such as a withdrawal or surrender.

For both the <From> and the <To> tag, a SELECT SQL is written to load values in creating allocations for the current activity. Three columns must be returned in each SQL: the FundGUID, the AllocationMethodCode, and then, depending on the AllocationMethodCode, either AllocationPercent, AllocationAmount, or AllocationUnits. For each record returned in the SQL statement, an AsAllocation record will be generated for the activity. Any allocations generated by the <From> tag will be treated as money out allocations and will have their allocation (AllocationPercent, AllocationAmount, or AllocationUnits) set as a negative value. Any allocations generated by the <To> tag will be treated as money in and will be positive.

Use this rule to perform either money in or money out. Neither tag is required, but one of the two tags must be used. If money needs to be transferred, then configure both tags.

This rule’s purpose is to set the allocations that will be used in the activity’s Assignment processing. Most Assignment types rely on the activity having a group of AsAllocation records that already exist in order to know how to generate AsValuation records. For example, an Apply Assignment type will create an AsValuation record for each AsAllocation record for the activity. See the Assignment section for more details on how valuation records are created from all Assignment types.

Executing this rule makes any allocation records for the activity inactive. It supersedes any allocations that the activity may already have.

Copyright © 2009, 2011, Oracle and/or its affiliates. All rights reserved. Legal Notices