eTRM uses javascript that opens and focuses a separate window to display reports. Your browser does not appear to support javascript. This should not prevent you from using eTRM but it does mean the window focus feature will not work. Please check the contents of other windows on your desktop if you click on a link that does not appear to do anything.

APPS.HR_LIP_INS dependencies on HR_API

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

99: --
100: -- If the datetrack_mode is not INSERT then we must populate the WHO
101: -- columns with the 'old' creation values and 'new' updated values.
102: --
103: If (p_datetrack_mode <> hr_api.g_insert) then
104: hr_utility.set_location(l_proc, 10);
105: --
106: -- Select the 'old' created values
107: --

Line 213: When hr_api.check_integrity_violated Then

209: --
210: hr_utility.set_location(' Leaving:'||l_proc, 15);
211: --
212: Exception
213: When hr_api.check_integrity_violated Then
214: -- A check constraint has been violated
215: --
216: hr_lip_shd.constraint_error
217: (p_constraint_name => hr_api.strip_constraint_name(SQLERRM));

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

213: When hr_api.check_integrity_violated Then
214: -- A check constraint has been violated
215: --
216: hr_lip_shd.constraint_error
217: (p_constraint_name => hr_api.strip_constraint_name(SQLERRM));
218: When hr_api.unique_integrity_violated Then
219: -- Unique integrity has been violated
220: --
221: hr_lip_shd.constraint_error

Line 218: When hr_api.unique_integrity_violated Then

214: -- A check constraint has been violated
215: --
216: hr_lip_shd.constraint_error
217: (p_constraint_name => hr_api.strip_constraint_name(SQLERRM));
218: When hr_api.unique_integrity_violated Then
219: -- Unique integrity has been violated
220: --
221: hr_lip_shd.constraint_error
222: (p_constraint_name => hr_api.strip_constraint_name(SQLERRM));

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

218: When hr_api.unique_integrity_violated Then
219: -- Unique integrity has been violated
220: --
221: hr_lip_shd.constraint_error
222: (p_constraint_name => hr_api.strip_constraint_name(SQLERRM));
223: When Others Then
224: --
225: Raise;
226: End dt_insert_dml;

Line 437: when hr_api.cannot_find_prog_unit then

433: );
434: --
435: exception
436: --
437: when hr_api.cannot_find_prog_unit then
438: --
439: hr_api.cannot_find_prog_unit_error
440: (p_module_name => 'HR_DE_LIABILITY_PREMIUMS_F'
441: ,p_hook_type => 'AI');

Line 439: hr_api.cannot_find_prog_unit_error

435: exception
436: --
437: when hr_api.cannot_find_prog_unit then
438: --
439: hr_api.cannot_find_prog_unit_error
440: (p_module_name => 'HR_DE_LIABILITY_PREMIUMS_F'
441: ,p_hook_type => 'AI');
442: --
443: end;

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

468: --
469: -- Post Failure:
470: -- The Lck process can fail for:
471: -- 1) When attempting to lock the row the row could already be locked by
472: -- another user. This will raise the HR_Api.Object_Locked exception.
473: -- 2) When attempting to the lock the parent which doesn't exist.
474: -- For the entity to be locked the parent must exist!
475: --
476: -- Developer Implementation Notes:

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

527: ,p_rec in out nocopy hr_lip_shd.g_rec_type
528: ) is
529: --
530: l_proc varchar2(72) := g_package||'ins';
531: l_datetrack_mode varchar2(30) := hr_api.g_insert;
532: l_validation_start_date date;
533: l_validation_end_date date;
534: --
535: Begin