APPS.PAY_ETP_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 359: When hr_api.check_integrity_violated Then

355: pay_etp_shd.g_api_dml := false; -- Unset the api dml status
356: hr_utility.set_location(' Leaving:'||l_proc, 15);
357: --
358: Exception
359: When hr_api.check_integrity_violated Then
360: -- A check constraint has been violated
361: pay_etp_shd.g_api_dml := false; -- Unset the api dml status
362: pay_etp_shd.constraint_error
363: (p_constraint_name => hr_api.strip_constraint_name(SQLERRM));

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

359: When hr_api.check_integrity_violated Then
360: -- A check constraint has been violated
361: pay_etp_shd.g_api_dml := false; -- Unset the api dml status
362: pay_etp_shd.constraint_error
363: (p_constraint_name => hr_api.strip_constraint_name(SQLERRM));
364: When hr_api.unique_integrity_violated Then
365: -- Unique integrity has been violated
366: pay_etp_shd.g_api_dml := false; -- Unset the api dml status
367: pay_etp_shd.constraint_error

Line 364: When hr_api.unique_integrity_violated Then

360: -- A check constraint has been violated
361: pay_etp_shd.g_api_dml := false; -- Unset the api dml status
362: pay_etp_shd.constraint_error
363: (p_constraint_name => hr_api.strip_constraint_name(SQLERRM));
364: When hr_api.unique_integrity_violated Then
365: -- Unique integrity has been violated
366: pay_etp_shd.g_api_dml := false; -- Unset the api dml status
367: pay_etp_shd.constraint_error
368: (p_constraint_name => hr_api.strip_constraint_name(SQLERRM));

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

364: When hr_api.unique_integrity_violated Then
365: -- Unique integrity has been violated
366: pay_etp_shd.g_api_dml := false; -- Unset the api dml status
367: pay_etp_shd.constraint_error
368: (p_constraint_name => hr_api.strip_constraint_name(SQLERRM));
369: When Others Then
370: pay_etp_shd.g_api_dml := false; -- Unset the api dml status
371: Raise;
372: End dt_insert_dml;

Line 806: when hr_api.cannot_find_prog_unit then

802: );
803: --
804: exception
805: --
806: when hr_api.cannot_find_prog_unit then
807: --
808: hr_api.cannot_find_prog_unit_error
809: (p_module_name => 'PAY_ELEMENT_TYPES_F'
810: ,p_hook_type => 'AI');

Line 808: hr_api.cannot_find_prog_unit_error

804: exception
805: --
806: when hr_api.cannot_find_prog_unit then
807: --
808: hr_api.cannot_find_prog_unit_error
809: (p_module_name => 'PAY_ELEMENT_TYPES_F'
810: ,p_hook_type => 'AI');
811: --
812: end;

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

837: --
838: -- Post Failure:
839: -- The Lck process can fail for:
840: -- 1) When attempting to lock the row the row could already be locked by
841: -- another user. This will raise the HR_Api.Object_Locked exception.
842: -- 2) When attempting to the lock the parent which doesn't exist.
843: -- For the entity to be locked the parent must exist!
844: --
845: -- Developer Implementation Notes:

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

897: ,p_processing_priority_warning out nocopy boolean
898: ) is
899: --
900: l_proc varchar2(72) := g_package||'ins';
901: l_datetrack_mode varchar2(30) := hr_api.g_insert;
902: l_validation_start_date date;
903: l_validation_end_date date;
904: l_processing_priority_warning boolean;
905: --