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.PAY_ETU_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 173: When hr_api.check_integrity_violated Then

169: --
170: hr_utility.set_location(' Leaving:'||l_proc, 15);
171: --
172: Exception
173: When hr_api.check_integrity_violated Then
174: -- A check constraint has been violated
175: --
176: pay_etu_shd.constraint_error
177: (p_constraint_name => hr_api.strip_constraint_name(SQLERRM));

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

173: When hr_api.check_integrity_violated Then
174: -- A check constraint has been violated
175: --
176: pay_etu_shd.constraint_error
177: (p_constraint_name => hr_api.strip_constraint_name(SQLERRM));
178: When hr_api.unique_integrity_violated Then
179: -- Unique integrity has been violated
180: --
181: pay_etu_shd.constraint_error

Line 178: When hr_api.unique_integrity_violated Then

174: -- A check constraint has been violated
175: --
176: pay_etu_shd.constraint_error
177: (p_constraint_name => hr_api.strip_constraint_name(SQLERRM));
178: When hr_api.unique_integrity_violated Then
179: -- Unique integrity has been violated
180: --
181: pay_etu_shd.constraint_error
182: (p_constraint_name => hr_api.strip_constraint_name(SQLERRM));

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

178: When hr_api.unique_integrity_violated Then
179: -- Unique integrity has been violated
180: --
181: pay_etu_shd.constraint_error
182: (p_constraint_name => hr_api.strip_constraint_name(SQLERRM));
183: When Others Then
184: --
185: Raise;
186: End dt_insert_dml;

Line 414: when hr_api.cannot_find_prog_unit then

410: );
411: --
412: exception
413: --
414: when hr_api.cannot_find_prog_unit then
415: --
416: hr_api.cannot_find_prog_unit_error
417: (p_module_name => 'PAY_ELEMENT_TYPE_USAGES_F'
418: ,p_hook_type => 'AI');

Line 416: hr_api.cannot_find_prog_unit_error

412: exception
413: --
414: when hr_api.cannot_find_prog_unit then
415: --
416: hr_api.cannot_find_prog_unit_error
417: (p_module_name => 'PAY_ELEMENT_TYPE_USAGES_F'
418: ,p_hook_type => 'AI');
419: --
420: end;

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

445: --
446: -- Post Failure:
447: -- The Lck process can fail for:
448: -- 1) When attempting to lock the row the row could already be locked by
449: -- another user. This will raise the HR_Api.Object_Locked exception.
450: -- 2) When attempting to the lock the parent which doesn't exist.
451: -- For the entity to be locked the parent must exist!
452: --
453: -- Developer Implementation Notes:

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

510: ,p_rec in out nocopy pay_etu_shd.g_rec_type
511: ) is
512: --
513: l_proc varchar2(72) := g_package||'ins';
514: l_datetrack_mode varchar2(30) := hr_api.g_insert;
515: l_validation_start_date date;
516: l_validation_end_date date;
517: --
518: Begin