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

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

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

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_stv_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_stv_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_stv_shd.constraint_error

Line 230: When hr_api.unique_integrity_violated Then

226: -- A check constraint has been violated
227: --
228: ame_stv_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_stv_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_stv_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 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_STRING_VALUES'
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_STRING_VALUES'
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 551: l_datetrack_mode varchar2(30) := hr_api.g_insert;

547: ,p_rec in out nocopy ame_stv_shd.g_rec_type
548: ) is
549: --
550: l_proc varchar2(72) := g_package||'ins';
551: l_datetrack_mode varchar2(30) := hr_api.g_insert;
552: l_validation_start_date date;
553: l_validation_end_date date;
554: --
555: Begin