APPS.PER_REI_INS dependencies on HR_API

Line 125: If (p_datetrack_mode <> hr_api.g_insert) then

121: --
122: -- If the datetrack_mode is not INSERT then we must populate the WHO
123: -- columns with the 'old' creation values and 'new' updated values.
124: --
125: If (p_datetrack_mode <> hr_api.g_insert) then
126: hr_utility.set_location(l_proc, 10);
127: --
128: -- Select the 'old' created values
129: --

Line 299: When hr_api.check_integrity_violated Then

295: per_rei_shd.g_api_dml := false; -- Unset the api dml status
296: hr_utility.set_location(' Leaving:'||l_proc, 15);
297: --
298: Exception
299: When hr_api.check_integrity_violated Then
300: -- A check constraint has been violated
301: per_rei_shd.g_api_dml := false; -- Unset the api dml status
302: per_rei_shd.constraint_error
303: (p_constraint_name => hr_api.strip_constraint_name(SQLERRM));

Line 303: (p_constraint_name => hr_api.strip_constraint_name(SQLERRM));

299: When hr_api.check_integrity_violated Then
300: -- A check constraint has been violated
301: per_rei_shd.g_api_dml := false; -- Unset the api dml status
302: per_rei_shd.constraint_error
303: (p_constraint_name => hr_api.strip_constraint_name(SQLERRM));
304: When hr_api.unique_integrity_violated Then
305: -- Unique integrity has been violated
306: per_rei_shd.g_api_dml := false; -- Unset the api dml status
307: per_rei_shd.constraint_error

Line 304: When hr_api.unique_integrity_violated Then

300: -- A check constraint has been violated
301: per_rei_shd.g_api_dml := false; -- Unset the api dml status
302: per_rei_shd.constraint_error
303: (p_constraint_name => hr_api.strip_constraint_name(SQLERRM));
304: When hr_api.unique_integrity_violated Then
305: -- Unique integrity has been violated
306: per_rei_shd.g_api_dml := false; -- Unset the api dml status
307: per_rei_shd.constraint_error
308: (p_constraint_name => hr_api.strip_constraint_name(SQLERRM));

Line 308: (p_constraint_name => hr_api.strip_constraint_name(SQLERRM));

304: When hr_api.unique_integrity_violated Then
305: -- Unique integrity has been violated
306: per_rei_shd.g_api_dml := false; -- Unset the api dml status
307: per_rei_shd.constraint_error
308: (p_constraint_name => hr_api.strip_constraint_name(SQLERRM));
309: When Others Then
310: per_rei_shd.g_api_dml := false; -- Unset the api dml status
311: Raise;
312: End dt_insert_dml;

Line 621: when hr_api.cannot_find_prog_unit then

617: );
618: --
619: exception
620: --
621: when hr_api.cannot_find_prog_unit then
622: --
623: hr_api.cannot_find_prog_unit_error
624: (p_module_name => 'PER_CONTACT_EXTRA_INFO_F'
625: ,p_hook_type => 'AI');

Line 623: hr_api.cannot_find_prog_unit_error

619: exception
620: --
621: when hr_api.cannot_find_prog_unit then
622: --
623: hr_api.cannot_find_prog_unit_error
624: (p_module_name => 'PER_CONTACT_EXTRA_INFO_F'
625: ,p_hook_type => 'AI');
626: --
627: end;

Line 656: -- another user. This will raise the HR_Api.Object_Locked exception.

652: --
653: -- Post Failure:
654: -- The Lck process can fail for:
655: -- 1) When attempting to lock the row the row could already be locked by
656: -- another user. This will raise the HR_Api.Object_Locked exception.
657: -- 2) When attempting to the lock the parent which doesn't exist.
658: -- For the entity to be locked the parent must exist!
659: --
660: -- Developer Implementation Notes:

Line 724: l_datetrack_mode varchar2(30) := hr_api.g_insert;

720: ,p_rec in out nocopy per_rei_shd.g_rec_type
721: ) is
722: --
723: l_proc varchar2(72) := g_package||'ins';
724: l_datetrack_mode varchar2(30) := hr_api.g_insert;
725: l_validation_start_date date;
726: l_validation_end_date date;
727: --
728: Begin