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_ACU_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 233: When hr_api.check_integrity_violated Then

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

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

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

Line 238: When hr_api.unique_integrity_violated Then

234: -- A check constraint has been violated
235: --
236: ame_acu_shd.constraint_error
237: (p_constraint_name => hr_api.strip_constraint_name(SQLERRM));
238: When hr_api.unique_integrity_violated Then
239: -- Unique integrity has been violated
240: --
241: ame_acu_shd.constraint_error
242: (p_constraint_name => hr_api.strip_constraint_name(SQLERRM));

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

238: When hr_api.unique_integrity_violated Then
239: -- Unique integrity has been violated
240: --
241: ame_acu_shd.constraint_error
242: (p_constraint_name => hr_api.strip_constraint_name(SQLERRM));
243: When Others Then
244: --
245: Raise;
246: End dt_insert_dml;

Line 442: when hr_api.cannot_find_prog_unit then

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

Line 444: hr_api.cannot_find_prog_unit_error

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

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

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

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

554: ,p_rec in out nocopy ame_acu_shd.g_rec_type
555: ) is
556: --
557: l_proc varchar2(72) := g_package||'ins';
558: l_datetrack_mode varchar2(30) := hr_api.g_insert;
559: l_validation_start_date date;
560: l_validation_end_date date;
561: --
562: Begin