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_GPI_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: -- Get the object version number for the insert
129: --

Line 225: When hr_api.check_integrity_violated Then

221: --
222: hr_utility.set_location(' Leaving:'||l_proc, 15);
223: --
224: Exception
225: When hr_api.check_integrity_violated Then
226: -- A check constraint has been violated
227: --
228: ame_gpi_shd.constraint_error
229: (p_constraint_name => hr_api.strip_constraint_name(SQLERRM));

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

225: When hr_api.check_integrity_violated Then
226: -- A check constraint has been violated
227: --
228: ame_gpi_shd.constraint_error
229: (p_constraint_name => hr_api.strip_constraint_name(SQLERRM));
230: When hr_api.unique_integrity_violated Then
231: -- Unique integrity has been violated
232: --
233: ame_gpi_shd.constraint_error

Line 230: When hr_api.unique_integrity_violated Then

226: -- A check constraint has been violated
227: --
228: ame_gpi_shd.constraint_error
229: (p_constraint_name => hr_api.strip_constraint_name(SQLERRM));
230: When hr_api.unique_integrity_violated Then
231: -- Unique integrity has been violated
232: --
233: ame_gpi_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.unique_integrity_violated Then
231: -- Unique integrity has been violated
232: --
233: ame_gpi_shd.constraint_error
234: (p_constraint_name => hr_api.strip_constraint_name(SQLERRM));
235: When Others Then
236: --
237: Raise;
238: End dt_insert_dml;

Line 443: when hr_api.cannot_find_prog_unit then

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

Line 445: hr_api.cannot_find_prog_unit_error

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

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

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

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

543: ,p_rec in out nocopy ame_gpi_shd.g_rec_type
544: ) is
545: --
546: l_proc varchar2(72) := g_package||'ins';
547: l_datetrack_mode varchar2(30) := hr_api.g_insert;
548: l_validation_start_date date;
549: l_validation_end_date date;
550: --
551: Begin