REL1001F: Adjusting Start Date of Flex Field Value Does not Check Period Validity (Doc ID 2081725.1)

Last updated on NOVEMBER 24, 2015

Applies to:

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

Symptoms

On : 10.15.1.2 version, Configuration (Policy)

ACTUAL BEHAVIOR
---------------
REL1001F: Adding a flex field value with a period violating the allowed period of the entity flex field results in error message:
REF-01418 - The validity period of the flex field value must be within the validity period of the entity flex field. (#1#).
However, when updating the start date of the validity period of the flex field value leading to a violating of the allowed period of the entity flex field does NOT result in this error message.
(Updating the end date does result in the error message)

EXPECTED BEHAVIOR
-----------------------
Updating the start date of the validity period of the flex field value leading to a violating of the allowed period of the entity flex field should result in an error message.


STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. Start REL1001F, lookup a relation
2. navigate to page 3
3. fill in a value and start date and end date, use a valid period. Commit.
4. Update the start date, so that the resulting period is not valid

BUSINESS IMPACT
-----------------------
The issue has the following business impact:
Due to this issue, invalid periods can arise

Cause

Sign In with your My Oracle Support account

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

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms