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

Line 328: When hr_api.check_integrity_violated Then

324: pay_sta_shd.g_api_dml := false; -- Unset the api dml status
325: hr_utility.set_location(' Leaving:'||l_proc, 15);
326: --
327: Exception
328: When hr_api.check_integrity_violated Then
329: -- A check constraint has been violated
330: pay_sta_shd.g_api_dml := false; -- Unset the api dml status
331: pay_sta_shd.constraint_error
332: (p_constraint_name => hr_api.strip_constraint_name(SQLERRM));

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

328: When hr_api.check_integrity_violated Then
329: -- A check constraint has been violated
330: pay_sta_shd.g_api_dml := false; -- Unset the api dml status
331: pay_sta_shd.constraint_error
332: (p_constraint_name => hr_api.strip_constraint_name(SQLERRM));
333: When hr_api.unique_integrity_violated Then
334: -- Unique integrity has been violated
335: pay_sta_shd.g_api_dml := false; -- Unset the api dml status
336: pay_sta_shd.constraint_error

Line 333: When hr_api.unique_integrity_violated Then

329: -- A check constraint has been violated
330: pay_sta_shd.g_api_dml := false; -- Unset the api dml status
331: pay_sta_shd.constraint_error
332: (p_constraint_name => hr_api.strip_constraint_name(SQLERRM));
333: When hr_api.unique_integrity_violated Then
334: -- Unique integrity has been violated
335: pay_sta_shd.g_api_dml := false; -- Unset the api dml status
336: pay_sta_shd.constraint_error
337: (p_constraint_name => hr_api.strip_constraint_name(SQLERRM));

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

333: When hr_api.unique_integrity_violated Then
334: -- Unique integrity has been violated
335: pay_sta_shd.g_api_dml := false; -- Unset the api dml status
336: pay_sta_shd.constraint_error
337: (p_constraint_name => hr_api.strip_constraint_name(SQLERRM));
338: When Others Then
339: pay_sta_shd.g_api_dml := false; -- Unset the api dml status
340: Raise;
341: End dt_insert_dml;

Line 515: when hr_api.cannot_find_prog_unit then

511: );
512: --
513: exception
514: --
515: when hr_api.cannot_find_prog_unit then
516: --
517: hr_api.cannot_find_prog_unit_error
518: (p_module_name => 'PAY_US_EMP_STATE_TAX_RULES_F
519: ,p_hook_type => 'AI');

Line 517: hr_api.cannot_find_prog_unit_error

513: exception
514: --
515: when hr_api.cannot_find_prog_unit then
516: --
517: hr_api.cannot_find_prog_unit_error
518: (p_module_name => 'PAY_US_EMP_STATE_TAX_RULES_F
519: ,p_hook_type => 'AI');
520: --
521: */

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

553: --
554: -- Post Failure:
555: -- The Lck process can fail for:
556: -- 1) When attempting to lock the row the row could already be locked by
557: -- another user. This will raise the HR_Api.Object_Locked exception.
558: -- 2) When attempting to the lock the parent which doesn't exist.
559: -- For the entity to be locked the parent must exist!
560: --
561: -- Developer Implementation Notes: