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

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

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

Line 230: When hr_api.check_integrity_violated Then

226: --
227: hr_utility.set_location(' Leaving:'||l_proc, 15);
228: --
229: Exception
230: When hr_api.check_integrity_violated Then
231: -- A check constraint has been violated
232: --
233: ame_itu_shd.constraint_error
234: (p_constraint_name => hr_api.strip_constraint_name(SQLERRM));

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

230: When hr_api.check_integrity_violated Then
231: -- A check constraint has been violated
232: --
233: ame_itu_shd.constraint_error
234: (p_constraint_name => hr_api.strip_constraint_name(SQLERRM));
235: When hr_api.unique_integrity_violated Then
236: -- Unique integrity has been violated
237: --
238: ame_itu_shd.constraint_error

Line 235: When hr_api.unique_integrity_violated Then

231: -- A check constraint has been violated
232: --
233: ame_itu_shd.constraint_error
234: (p_constraint_name => hr_api.strip_constraint_name(SQLERRM));
235: When hr_api.unique_integrity_violated Then
236: -- Unique integrity has been violated
237: --
238: ame_itu_shd.constraint_error
239: (p_constraint_name => hr_api.strip_constraint_name(SQLERRM));

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

235: When hr_api.unique_integrity_violated Then
236: -- Unique integrity has been violated
237: --
238: ame_itu_shd.constraint_error
239: (p_constraint_name => hr_api.strip_constraint_name(SQLERRM));
240: When Others Then
241: --
242: Raise;
243: End dt_insert_dml;

Line 444: when hr_api.cannot_find_prog_unit then

440: );
441: --
442: exception
443: --
444: when hr_api.cannot_find_prog_unit then
445: --
446: hr_api.cannot_find_prog_unit_error
447: (p_module_name => 'AME_ITEM_CLASS_USAGES'
448: ,p_hook_type => 'AI');

Line 446: hr_api.cannot_find_prog_unit_error

442: exception
443: --
444: when hr_api.cannot_find_prog_unit then
445: --
446: hr_api.cannot_find_prog_unit_error
447: (p_module_name => 'AME_ITEM_CLASS_USAGES'
448: ,p_hook_type => 'AI');
449: --
450: end;

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

475: --
476: -- Post Failure:
477: -- The Lck process can fail for:
478: -- 1) When attempting to lock the row the row could already be locked by
479: -- another user. This will raise the HR_Api.Object_Locked exception.
480: -- 2) When attempting to the lock the parent which doesn't exist.
481: -- For the entity to be locked the parent must exist!
482: --
483: -- Developer Implementation Notes:

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

527: ,p_rec in out nocopy ame_itu_shd.g_rec_type
528: ) is
529: --
530: l_proc varchar2(72) := g_package||'ins';
531: l_datetrack_mode varchar2(30) := hr_api.g_insert;
532: l_validation_start_date date;
533: l_validation_end_date date;
534: --
535: Begin