My Oracle Support Banner

EffectiveDate Parameter Not Working In ExposedComputation Business Rule (Doc ID 2508483.1)

Last updated on DECEMBER 04, 2019

Applies to:

Oracle Insurance Policy Administration J2EE - Version and later
Information in this document applies to any platform.


On : version, General

Per the documentation in V10:

Inclusion of an EffectiveDate parameter can be done when an exposed computation executes Valuation during the request. This date will be used as the Valuation Date during Valuation. If this parameter is not defined and Valuation is still executed, then the Valuation Date will default to the System Date. Below is the expected format for the XML parameter in the request:

<Parameter NAME=”PolicyNumber”>POL12345
<Parameter NAME=”EffectiveDate”>01/01/2009

Currently the system doesn’t take into consideration the configured effective date parameter, instead it always uses the System Date.

 Per the documentation noted above, when an EffectiveDate parameter is used in the ExposedComputation rule, the date specified should be used in place of the System Date in Valuation.

The issue can be reproduced at will with the following steps:
1. Configure an instance of the ExposedComputation rule with the EffectiveDate parameter specified as a date other than the System Date. When executed, the computation will utilize the System Date.

The issue has the following business impact:
Cannot specify a date other than the System Date in an exposed computation, resulting in incorrect values.


To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!

In this Document

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.