ETL9.2: Earliest Change Date Gets Updated To Future Date When Future Absence Request Is Reported. (Doc ID 2221498.1)

Last updated on JULY 21, 2023

Applies to:

Symptoms

On : 9.2 version, TL Integrations

We are in the process of testing our upgraded 9.2 PUM 18 environment. We noticed that when future-dated absence request is entered and approved, Earliest Change Date for the employee gets set to the date of the absence.   As a result, employee's reported time between the current date and the future absence date is not processed.

This issue was previously identified in v9.1 and Bug 20458416 has been logged . Oracle provided a print project for us to fix the issue in v9.1.
Search for this bug returns an article that indicates that the fix was targeted for v9.2 PUM 13, but the issue is still occurring:

ETL9.x: TL_TR_STATUS Not Updated As Expected In Some Absence Event Scenarios (Doc ID 1996614.1) that contains information about the bug that was fixed in PUM 13: Bug 20541699.

REPLICATION STEPS
=================
TESTED IN PUM 18:
Login as the supervisor that employee reports time to. `Approve reported time¿ needs to be on for the employee. Replicate using absence management employee.
The absence tab will be present on the timesheet. Make sure that TA_STATUS field is set to N prior to reporting the absence event.

1-Navigate to Employee's timesheet (MSS->Time Management ->Report Time  ->TimeSheet)
2-Click on absence and report vacation for a future date from ECD.
3-On the same timesheet, click on the absence tab once more and approve the absence reported
4-ECD will get reset to the date of absence

Cause

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