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_PEL_INS dependencies on HR_API

Line 125: If (p_datetrack_mode <> hr_api.g_insert) then

121: --
122: -- If the datetrack_mode is not INSERT then we must populate the WHO
123: -- columns with the 'old' creation values and 'new' updated values.
124: --
125: If (p_datetrack_mode <> hr_api.g_insert) then
126:
127: --
128: -- Select the 'old' created values
129: --

Line 271: When hr_api.check_integrity_violated Then

267: pay_pel_shd.g_api_dml := false; -- Unset the api dml status
268: hr_utility.set_location(' Leaving:'||l_proc, 15);
269: --
270: Exception
271: When hr_api.check_integrity_violated Then
272: -- A check constraint has been violated
273: pay_pel_shd.g_api_dml := false; -- Unset the api dml status
274: pay_pel_shd.constraint_error
275: (p_constraint_name => hr_api.strip_constraint_name(SQLERRM));

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

271: When hr_api.check_integrity_violated Then
272: -- A check constraint has been violated
273: pay_pel_shd.g_api_dml := false; -- Unset the api dml status
274: pay_pel_shd.constraint_error
275: (p_constraint_name => hr_api.strip_constraint_name(SQLERRM));
276: When hr_api.unique_integrity_violated Then
277: -- Unique integrity has been violated
278: pay_pel_shd.g_api_dml := false; -- Unset the api dml status
279: pay_pel_shd.constraint_error

Line 276: When hr_api.unique_integrity_violated Then

272: -- A check constraint has been violated
273: pay_pel_shd.g_api_dml := false; -- Unset the api dml status
274: pay_pel_shd.constraint_error
275: (p_constraint_name => hr_api.strip_constraint_name(SQLERRM));
276: When hr_api.unique_integrity_violated Then
277: -- Unique integrity has been violated
278: pay_pel_shd.g_api_dml := false; -- Unset the api dml status
279: pay_pel_shd.constraint_error
280: (p_constraint_name => hr_api.strip_constraint_name(SQLERRM));

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

276: When hr_api.unique_integrity_violated Then
277: -- Unique integrity has been violated
278: pay_pel_shd.g_api_dml := false; -- Unset the api dml status
279: pay_pel_shd.constraint_error
280: (p_constraint_name => hr_api.strip_constraint_name(SQLERRM));
281: When Others Then
282: pay_pel_shd.g_api_dml := false; -- Unset the api dml status
283: Raise;
284: End dt_insert_dml;

Line 576: when hr_api.cannot_find_prog_unit then

572: );
573: --
574: exception
575: --
576: when hr_api.cannot_find_prog_unit then
577: --
578: hr_api.cannot_find_prog_unit_error
579: (p_module_name => 'PAY_ELEMENT_LINKS_F'
580: ,p_hook_type => 'AI');

Line 578: hr_api.cannot_find_prog_unit_error

574: exception
575: --
576: when hr_api.cannot_find_prog_unit then
577: --
578: hr_api.cannot_find_prog_unit_error
579: (p_module_name => 'PAY_ELEMENT_LINKS_F'
580: ,p_hook_type => 'AI');
581: --
582: end;

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

607: --
608: -- Post Failure:
609: -- The Lck process can fail for:
610: -- 1) When attempting to lock the row the row could already be locked by
611: -- another user. This will raise the HR_Api.Object_Locked exception.
612: -- 2) When attempting to the lock the parent which doesn't exist.
613: -- For the entity to be locked the parent must exist!
614: --
615: -- Developer Implementation Notes:

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

672: ,p_rec in out nocopy pay_pel_shd.g_rec_type
673: ) is
674: --
675: l_proc varchar2(72) := g_package||'ins';
676: l_datetrack_mode varchar2(30) := hr_api.g_insert;
677: l_validation_start_date date;
678: l_validation_end_date date;
679: --
680: Begin