APPS.PAY_ETP_INS_ND 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 355: When hr_api.check_integrity_violated Then

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

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

355: When hr_api.check_integrity_violated Then
356: -- A check constraint has been violated
357: pay_etp_shd_nd.g_api_dml := false; -- Unset the api dml status
358: pay_etp_shd_nd.constraint_error
359: (p_constraint_name => hr_api.strip_constraint_name(SQLERRM));
360: When hr_api.unique_integrity_violated Then
361: -- Unique integrity has been violated
362: pay_etp_shd_nd.g_api_dml := false; -- Unset the api dml status
363: pay_etp_shd_nd.constraint_error

Line 360: When hr_api.unique_integrity_violated Then

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

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

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

Line 802: when hr_api.cannot_find_prog_unit then

798: );
799: --
800: exception
801: --
802: when hr_api.cannot_find_prog_unit then
803: --
804: hr_api.cannot_find_prog_unit_error
805: (p_module_name => 'PAY_ELEMENT_TYPES_F'
806: ,p_hook_type => 'AI');

Line 804: hr_api.cannot_find_prog_unit_error

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

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

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

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

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