My Oracle Support Banner

Cannot Assign EffectiveDate by an OnLoad (Doc ID 2509839.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, Activity

The EffectiveDate of a transaction cannot have its value changed by an OnLoad.
However it can using OnChange and OnSubmit.

The EffectiveDate to change to the date determine by the config.

The issue can be reproduced at will with the following steps:
1. Use Policy 010004091 (supplied in backup).
2. In the activity queue , user selects the test policy transaction. The system date is 2019-12-30.
3. During the OnLoad the config updates the EffectiveDate and the Date for OnChange to 2001-01-01. * Only the Date for OnChange did change. Not the EffectiveDate.
4. Then enter in the Date for OnChange 2002-02-02, the EffectiveDate will change to 2002-02-02.
5. Finally press OK and the OnSubmit will change the EffectiveDate to 2003-03-03 as shown in the queue.

The issue has the following business impact:
The transaction will not be schedule on the correct EffectiveDate.
We have move the EffectiveDate change to the OnSubmit (not on the test-policy transaction but on our actual transaction that would need this) but that means that the user cannot
see the change on the EffectiveDate and must look into the ActivityQueue for the activity. This last part is time consuming.


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.