Oracle® Rules Palette Release 9.1.0.0.0 E15811-01

# Reassign Allocations Rule

The ReassignAllocations business rule can be used to apply all money into a defined fund. This is useful when you don’t want the OIPA user to select any allocations. An allocation record is created when this business rule is processed. The Allocation record contains the fund the money is moving into. This business rule can also be used to pull all money from a specified fund into another fund.

This should be used in lieu of configuring any 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.

The Assignment Type when using ReassignAllocations should be a type that moves an entire amount of money such as Apply or FullWithdrawal. An assignment type like ApplyByFund is expecting fund allocations.

You will attach (override) this business rule at the transaction level to use it. There is no visual editor in the Rules Palette, so you will need to configure using XML.

XML Syntax

<ReassignAllocations>

<From>SELECT SQL statement </From>

<To> SELECT SQL statement</To>

</ReassignAllocations>

You will identify where money comes from and where it goes.

- In the <From> tag enter a SQL statement that locates money that is to be moved from a fund. This tag is only necessary when money is moving from a fund. For example, in an Initial Premium transaction the premium amount is only moving to a fund so it will not have a <From> tag.

- In the <To> tag enter a SQL statement that money should be moved into.

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. Neither tag is required, so you can use this rule to perform either money in or money out. If you need to transfer money, 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 is created from all Assignment types.