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

Line 317: When hr_api.check_integrity_violated Then

313: pay_cnt_shd.g_api_dml := false; -- Unset the api dml status
314: hr_utility.set_location(' Leaving:'||l_proc, 15);
315: --
316: Exception
317: When hr_api.check_integrity_violated Then
318: -- A check constraint has been violated
319: pay_cnt_shd.g_api_dml := false; -- Unset the api dml status
320: pay_cnt_shd.constraint_error
321: (p_constraint_name => hr_api.strip_constraint_name(SQLERRM));

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

317: When hr_api.check_integrity_violated Then
318: -- A check constraint has been violated
319: pay_cnt_shd.g_api_dml := false; -- Unset the api dml status
320: pay_cnt_shd.constraint_error
321: (p_constraint_name => hr_api.strip_constraint_name(SQLERRM));
322: When hr_api.unique_integrity_violated Then
323: -- Unique integrity has been violated
324: pay_cnt_shd.g_api_dml := false; -- Unset the api dml status
325: pay_cnt_shd.constraint_error

Line 322: When hr_api.unique_integrity_violated Then

318: -- A check constraint has been violated
319: pay_cnt_shd.g_api_dml := false; -- Unset the api dml status
320: pay_cnt_shd.constraint_error
321: (p_constraint_name => hr_api.strip_constraint_name(SQLERRM));
322: When hr_api.unique_integrity_violated Then
323: -- Unique integrity has been violated
324: pay_cnt_shd.g_api_dml := false; -- Unset the api dml status
325: pay_cnt_shd.constraint_error
326: (p_constraint_name => hr_api.strip_constraint_name(SQLERRM));

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

322: When hr_api.unique_integrity_violated Then
323: -- Unique integrity has been violated
324: pay_cnt_shd.g_api_dml := false; -- Unset the api dml status
325: pay_cnt_shd.constraint_error
326: (p_constraint_name => hr_api.strip_constraint_name(SQLERRM));
327: When Others Then
328: pay_cnt_shd.g_api_dml := false; -- Unset the api dml status
329: Raise;
330: End dt_insert_dml;

Line 499: when hr_api.cannot_find_prog_unit then

495: );
496: --
497: exception
498: --
499: when hr_api.cannot_find_prog_unit then
500: --
501: hr_api.cannot_find_prog_unit_error
502: (p_module_name => 'PAY_US_EMP_COUNTY_TAX_RULES_F'
503: ,p_hook_type => 'AI');

Line 501: hr_api.cannot_find_prog_unit_error

497: exception
498: --
499: when hr_api.cannot_find_prog_unit then
500: --
501: hr_api.cannot_find_prog_unit_error
502: (p_module_name => 'PAY_US_EMP_COUNTY_TAX_RULES_F'
503: ,p_hook_type => 'AI');
504: --
505: */

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

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