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_IPD_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 269: When hr_api.check_integrity_violated Then

265: --
266: hr_utility.set_location(' Leaving:'||l_proc, 15);
267: --
268: Exception
269: When hr_api.check_integrity_violated Then
270: -- A check constraint has been violated
271: --
272: pay_ipd_shd.constraint_error
273: (p_constraint_name => hr_api.strip_constraint_name(SQLERRM));

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

269: When hr_api.check_integrity_violated Then
270: -- A check constraint has been violated
271: --
272: pay_ipd_shd.constraint_error
273: (p_constraint_name => hr_api.strip_constraint_name(SQLERRM));
274: When hr_api.unique_integrity_violated Then
275: -- Unique integrity has been violated
276: --
277: pay_ipd_shd.constraint_error

Line 274: When hr_api.unique_integrity_violated Then

270: -- A check constraint has been violated
271: --
272: pay_ipd_shd.constraint_error
273: (p_constraint_name => hr_api.strip_constraint_name(SQLERRM));
274: When hr_api.unique_integrity_violated Then
275: -- Unique integrity has been violated
276: --
277: pay_ipd_shd.constraint_error
278: (p_constraint_name => hr_api.strip_constraint_name(SQLERRM));

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

274: When hr_api.unique_integrity_violated Then
275: -- Unique integrity has been violated
276: --
277: pay_ipd_shd.constraint_error
278: (p_constraint_name => hr_api.strip_constraint_name(SQLERRM));
279: When Others Then
280: --
281: Raise;
282: End dt_insert_dml;

Line 473: when hr_api.cannot_find_prog_unit then

469: );
470: --
471: exception
472: --
473: when hr_api.cannot_find_prog_unit then
474: --
475: hr_api.cannot_find_prog_unit_error
476: (p_module_name => 'PAY_IE_PAYE_DETAILS_F'
477: ,p_hook_type => 'AI');

Line 475: hr_api.cannot_find_prog_unit_error

471: exception
472: --
473: when hr_api.cannot_find_prog_unit then
474: --
475: hr_api.cannot_find_prog_unit_error
476: (p_module_name => 'PAY_IE_PAYE_DETAILS_F'
477: ,p_hook_type => 'AI');
478: --
479: end;

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

504: --
505: -- Post Failure:
506: -- The Lck process can fail for:
507: -- 1) When attempting to lock the row the row could already be locked by
508: -- another user. This will raise the HR_Api.Object_Locked exception.
509: -- 2) When attempting to the lock the parent which doesn't exist.
510: -- For the entity to be locked the parent must exist!
511: --
512: -- Developer Implementation Notes:

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

566: ,p_rec in out nocopy pay_ipd_shd.g_rec_type
567: ) is
568: --
569: l_proc varchar2(72) := g_package||'ins';
570: l_datetrack_mode varchar2(30) := hr_api.g_insert;
571: l_validation_start_date date;
572: l_validation_end_date date;
573: --
574: Begin