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

Line 188: When hr_api.check_integrity_violated Then

184: pay_grr_shd.g_api_dml := false; -- Unset the api dml status
185: hr_utility.set_location(' Leaving:'||l_proc, 15);
186: --
187: Exception
188: When hr_api.check_integrity_violated Then
189: -- A check constraint has been violated
190: pay_grr_shd.g_api_dml := false; -- Unset the api dml status
191: pay_grr_shd.constraint_error
192: (p_constraint_name => hr_api.strip_constraint_name(SQLERRM));

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

188: When hr_api.check_integrity_violated Then
189: -- A check constraint has been violated
190: pay_grr_shd.g_api_dml := false; -- Unset the api dml status
191: pay_grr_shd.constraint_error
192: (p_constraint_name => hr_api.strip_constraint_name(SQLERRM));
193: When hr_api.unique_integrity_violated Then
194: -- Unique integrity has been violated
195: pay_grr_shd.g_api_dml := false; -- Unset the api dml status
196: pay_grr_shd.constraint_error

Line 193: When hr_api.unique_integrity_violated Then

189: -- A check constraint has been violated
190: pay_grr_shd.g_api_dml := false; -- Unset the api dml status
191: pay_grr_shd.constraint_error
192: (p_constraint_name => hr_api.strip_constraint_name(SQLERRM));
193: When hr_api.unique_integrity_violated Then
194: -- Unique integrity has been violated
195: pay_grr_shd.g_api_dml := false; -- Unset the api dml status
196: pay_grr_shd.constraint_error
197: (p_constraint_name => hr_api.strip_constraint_name(SQLERRM));

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

193: When hr_api.unique_integrity_violated Then
194: -- Unique integrity has been violated
195: pay_grr_shd.g_api_dml := false; -- Unset the api dml status
196: pay_grr_shd.constraint_error
197: (p_constraint_name => hr_api.strip_constraint_name(SQLERRM));
198: When Others Then
199: pay_grr_shd.g_api_dml := false; -- Unset the api dml status
200: Raise;
201: End dt_insert_dml;

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

359: --
360: -- Post Failure:
361: -- The Lck process can fail for:
362: -- 1) When attempting to lock the row the row could already be locked by
363: -- another user. This will raise the HR_Api.Object_Locked exception.
364: -- 2) When attempting to the lock the parent which doesn't exist.
365: -- For the entity to be locked the parent must exist!
366: --
367: -- Developer Implementation Notes:

Line 486: Raise HR_Api.Validate_Enabled;

482: --
483: -- If we are validating then raise the Validate_Enabled exception
484: --
485: If p_validate then
486: Raise HR_Api.Validate_Enabled;
487: End If;
488: --
489: hr_utility.set_location(' Leaving:'||l_proc, 10);
490: Exception

Line 491: When HR_Api.Validate_Enabled Then

487: End If;
488: --
489: hr_utility.set_location(' Leaving:'||l_proc, 10);
490: Exception
491: When HR_Api.Validate_Enabled Then
492: --
493: -- As the Validate_Enabled exception has been raised
494: -- we must rollback to the savepoint
495: --