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_EVQ_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 205: When hr_api.check_integrity_violated Then

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

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

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

Line 210: When hr_api.unique_integrity_violated Then

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

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

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

Line 487: when hr_api.cannot_find_prog_unit then

483: );
484: --
485: exception
486: --
487: when hr_api.cannot_find_prog_unit then
488: --
489: hr_api.cannot_find_prog_unit_error
490: (p_module_name => 'PAY_EVENT_QUALIFIERS_F'
491: ,p_hook_type => 'AI');

Line 489: hr_api.cannot_find_prog_unit_error

485: exception
486: --
487: when hr_api.cannot_find_prog_unit then
488: --
489: hr_api.cannot_find_prog_unit_error
490: (p_module_name => 'PAY_EVENT_QUALIFIERS_F'
491: ,p_hook_type => 'AI');
492: --
493: end;

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

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

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

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