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

Line 280: When hr_api.check_integrity_violated Then

276: pay_cpt_shd.g_api_dml := false; -- Unset the api dml status
277: hr_utility.set_location(' Leaving:'||l_proc, 15);
278: --
279: Exception
280: When hr_api.check_integrity_violated Then
281: -- A check constraint has been violated
282: pay_cpt_shd.g_api_dml := false; -- Unset the api dml status
283: pay_cpt_shd.constraint_error
284: (p_constraint_name => hr_api.strip_constraint_name(SQLERRM));

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

280: When hr_api.check_integrity_violated Then
281: -- A check constraint has been violated
282: pay_cpt_shd.g_api_dml := false; -- Unset the api dml status
283: pay_cpt_shd.constraint_error
284: (p_constraint_name => hr_api.strip_constraint_name(SQLERRM));
285: When hr_api.unique_integrity_violated Then
286: -- Unique integrity has been violated
287: pay_cpt_shd.g_api_dml := false; -- Unset the api dml status
288: pay_cpt_shd.constraint_error

Line 285: When hr_api.unique_integrity_violated Then

281: -- A check constraint has been violated
282: pay_cpt_shd.g_api_dml := false; -- Unset the api dml status
283: pay_cpt_shd.constraint_error
284: (p_constraint_name => hr_api.strip_constraint_name(SQLERRM));
285: When hr_api.unique_integrity_violated Then
286: -- Unique integrity has been violated
287: pay_cpt_shd.g_api_dml := false; -- Unset the api dml status
288: pay_cpt_shd.constraint_error
289: (p_constraint_name => hr_api.strip_constraint_name(SQLERRM));

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

285: When hr_api.unique_integrity_violated Then
286: -- Unique integrity has been violated
287: pay_cpt_shd.g_api_dml := false; -- Unset the api dml status
288: pay_cpt_shd.constraint_error
289: (p_constraint_name => hr_api.strip_constraint_name(SQLERRM));
290: When Others Then
291: pay_cpt_shd.g_api_dml := false; -- Unset the api dml status
292: Raise;
293: End dt_insert_dml;

Line 505: when hr_api.cannot_find_prog_unit then

501: );
502: --
503: exception
504: --
505: when hr_api.cannot_find_prog_unit then
506: --
507: hr_api.cannot_find_prog_unit_error
508: (p_module_name => 'pay_ca_emp_prov_tax_info_f'
509: ,p_hook_type => 'AI');

Line 507: hr_api.cannot_find_prog_unit_error

503: exception
504: --
505: when hr_api.cannot_find_prog_unit then
506: --
507: hr_api.cannot_find_prog_unit_error
508: (p_module_name => 'pay_ca_emp_prov_tax_info_f'
509: ,p_hook_type => 'AI');
510: --
511: end;

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

540: --
541: -- Post Failure:
542: -- The Lck process can fail for:
543: -- 1) When attempting to lock the row the row could already be locked by
544: -- another user. This will raise the HR_Api.Object_Locked exception.
545: -- 2) When attempting to the lock the parent which doesn't exist.
546: -- For the entity to be locked the parent must exist<>
547: --
548: -- Developer Implementation Notes: