0 registered members (),
3
guests, and
12
spiders. |
Key:
Admin,
Global Mod,
Mod
|
|
|
#12220 - 15/04/19 03:52 PM
Re: Fixed Term/Contract Employees
[Re: JGrewal01]
|
Joined: Mar 2005
Posts: 4
JGrewal01
stranger
|
stranger
Joined: Mar 2005
Posts: 4
|
Gentlemen Greetings Happy to hear from Del and CT .
Here is the problem(I think): There seems to be behaviour difference in the application when an API is used to terminate the employee, compared to when an employee is terminated in the application (End Employment). When the API is used to terminate an employee, the issues are: Entering end date to the Open ended absences. Tax Certificates do not load for these employees … blah Reverse termination has to be performed, before the above can be addressed.
This begs a question – when should one enter terminations details – rather when is the ideal time! For fixed term contract employees they are terminated on the same day they are hired – i.e. Hire date 1-JAN-2016, Termination date = 31 Dec-2017, 2 year duration, all done in one integration run( create_<>_employee,-----, actual_termination_emp). Problem is that the End date is used for reporting, benefit entitlement, blah, blah. I was looking for quick and dirty - which seems to be Reverse...
I never wanted to be a consultant – I wanted to be a Pig farmer, my first choice – failed my CSEs.
Last edited by JGrewal01; 15/04/19 03:53 PM.
|
|
|
#12223 - 16/04/19 01:03 PM
Re: Fixed Term/Contract Employees
[Re: JGrewal01]
|
Joined: Mar 2005
Posts: 2,122
CT
|
  
Joined: Mar 2005
Posts: 2,122
|
Taking a bit of a step back here, is this actually about migrating historical details of ex-employees? Or are we talking about a live system where new employees are entered, and a termination date added because the end-date is known in advance eg 2 years? Or both? In migration, one would always seek to make setting the end date(s) the last thing one does to an historical record.
In terms of APIs, it should be remembered that the end employment form deals with a business process in its entirety, which encompasses the use of several APIs (not just actual_termination_emp), and may also include references to benefits-type APIs for end-dating absences etc. There could even be some custom code hanging around in the background that wouldn't be known about by the APIs.
Obviously being one of the great unwashed now I am unable (and it must be said mentally incapable) to follow this up in any great detail, but one of the things you might look at is the effect of the final process date, e.g. does it get entered at the same time, and if so what happens if you leave it off and just have the actual termination/last-standard-process dates.
What reports and process rely on the presence of the actual termination date? Are they custom ones or Oracle standard ones?
CT
|
|
|
|
Forums60
Topics2,233
Posts12,046
Members1,321
|
Most Online283 Dec 25th, 2019
|
|
|
|
|
|
|
1
|
2
|
3
|
4
|
5
|
6
|
7
|
8
|
9
|
10
|
11
|
12
|
13
|
14
|
15
|
16
|
17
|
18
|
19
|
20
|
21
|
22
|
23
|
24
|
25
|
26
|
27
|
28
|
29
|
30
|
31
|
|
|
|
|
|
|
|
|