NUV Effective Date Missing Base Code Error When Some Transactions Are Being Processed
(Doc ID 2368600.1)
Last updated on FEBRUARY 03, 2019
Applies to:Oracle Insurance Policy Administration J2EE - Version 10.2.0.29 and later
Information in this document applies to any platform.
On : 10.2.0.29 version, General
prior to 12/31/2006, certain policies had deposited and then completely liquidated money from a closed fund, but the last ending record in AsFundValue still shows cash value and units as greater than 0. Even though there is no money currently in that fund and there have been multiple activities processed since then, OIPA base code does not like the fact that the ending cashvalue and units were never set to 0 and since there are no NUV’s for the closed funds on the date that the activities are being processed for, it throws the NUV error.
Since we are using Point In Time valuation, base code should only be concerned with the funds that are existing as of the last processed activity, yet we are observing that it is looking through all the fund history in AsFundValue and considering any funds that do not have an ending balance of 0
The issue has the following business impact:
Due to this issue, users are Unable to process certain transactions
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