You are here: Main Explorer Folders > Prototypes > New Prototype Samples For This Release > Rolling Valuation

Oracle® Insurance Rules Palette 9.4.0.0 E18894_01

# Rolling Valuation

As part of the new Unit Linked processing, a new attached business rule called PostAssignmentValidateExpressions has been added to support math calculations and business edits that need to occur after transaction assignment processing has completed.

The processing sequence of an activity is now as follows:

1. Suspense
2. Valuation
3. Math
4. Attached Business Rules (existing configurable processing breakpoint)
5. Assignment
6. Post Assignment Business Rules (new configurable processing breakpoint)
7. Disbursement
8. Accounting
9. Spawns

The PostAssignmentValidateExpressions rule will be optionally associated to a transaction by a transaction override on the AsBusinessRules table but not exist in the TransactionBusinessRulePacket itself. This distinction allows the rule to process each time the activity processes while in an (NUV) pending state.

The PostAssignmentValidateExpressions rule is made up of three sections with distinct uses.

1. Math: This is where standard math logic can be configured to calculate necessary values. It will have access to any field or logged math variable from the transaction in addition to assignment records calculated to write to AsValuation. Where regular transaction math does not processes again after the activity moves to NUV Pending status, the math of the PostAssignmentValidateExpressions will process with every execution until the activity is Active or Gain Loss Pending. Note: Variables in the PostAssignmentValidateExpressions math cannot be logged and are not visible in the processed activity math pane. They are visible in the AsActivity XMLData.
2. Expressions: Configured expressions operate the same as the ValidateExpressions rule but use values from the PostAssignmentValidateExpressions math and fields or logged math variables from the transaction. An additional feature is the optional automatic cancellation attribute that will force the system to shadow the activity if the conditional expression resolves to true. Activities that are systematically rejected with this rule still appear in the policy activity list but have a status of "Cancelled". An application of this feature would be if an owner requests a withdrawal of 5% of their policy but days later when the policy value is known, it turns out this calculation is below the plan minimum surrender amount. Rather than notifying users of the business error via an action required report, the system can automatically reject the activity.
3. GenerateAccounting: This element holds a simple Yes or No value (literal value or math variable) that tells the system if accounting should process for the activity. When set to Yes, accounting will process and write records for the applicable chart of accounts entries provided a PostAssignmentValidateExpressions error is not thrown. Accounting will run each time the activity processes but will only write to the database once. The value of this element acts as a configurable gate that prevents accounting from writing records prematurely. Note:If the transaction writes accounting from the transaction math, then those variables should be logged to ensure they will be available for the accounting detail.

## Spawns

- In order to prevent unwanted spawning of duplicate activities, the PostAssignmentValidateExpressions math can create indicators based on existing spawned activities that can be read by the SpawnIF conditions. Similarly, the <From> field values in the spawn section should be able to draw from the PostAssignmentValidateExpressions math in addition to the normal transaction math and fields.

- If an activity is spawned again upon subsequent processing of the parent activity, the spawned activity may cause prior spawned activities to reprocess only if its effective date and/or processing order are earlier than those of its siblings.

- ## Status Changes

- If the new PostAssignmentValidateExpressions rule stops the activity from processing, then the activity will go to its prior status. Even if all the prices for the funds are found on the first execution of the activity (from a pending status), and if an error occurs, then the activity will remain in a pending status. If the error is overridden, then the activity will process again (including math and attached rules) and if the same error is given again, then the system will retain that it was overridden and will not stop the activity from executing.

## Configuration Requirements

- Create the transaction that will process assignment values.
- Configure the PostAssignmentValidateExpressions business rule override.

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

Open table of contents