12.2 E-Business Suite Workflow Directory Services Termination Workflow Responsiblity End Date Prevents Responsibility Access For The Last Day Marked As The Expiration Date
(Doc ID 2459659.1)
Last updated on MARCH 29, 2022
Applies to:Oracle Workflow - Version 12.2.6 and later
Information in this document applies to any platform.
E-Business Suite 12.2 Workflow, Directory Service Missing Responsibility related issues
When the termination workflow is end dates FND users, a user responsibility assignment is end dated with today's date and the user cannot access the responsibility for the rest of the day.
For example when responsibilities are end dated, the date is populated with 12:00 a.m. on the date the employee separated from the company.
The responsibilities should be end dated at 11:59 p.m. on the date of termination.
Responsibilities which receive an end date on a particular day should be considered inactive at midnight (12:00:00 AM) of that day and not till the last second at 11:59:59 PM.
If not then the user misses a whole day.
If an Employee is terminated on 8-Aug, they do not become an ex-Employee until 9-Aug.
If an Assignment is changed, like the Position, Location, or Supervisor ending on 8-Aug, the new Position/Location/Supervisor do not take effect until 9-Aug.
If a salary is updated effective 9-Aug, the previous salary ends on 8-Aug.
Everywhere else in date-tracking is inclusive of the end-date and it should be the same for Responsibilities.
If a Responsibility ends on 8-Aug, users should have access throughout the day and not have access beginning on 9-Aug.
The issue can be reproduced at will with the following steps:
1. Terminate employee
2. Responsibilities are ended @ 12:00am instead of 11:59
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