First of all: I'm new in the forum so... Hi all from Madrid, Spain.
I'm new with Oracle Applications and with HR module, so I hope I can learn/help a lot here.
This is my problem, not answered in metalink neither OTN forums :
-----------------------------------------------------------------------------------
I've found a curious behavior updating the employee assignment... that affects to the Historical of an employee assignment (per_all_assignments_f)
- I make an update (not a CORRECTION) in the location item (form PERWSHRG) and after that I go to see the Assignment History (PERWSASH)... it occurs that I only can see the last "location" for my emp... the others (sent to the historical) were deleted during the "update"...
I am also new in HRMS.
As per my knowledge,this is the way of date tracking in HRMS.
HRMS prompts you for either a "Correct Mode" or "Update Mode".
Lets say the record, before making the change the record was
Person First Name: Aish
Person First Name: Rai
effective_start_date : 10-JAN-2003 --when the person joined organization
effective_end_date : 31-12-4712 -- From Hr_Api.g_eot [end of time, well not literally]
If the record is modified in Correction mode, then this record will be modified as
Person First Name: Aish
Person First Name: Bachan
effective_start_date : 10-JAN-2003 --when the person joined organization
effective_end_date : 31-12-4712 -- From Hr_Api.g_eot [end of time, well not literally]
If the record is modified in UPDATE mode, then this record will be modified as
The existing record will be end dated
Person First Name: Aish
Person First Name: Rai
effective_start_date : 10-JAN-2003 --when the person joined organization
effective_end_date : 23-Dec-2006 -- a day prior to date-track date
A new record will be created
Person First Name: Aish
Person First Name: bachan
effective_start_date : 24-DEC2006 --when the person joined organization
effective_end_date : 31-12-4712 -- From Hr_Api.g_eot
Does this mean, when modifying in UPDATE mode existing record is end-dated and a new record is created.
Hi Siva,
in my case, and following with your example, my records are:
(I had two assignment records initially)
------------------------- record 1
Person First Name: Jose
Person First Name: Luis
effective_start_date : 01-03-2001
effective_end_date : 30-11-2005
creation_date: 11-07-2002
last_updated_date: 06-02-2006
location_id: 25011
---------------------- record 2
Person First Name: Jose
Person First Name: Luis
effective_start_date : 01-12-2005
effective_end_date : 31-12-4712
creation_date: 21-12-2005
last_updated_date: 24-02-2006
location_id: 25011
----------------------
After Updating in employee assignment the location field, the records have this:
------------------------- record 1
Same values...
---------------------- record 2
Person First Name: Jose
Person First Name: Luis
effective_start_date : 01-12-2005
effective_end_date : 02-04-2007
creation_date: 21-12-2005
last_updated_date: 24-02-2006
location_id: NULL
---------------------- RECORD 3 (NEW)
Person First Name: Jose
Person First Name: Luis
effective_start_date : 03-04-2007
effective_end_date : 31/12/4712
creation_date: 21-12-2005
last_updated_date: 24-02-2006
location_id: 26344
----------------------
The questions are:
- Why is update to NULL the location code in record 2?
- Why last_updated_date doesn't have sysdate value? (update was made today)
Following the code, I've see that in the ON-UPDATE trigger ,at ASSGT block, in PERWSHR form, it's made the call to fnd_standard.set_who so.. I don't understand why the last_updated_date is not set to sysdate.
: