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_APU_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 222: When hr_api.check_integrity_violated Then

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

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

222: When hr_api.check_integrity_violated Then
223: -- A check constraint has been violated
224: --
225: ame_apu_shd.constraint_error
226: (p_constraint_name => hr_api.strip_constraint_name(SQLERRM));
227: When hr_api.unique_integrity_violated Then
228: -- Unique integrity has been violated
229: --
230: ame_apu_shd.constraint_error

Line 227: When hr_api.unique_integrity_violated Then

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

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

227: When hr_api.unique_integrity_violated Then
228: -- Unique integrity has been violated
229: --
230: ame_apu_shd.constraint_error
231: (p_constraint_name => hr_api.strip_constraint_name(SQLERRM));
232: When Others Then
233: --
234: Raise;
235: End dt_insert_dml;

Line 439: when hr_api.cannot_find_prog_unit then

435: );
436: --
437: exception
438: --
439: when hr_api.cannot_find_prog_unit then
440: --
441: hr_api.cannot_find_prog_unit_error
442: (p_module_name => 'AME_APPROVER_TYPE_USAGES'
443: ,p_hook_type => 'AI');

Line 441: hr_api.cannot_find_prog_unit_error

437: exception
438: --
439: when hr_api.cannot_find_prog_unit then
440: --
441: hr_api.cannot_find_prog_unit_error
442: (p_module_name => 'AME_APPROVER_TYPE_USAGES'
443: ,p_hook_type => 'AI');
444: --
445: end;

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

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

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

534: ,p_rec in out nocopy ame_apu_shd.g_rec_type
535: ) is
536: --
537: l_proc varchar2(72) := g_package||'ins';
538: l_datetrack_mode varchar2(30) := hr_api.g_insert;
539: l_validation_start_date date;
540: l_validation_end_date date;
541: --
542: Begin