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_SID_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 193: When hr_api.check_integrity_violated Then

189: --
190: hr_utility.set_location(' Leaving:'||l_proc, 15);
191: --
192: Exception
193: When hr_api.check_integrity_violated Then
194: -- A check constraint has been violated
195: --
196: pay_sid_shd.constraint_error
197: (p_constraint_name => hr_api.strip_constraint_name(SQLERRM));

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

193: When hr_api.check_integrity_violated Then
194: -- A check constraint has been violated
195: --
196: pay_sid_shd.constraint_error
197: (p_constraint_name => hr_api.strip_constraint_name(SQLERRM));
198: When hr_api.unique_integrity_violated Then
199: -- Unique integrity has been violated
200: --
201: pay_sid_shd.constraint_error

Line 198: When hr_api.unique_integrity_violated Then

194: -- A check constraint has been violated
195: --
196: pay_sid_shd.constraint_error
197: (p_constraint_name => hr_api.strip_constraint_name(SQLERRM));
198: When hr_api.unique_integrity_violated Then
199: -- Unique integrity has been violated
200: --
201: pay_sid_shd.constraint_error
202: (p_constraint_name => hr_api.strip_constraint_name(SQLERRM));

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

198: When hr_api.unique_integrity_violated Then
199: -- Unique integrity has been violated
200: --
201: pay_sid_shd.constraint_error
202: (p_constraint_name => hr_api.strip_constraint_name(SQLERRM));
203: When Others Then
204: --
205: Raise;
206: End dt_insert_dml;

Line 397: when hr_api.cannot_find_prog_unit then

393: );
394: --
395: exception
396: --
397: when hr_api.cannot_find_prog_unit then
398: --
399: hr_api.cannot_find_prog_unit_error
400: (p_module_name => 'PAY_IE_PRSI_DETAILS_F'
401: ,p_hook_type => 'AI');

Line 399: hr_api.cannot_find_prog_unit_error

395: exception
396: --
397: when hr_api.cannot_find_prog_unit then
398: --
399: hr_api.cannot_find_prog_unit_error
400: (p_module_name => 'PAY_IE_PRSI_DETAILS_F'
401: ,p_hook_type => 'AI');
402: --
403: end;

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

428: --
429: -- Post Failure:
430: -- The Lck process can fail for:
431: -- 1) When attempting to lock the row the row could already be locked by
432: -- another user. This will raise the HR_Api.Object_Locked exception.
433: -- 2) When attempting to the lock the parent which doesn't exist.
434: -- For the entity to be locked the parent must exist!
435: --
436: -- Developer Implementation Notes:

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

490: ,p_rec in out nocopy pay_sid_shd.g_rec_type
491: ) is
492: --
493: l_proc varchar2(72) := g_package||'ins';
494: l_datetrack_mode varchar2(30) := hr_api.g_insert;
495: l_validation_start_date date;
496: l_validation_end_date date;
497: --
498: Begin