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_RTU_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 171: When hr_api.check_integrity_violated Then

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

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

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

Line 176: When hr_api.unique_integrity_violated Then

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

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

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

Line 404: when hr_api.cannot_find_prog_unit then

400: );
401: --
402: exception
403: --
404: when hr_api.cannot_find_prog_unit then
405: --
406: hr_api.cannot_find_prog_unit_error
407: (p_module_name => 'PAY_RUN_TYPE_USAGES_F'
408: ,p_hook_type => 'AI');

Line 406: hr_api.cannot_find_prog_unit_error

402: exception
403: --
404: when hr_api.cannot_find_prog_unit then
405: --
406: hr_api.cannot_find_prog_unit_error
407: (p_module_name => 'PAY_RUN_TYPE_USAGES_F'
408: ,p_hook_type => 'AI');
409: --
410: end;

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

435: --
436: -- Post Failure:
437: -- The Lck process can fail for:
438: -- 1) When attempting to lock the row the row could already be locked by
439: -- another user. This will raise the HR_Api.Object_Locked exception.
440: -- 2) When attempting to the lock the parent which doesn't exist.
441: -- For the entity to be locked the parent must exist!
442: --
443: -- Developer Implementation Notes:

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

500: ,p_rec in out nocopy pay_rtu_shd.g_rec_type
501: ) is
502: --
503: l_proc varchar2(72) := g_package||'ins';
504: l_datetrack_mode varchar2(30) := hr_api.g_insert;
505: l_validation_start_date date;
506: l_validation_end_date date;
507: --
508: Begin