Oracle® XML Configuration Guide Release 9.7.1.0 E51561-01
The ReassignAllocations business rule is used to tell the system what funds to use in conjunction with Assignment. This can be used to apply all money into a defined fund. This is useful when the selection of allocation by the end user should be restricted. An allocation record is created when this 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.
Note:
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 rules configuration
takes precedence and applies money according to the business rule.
ReassignAllocations writes to AsAllocation at the activity processing level. It will also overwrite the presence of the allocation element and any previous allocation records and writes the new records at the point the activity is saved.
Used with transactions like FullSurrender, AutoTransfer (where the money is moved from one fund to another), InitialPremium, etc.
Element/Tag |
Attribute |
Definition |
Element/Attribute Value and Description |
---|---|---|---|
<ReassignAllocations> |
|
The opening and closing tag for the business rule. |
|
<From> |
|
Optional element: A SQL statement that locates the money that is to be moved from
a fund is entered in the This tag is not always necessary as the money is not always moving from
a fund. For example, in an Initial Premium transaction the premium amount is only moving to a fund. It was never established in a fund to be moved from, prior to the transaction. |
Required
element value: |
COLLECTION | Math variable collection of either FundGUID/Percent or FundGUID/Amount value pairs. | ||
ALLOCATIONMETHOD | literal or variable (code value) indicating the allocation method to use. Amount - 02 is the only allowed value. | ||
<To> |
|
Optional element: Used in transactions like FullSurrender, AutoTransfer
and InitialPremium. |
Required
element value: |
LEVEL |
Allocations can be defined at the level of plan, policy, or allocation model. |
Plan | Policy | Model | |
TYPECODE |
Defines the allocation type. |
Literal value Use a TypeCode from AsCodeAllocationType. |
|
MODELNAME |
If the LEVEL is defined as Model, this attribute specifies the Model name. | Literal value | Policy:PolicyField |
<ReassignAllocations>
<From>SELECT AsFund.FundGUID, '01', -1 FROM AsFund
JOIN AsPlanFund ON AsPlanFund.FundGUID = AsFund.FundGUID AND AsFund.FundName='Money Market Fund'
WHERE AsPlanFund.PlanGUID='[Policy:PlanGUID]'</From>
<To LEVEL="Plan" TYPECODE="01"/>
</ReassignAllocations>
<ReassignAllocations>
<From>SELECT AsAllocation.FundGUID, '01',-1 FROM AsAllocation
WHERE AsAllocation.TypeCode = '02' AND AsAllocation.RelatedGUID = '[Policy:PolicyGUID]'</From>
<To LEVEL="Model" MODELNAME="LifeStyle Moderate Portfolio"/>
</ReassignAllocations>
<ReassignAllocations>
<From>SELECT AsAllocation.FundGUID, '01',-1 FROM AsAllocation
WHERE AsAllocation.TypeCode = '02' AND AsAllocation.RelatedGUID = '[Policy:PolicyGUID]'</From>
<To LEVEL="Model" MODELNAME="Policy:StandardModel"/>
</ReassignAllocations>
<ReassignAllocations>
<From>[SQL]</From>
<To LEVEL="[Plan|Policy|Model]" TYPECODE="[literal value]" MODELNAME="[literal value|Policy:PolicyField]"></To>
</ReassignAllocations>
Copyright © 2009, 2013, Oracle and/or its affiliates. All rights reserved. Legal notices.