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

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

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

Line 213: When hr_api.check_integrity_violated Then

209: --
210: hr_utility.set_location(' Leaving:'||l_proc, 15);
211: --
212: Exception
213: When hr_api.check_integrity_violated Then
214: -- A check constraint has been violated
215: --
216: ame_itc_shd.constraint_error
217: (p_constraint_name => hr_api.strip_constraint_name(SQLERRM));

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

213: When hr_api.check_integrity_violated Then
214: -- A check constraint has been violated
215: --
216: ame_itc_shd.constraint_error
217: (p_constraint_name => hr_api.strip_constraint_name(SQLERRM));
218: When hr_api.unique_integrity_violated Then
219: -- Unique integrity has been violated
220: --
221: ame_itc_shd.constraint_error

Line 218: When hr_api.unique_integrity_violated Then

214: -- A check constraint has been violated
215: --
216: ame_itc_shd.constraint_error
217: (p_constraint_name => hr_api.strip_constraint_name(SQLERRM));
218: When hr_api.unique_integrity_violated Then
219: -- Unique integrity has been violated
220: --
221: ame_itc_shd.constraint_error
222: (p_constraint_name => hr_api.strip_constraint_name(SQLERRM));

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

218: When hr_api.unique_integrity_violated Then
219: -- Unique integrity has been violated
220: --
221: ame_itc_shd.constraint_error
222: (p_constraint_name => hr_api.strip_constraint_name(SQLERRM));
223: When Others Then
224: --
225: Raise;
226: End dt_insert_dml;

Line 417: when hr_api.cannot_find_prog_unit then

413: );
414: --
415: exception
416: --
417: when hr_api.cannot_find_prog_unit then
418: --
419: hr_api.cannot_find_prog_unit_error
420: (p_module_name => 'AME_ITEM_CLASSES'
421: ,p_hook_type => 'AI');

Line 419: hr_api.cannot_find_prog_unit_error

415: exception
416: --
417: when hr_api.cannot_find_prog_unit then
418: --
419: hr_api.cannot_find_prog_unit_error
420: (p_module_name => 'AME_ITEM_CLASSES'
421: ,p_hook_type => 'AI');
422: --
423: end;

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

448: --
449: -- Post Failure:
450: -- The Lck process can fail for:
451: -- 1) When attempting to lock the row the row could already be locked by
452: -- another user. This will raise the HR_Api.Object_Locked exception.
453: -- 2) When attempting to the lock the parent which doesn't exist.
454: -- For the entity to be locked the parent must exist!
455: --
456: -- Developer Implementation Notes:

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

497: ,p_rec in out nocopy ame_itc_shd.g_rec_type
498: ) is
499: --
500: l_proc varchar2(72) := g_package||'ins';
501: l_datetrack_mode varchar2(30) := hr_api.g_insert;
502: l_validation_start_date date;
503: l_validation_end_date date;
504: --
505: Begin