DBA Data[Home] [Help]

APPS.IRC_IID_INS dependencies on HR_API

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

111: --
112: -- If the datetrack_mode is not INSERT then we must populate the WHO
113: -- columns with the 'old' creation values and 'new' updated values.
114: --
115: If (p_datetrack_mode <> hr_api.g_insert) then
116: hr_utility.set_location(l_proc, 10);
117: --
118: -- Get the object version number for the insert
119: --

Line 226: When hr_api.check_integrity_violated Then

222: --
223: hr_utility.set_location(' Leaving:'||l_proc, 15);
224: --
225: Exception
226: When hr_api.check_integrity_violated Then
227: -- A check constraint has been violated
228: --
229: irc_iid_shd.constraint_error
230: (p_constraint_name => hr_api.strip_constraint_name(SQLERRM));

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

226: When hr_api.check_integrity_violated Then
227: -- A check constraint has been violated
228: --
229: irc_iid_shd.constraint_error
230: (p_constraint_name => hr_api.strip_constraint_name(SQLERRM));
231: When hr_api.unique_integrity_violated Then
232: -- Unique integrity has been violated
233: --
234: irc_iid_shd.constraint_error

Line 231: When hr_api.unique_integrity_violated Then

227: -- A check constraint has been violated
228: --
229: irc_iid_shd.constraint_error
230: (p_constraint_name => hr_api.strip_constraint_name(SQLERRM));
231: When hr_api.unique_integrity_violated Then
232: -- Unique integrity has been violated
233: --
234: irc_iid_shd.constraint_error
235: (p_constraint_name => hr_api.strip_constraint_name(SQLERRM));

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

231: When hr_api.unique_integrity_violated Then
232: -- Unique integrity has been violated
233: --
234: irc_iid_shd.constraint_error
235: (p_constraint_name => hr_api.strip_constraint_name(SQLERRM));
236: When Others Then
237: --
238: Raise;
239: End dt_insert_dml;

Line 455: when hr_api.cannot_find_prog_unit then

451: );
452: --
453: exception
454: --
455: when hr_api.cannot_find_prog_unit then
456: --
457: hr_api.cannot_find_prog_unit_error
458: (p_module_name => 'IRC_INTERVIEW_DETAILS'
459: ,p_hook_type => 'AI');

Line 457: hr_api.cannot_find_prog_unit_error

453: exception
454: --
455: when hr_api.cannot_find_prog_unit then
456: --
457: hr_api.cannot_find_prog_unit_error
458: (p_module_name => 'IRC_INTERVIEW_DETAILS'
459: ,p_hook_type => 'AI');
460: --
461: end;

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

486: --
487: -- Post Failure:
488: -- The Lck process can fail for:
489: -- 1) When attempting to lock the row the row could already be locked by
490: -- another user. This will raise the HR_Api.Object_Locked exception.
491: -- 2) When attempting to the lock the parent which doesn't exist.
492: -- For the entity to be locked the parent must exist!
493: --
494: -- Developer Implementation Notes:

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

538: ,p_rec in out nocopy irc_iid_shd.g_rec_type
539: ) is
540: --
541: l_proc varchar2(72) := g_package||'ins';
542: l_datetrack_mode varchar2(30) := hr_api.g_insert;
543: l_validation_start_date date;
544: l_validation_end_date date;
545: --
546: Begin