Scheduled Computation

Scheduled Computation is run at the plan level and provides the ability to calculate values on policies or segments that do not have a variable component. For policies with a variable component, use scheduled valuation to calculate values.

A plan level transaction is typically used to execute scheduled computation. The ScheduledValuation rule is attached to the transaction. A specific selection of policies or segments can be identified through the use of a SQLquery in the rule. Make sure that the planGUIDis hard coded in the query. Once the policies or segments have been selected, a computation rule is called to perform various calculations such as cash value, surrender charge, and anything else required using standard math syntax. The output values that are calculated are stored in the database in order to be accessed for reporting or to be picked up by downstream systems.

View Scheduled Computation prototype example...

Configure Scheduled Computation

The ScheduledValuation business rule is used to perform either scheduled valuation or scheduled computation. The rule configuration drives the type of action that is performed. This rule is attached to a plan level transaction. An explanation of the configuration needed to perform scheduled computation is provided below.

High Level Steps to Configure

  1. A plan level transaction must be created to initiate the process.
  2. A ScheduledValutation rule must be configured to perform computation. This is an attached business rule that will be added to the plan level transaction.
  3. A Computation rule must be configured to perform the calculations. This rule is identified in the <Computation> element inside the ScheduledValuation rule.
  4. Use the System Properties to define the number of requests that can be simultaneously processed by the system. The scheduledValuation.batchSize and scheduledValuation.period properties control this. An explanation of all OIPA System Properties can be found on the Oracle Technology Network (OTN) in the documentation library that supports this release.

Plan Level Transaction

A prototype transaction was created to demonstrate the configuration needed for scheduled computation. Navigate to Global Explorer | Transactions | ScheduledComputation Policy OR ScheduledComputationSegment. The following configuration requirements must exist in the transaction.

<Asynchronous CHECKINTERVAL="30" TIMEOUT="1000" CONTINUE="No">Yes</Asynchronous>

ScheduledValuation Rule

A prototype rule was created to demonstrate the configuration of this rule. Navigate to Global Explorer | Business Rules | Attached Rules | ScheduledValuation | Transaction Overrides | Scheduled Valuation (ScheduledComputationPolicy-Functional Prototype Plan).

Important   A best practice would be to create a validation count of the number of policies or segments the rule is expected to process within the activity math that could be used to compare to the actual number of requests created.

Computation Rule

Database Tables

Three tables were created to support scheduled computation:

  1. AsScheduledComputation: holds records created from the ScheduledValuation rule when Policy or Segment is the value of the <Computation> element and a computation rule output relates to a PolicyGUID or SegmentGUID.
  2. AsScheduledComputationField: holds output from Computation rule.
  3. AsComputationRequest: holds a record for each time a Plan level activity executes with an attached ScheduledValuation rule that is configured with a valid Computation element and computation rule.
     
Copyright © 2017, Oracle and/or its affiliates. All rights reserved. About Oracle Insurance | Contact Us