Absence Management ER: Absence Shows Wrong Error Message For Childbirth Type

(Doc ID 2207279.1)

Last updated on NOVEMBER 24, 2016

Applies to:

Oracle Fusion Absence Management Cloud Service - Version 11.1.10.0.0 and later
Information in this document applies to any platform.

Symptoms

Absence shows wrong error message for Childbirth type

When logging an absence the message "You must enter a planned end date or actual end date." is displayed even though one of the fields is populated.
Setup:
Pattern: Childbirth or Injury
Fields enabled:
  Expected Date of Event
  Planned Start Date
  Planned End Date
  Actual Date of Event
  Actual Start Date
  Actual End Date

The message should be something like "You must enter an Actual Start Date if you provide an Actual End Date".
The same message exactly pops up if Planned Start Date, Planned End Date, and Actual End Date are populated
Also, there are cases when the error should not show. All scenarios below explained in the EXPECTED BEHAVIOR area

EXPECTED BEHAVIOR
-----------------------
1. Scenario below:
Expected Date of Childbirth: 09-Dec-2015
Planned Start date: 26-Mar-2016
Actual End Date: 28-Mar-2016
Error: "You must enter a planned end date or actual end date."
Expected behavior: error message text needs to be changed to something like "You must enter an Actual Start Date if you provide an Actual End Date".

2. Scenario below:
Expected Date of Childbirth: 09-Dec-2015
Planned Start date: 26-Mar-2016
Planned End Date: 27-Mar-2016
Actual End Date: 28-Mar-2016
Error: "Actual start date must be before the actual end date"
Expected behavior: error message text needs to be changed to something like "You must enter an Actual Start Date if you provide an Actual End Date".

3. Scenario below:
Expected Date of Childbirth: 26-Mar-2015
Planned Start date: 26-Mar-2016
Planned End Date: 05-Apr-2016
Actual Start Date: 25-Mar-2016
Error: "You must enter a planned end date or actual end date."
Expected behavior: error message should not come here


BUSINESS IMPACT
-----------------------
The issue has the following business impact:
For the first 2 scenarios, the message is simply misleading.
For the third:
The typical process flow for logging a maternity leave is:
1) employee enters planned start date and planned end date
2) employee decides on actual start date, but does not yet know the actual end date.
3) employee goes on leave
4) employee is about to come back and actual end date is populated.

If this process requires the open-ended check box to be entered then the user experience suffers tremendously and this would lead to the wrong data being entered a lot. The system would then show both a "Planned End Date" and an "Estimated End Date".

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