DBA Data[Home] [Help]

APPS.HR_EMPLOYEE_APPLICANT_API dependencies on PER_PER_UPD

Line 1137: per_per_upd.upd

1133: else
1134: close csr_future_per_changes;
1135: end if;
1136: --
1137: per_per_upd.upd
1138: (p_person_id => p_person_id
1139: ,p_effective_start_date => l_per_effective_start_date
1140: ,p_effective_end_date => l_per_effective_end_date
1141: ,p_person_type_id => l_person_type_id1

Line 1997: -- being modified by the per_per_upd.upd table handler.)

1993: --
1994: -- Lock the person record in PER_ALL_PEOPLE_F ready for UPDATE at a later point.
1995: -- (Note: This is necessary because calling the table handlers in locking
1996: -- ladder order invokes an error in per_apl_upd.upd due to the person
1997: -- being modified by the per_per_upd.upd table handler.)
1998: if l_per_effective_start_date=l_hire_date then
1999: l_datetrack_update_mode:='CORRECTION';
2000: else
2001: l_datetrack_update_mode:='UPDATE';

Line 2079: per_per_upd.upd

2075: -- the per_all_people_f table.
2076: --
2077: l_applicant_number:=hr_api.g_varchar2;
2078: l_employee_number:=hr_api.g_varchar2;
2079: per_per_upd.upd
2080: (p_person_id => p_person_id
2081: ,p_effective_date => l_hire_date
2082: ,p_applicant_number => l_applicant_number
2083: ,p_employee_number => l_employee_number