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

Line 125: If (p_datetrack_mode <> hr_api.g_insert) then

121: --
122: -- If the datetrack_mode is not INSERT then we must populate the WHO
123: -- columns with the 'old' creation values and 'new' updated values.
124: --
125: If (p_datetrack_mode <> hr_api.g_insert) then
126: hr_utility.set_location(l_proc, 10);
127: --
128: -- Select the 'old' created values
129: --

Line 203: When hr_api.check_integrity_violated Then

199: --
200: hr_utility.set_location(' Leaving:'||l_proc, 15);
201: --
202: Exception
203: When hr_api.check_integrity_violated Then
204: -- A check constraint has been violated
205: --
206: pay_evc_shd.constraint_error
207: (p_constraint_name => hr_api.strip_constraint_name(SQLERRM));

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

203: When hr_api.check_integrity_violated Then
204: -- A check constraint has been violated
205: --
206: pay_evc_shd.constraint_error
207: (p_constraint_name => hr_api.strip_constraint_name(SQLERRM));
208: When hr_api.unique_integrity_violated Then
209: -- Unique integrity has been violated
210: --
211: pay_evc_shd.constraint_error

Line 208: When hr_api.unique_integrity_violated Then

204: -- A check constraint has been violated
205: --
206: pay_evc_shd.constraint_error
207: (p_constraint_name => hr_api.strip_constraint_name(SQLERRM));
208: When hr_api.unique_integrity_violated Then
209: -- Unique integrity has been violated
210: --
211: pay_evc_shd.constraint_error
212: (p_constraint_name => hr_api.strip_constraint_name(SQLERRM));

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

208: When hr_api.unique_integrity_violated Then
209: -- Unique integrity has been violated
210: --
211: pay_evc_shd.constraint_error
212: (p_constraint_name => hr_api.strip_constraint_name(SQLERRM));
213: When Others Then
214: --
215: Raise;
216: End dt_insert_dml;

Line 483: when hr_api.cannot_find_prog_unit then

479: );
480: --
481: exception
482: --
483: when hr_api.cannot_find_prog_unit then
484: --
485: hr_api.cannot_find_prog_unit_error
486: (p_module_name => 'PAY_EVENT_VALUE_CHANGES_F'
487: ,p_hook_type => 'AI');

Line 485: hr_api.cannot_find_prog_unit_error

481: exception
482: --
483: when hr_api.cannot_find_prog_unit then
484: --
485: hr_api.cannot_find_prog_unit_error
486: (p_module_name => 'PAY_EVENT_VALUE_CHANGES_F'
487: ,p_hook_type => 'AI');
488: --
489: end;

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

514: --
515: -- Post Failure:
516: -- The Lck process can fail for:
517: -- 1) When attempting to lock the row the row could already be locked by
518: -- another user. This will raise the HR_Api.Object_Locked exception.
519: -- 2) When attempting to the lock the parent which doesn't exist.
520: -- For the entity to be locked the parent must exist!
521: --
522: -- Developer Implementation Notes:

Line 580: l_datetrack_mode varchar2(30) := hr_api.g_insert;

576: ,p_rec in out nocopy pay_evc_shd.g_rec_type
577: ) is
578: --
579: l_proc varchar2(72) := g_package||'ins';
580: l_datetrack_mode varchar2(30) := hr_api.g_insert;
581: l_validation_start_date date;
582: l_validation_end_date date;
583: --
584: Begin