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.BEN_PEI_INS dependencies on HR_API

Line 187: When hr_api.check_integrity_violated Then

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

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

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

Line 192: When hr_api.unique_integrity_violated Then

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

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

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

Line 362: when hr_api.cannot_find_prog_unit then

358: );
359: --
360: exception
361: --
362: when hr_api.cannot_find_prog_unit then
363: --
364: hr_api.cannot_find_prog_unit_error
365: (p_module_name => 'ben_pl_extract_identifier_f'
366: ,p_hook_type => 'AI');

Line 364: hr_api.cannot_find_prog_unit_error

360: exception
361: --
362: when hr_api.cannot_find_prog_unit then
363: --
364: hr_api.cannot_find_prog_unit_error
365: (p_module_name => 'ben_pl_extract_identifier_f'
366: ,p_hook_type => 'AI');
367: --
368: end;

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

396: --
397: -- Post Failure:
398: -- The Lck process can fail for:
399: -- 1) When attempting to lock the row the row could already be locked by
400: -- another user. This will raise the HR_Api.Object_Locked exception.
401: -- 2) When attempting to the lock the parent which doesn't exist.
402: -- For the entity to be locked the parent must exist!
403: --
404: -- Developer Implementation Notes: