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_ELE_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 241: When hr_api.check_integrity_violated Then

237: pay_ele_shd.g_api_dml := false; -- Unset the api dml status
238: hr_utility.set_location(' Leaving:'||l_proc, 15);
239: --
240: Exception
241: When hr_api.check_integrity_violated Then
242: -- A check constraint has been violated
243: pay_ele_shd.g_api_dml := false; -- Unset the api dml status
244: pay_ele_shd.constraint_error
245: (p_constraint_name => hr_api.strip_constraint_name(SQLERRM));

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

241: When hr_api.check_integrity_violated Then
242: -- A check constraint has been violated
243: pay_ele_shd.g_api_dml := false; -- Unset the api dml status
244: pay_ele_shd.constraint_error
245: (p_constraint_name => hr_api.strip_constraint_name(SQLERRM));
246: When hr_api.unique_integrity_violated Then
247: -- Unique integrity has been violated
248: pay_ele_shd.g_api_dml := false; -- Unset the api dml status
249: pay_ele_shd.constraint_error

Line 246: When hr_api.unique_integrity_violated Then

242: -- A check constraint has been violated
243: pay_ele_shd.g_api_dml := false; -- Unset the api dml status
244: pay_ele_shd.constraint_error
245: (p_constraint_name => hr_api.strip_constraint_name(SQLERRM));
246: When hr_api.unique_integrity_violated Then
247: -- Unique integrity has been violated
248: pay_ele_shd.g_api_dml := false; -- Unset the api dml status
249: pay_ele_shd.constraint_error
250: (p_constraint_name => hr_api.strip_constraint_name(SQLERRM));

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

246: When hr_api.unique_integrity_violated Then
247: -- Unique integrity has been violated
248: pay_ele_shd.g_api_dml := false; -- Unset the api dml status
249: pay_ele_shd.constraint_error
250: (p_constraint_name => hr_api.strip_constraint_name(SQLERRM));
251: When Others Then
252: pay_ele_shd.g_api_dml := false; -- Unset the api dml status
253: Raise;
254: End dt_insert_dml;

Line 535: when hr_api.cannot_find_prog_unit then

531: );
532: --
533: exception
534: --
535: when hr_api.cannot_find_prog_unit then
536: --
537: hr_api.cannot_find_prog_unit_error
538: (p_module_name => 'PAY_ELEMENT_ENTRIES_F'
539: ,p_hook_type => 'AI');

Line 537: hr_api.cannot_find_prog_unit_error

533: exception
534: --
535: when hr_api.cannot_find_prog_unit then
536: --
537: hr_api.cannot_find_prog_unit_error
538: (p_module_name => 'PAY_ELEMENT_ENTRIES_F'
539: ,p_hook_type => 'AI');
540: --
541: end;

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

570: --
571: -- Post Failure:
572: -- The Lck process can fail for:
573: -- 1) When attempting to lock the row the row could already be locked by
574: -- another user. This will raise the HR_Api.Object_Locked exception.
575: -- 2) When attempting to the lock the parent which doesn't exist.
576: -- For the entity to be locked the parent must exist!
577: --
578: -- Developer Implementation Notes:

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

635: ,p_rec in out nocopy pay_ele_shd.g_rec_type
636: ) is
637: --
638: l_proc varchar2(72) := g_package||'ins';
639: l_datetrack_mode varchar2(30) := hr_api.g_insert;
640: l_validation_start_date date;
641: l_validation_end_date date;
642: --
643: Begin