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_ITR_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 175: When hr_api.check_integrity_violated Then

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

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

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

Line 180: When hr_api.unique_integrity_violated Then

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

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

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

Line 361: when hr_api.cannot_find_prog_unit then

357: );
358: --
359: exception
360: --
361: when hr_api.cannot_find_prog_unit then
362: --
363: hr_api.cannot_find_prog_unit_error
364: (p_module_name => 'PAY_ITERATIVE_RULES_F'
365: ,p_hook_type => 'AI');

Line 363: hr_api.cannot_find_prog_unit_error

359: exception
360: --
361: when hr_api.cannot_find_prog_unit then
362: --
363: hr_api.cannot_find_prog_unit_error
364: (p_module_name => 'PAY_ITERATIVE_RULES_F'
365: ,p_hook_type => 'AI');
366: --
367: end;

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

392: --
393: -- Post Failure:
394: -- The Lck process can fail for:
395: -- 1) When attempting to lock the row the row could already be locked by
396: -- another user. This will raise the HR_Api.Object_Locked exception.
397: -- 2) When attempting to the lock the parent which doesn't exist.
398: -- For the entity to be locked the parent must exist!
399: --
400: -- Developer Implementation Notes:

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

451: ,p_rec in out nocopy pay_itr_shd.g_rec_type
452: ) is
453: --
454: l_proc varchar2(72) := g_package||'ins';
455: l_datetrack_mode varchar2(30) := hr_api.g_insert;
456: l_validation_start_date date;
457: l_validation_end_date date;
458: --
459: Begin