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_ATU_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 235: When hr_api.check_integrity_violated Then

231: --
232: hr_utility.set_location(' Leaving:'||l_proc, 15);
233: --
234: Exception
235: When hr_api.check_integrity_violated Then
236: -- A check constraint has been violated
237: --
238: ame_atu_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.check_integrity_violated Then
236: -- A check constraint has been violated
237: --
238: ame_atu_shd.constraint_error
239: (p_constraint_name => hr_api.strip_constraint_name(SQLERRM));
240: When hr_api.unique_integrity_violated Then
241: -- Unique integrity has been violated
242: --
243: ame_atu_shd.constraint_error

Line 240: When hr_api.unique_integrity_violated Then

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

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

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

Line 451: when hr_api.cannot_find_prog_unit then

447: );
448: --
449: exception
450: --
451: when hr_api.cannot_find_prog_unit then
452: --
453: hr_api.cannot_find_prog_unit_error
454: (p_module_name => 'AME_ATTRIBUTE_USAGES'
455: ,p_hook_type => 'AI');

Line 453: hr_api.cannot_find_prog_unit_error

449: exception
450: --
451: when hr_api.cannot_find_prog_unit then
452: --
453: hr_api.cannot_find_prog_unit_error
454: (p_module_name => 'AME_ATTRIBUTE_USAGES'
455: ,p_hook_type => 'AI');
456: --
457: end;

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

482: --
483: -- Post Failure:
484: -- The Lck process can fail for:
485: -- 1) When attempting to lock the row the row could already be locked by
486: -- another user. This will raise the HR_Api.Object_Locked exception.
487: -- 2) When attempting to the lock the parent which doesn't exist.
488: -- For the entity to be locked the parent must exist!
489: --
490: -- Developer Implementation Notes:

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

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