Currency Code Validation
Before writing to the Target Field, OIPA will confirm that the currency code associated with the source value exists in the Currency element of the Target Field. If the Target Field has no defined currency, the default currency for the plan or company is assumed.
Business errors are generated if the Source Currency code is not found in the Currency element of the Target Field, or if the Target Field is not a Money data type.
Configuration Requirements
There are 16 distinct rules and one set of elements affected by currency validation functionality. The affected rules may be broken into the following four categories:
- CopyTo (update existing fields) rules attached to transactions
- Create / Add / Generate (insert new fields) rules attached to transactions
- Transaction elements that update existing fields
- Rules that are imbedded into Screen business rules, and create new, or update existing fields
For the purposes of demonstrating the currency validation feature, six rules/elements were selected from the four categories above.
Business Rules
- CopyToPolicyFields: This rule is attached to the Premium transaction in the International Holding Company in the Unit Linked template. Target field is LastPremiumAmount in PolicyScreen business rule in the Unit Linked template.
Navigate to Main Explorer | International Holding Company | Subsidiary Companies | International Child Company | Plans | Unit Linked Template | Transactions | Policy Transactions | Premium | Attached Rules | CopyToPolicyFields.
- MaintainSuspense: This rule can be found in the Prototype Company in the Functional Prototype Plan. The target field is the PremiumAmount in the SuspenseScreen business rule in the Functional Prototype Plan.
Navigate to Main Explorer | Prototype Company | Subsidiary Companies | Prototype Child Company | Plans | Functional Prototype Plan | Transactions | Policy Transactions | MaintainSuspense | Attached Rules | MaintainSuspense-(FunctionalPrototypePlan).
- CopyToSegmentFields: This transaction can be found in the Prototype Company in the Functional Prototype Plan under Policy Transactions. The target field is the SegmentAmount in the Base Coverage segment in the Functional Prototype Plan.
Navigate to Main Explorer | Prototype Company | Subsidiary Companies | Prototype Child Company | Plans | Functional Prototype Plan | Transactions | Policy Transactions | CopyToSegmentFields | Attached Rules | CopyToSegmentFields-(FunctionalPrototypePlan).
- CalculateGeneral: This rule can be found in the Global Rules explorer under Calculate | CalculateGenearlLifeBaseCov | Plan Overrides for Guaranteed Level Premium Term. The target fields are the money fields in the Guaranteed Level Premium Term Base Coverage segement and PolicyScreen business rule.
Transactions
- AddRolesPrototype: This transaction can be found in the Prototype Company in the Functional Prototype Plan. The target field is the Amount field in the Cont Bene Role Screen business rule in the Functional Prototype Plan.
- AddRolesCollection: This transaction can be found in the Prototype Company in the Functional Prototype Plan. The target field is the Amount field in the Cont Bene Role Screen business rule in the Functional Prototype Plan.
Elements
- Disbursement: This element can be found in the Holding Company | Primary Company in the Variable Deferred Annuity plan. The Target fields are TotalFederalWithholding and TotalStateWithholding in the Variable Deferred Annuity plan.