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

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

184: --
185: -- If the datetrack_mode is not INSERT then we must populate the WHO
186: -- columns with the 'old' creation values and 'new' updated values.
187: --
188: If (p_datetrack_mode <> hr_api.g_insert) then
189: hr_utility.set_location(l_proc, 10);
190: --
191: -- Get the object version number for the insert
192: --

Line 296: When hr_api.check_integrity_violated Then

292: --
293: hr_utility.set_location(' Leaving:'||l_proc, 15);
294: --
295: Exception
296: When hr_api.check_integrity_violated Then
297: -- A check constraint has been violated
298: --
299: ame_con_shd.constraint_error
300: (p_constraint_name => hr_api.strip_constraint_name(SQLERRM));

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

296: When hr_api.check_integrity_violated Then
297: -- A check constraint has been violated
298: --
299: ame_con_shd.constraint_error
300: (p_constraint_name => hr_api.strip_constraint_name(SQLERRM));
301: When hr_api.unique_integrity_violated Then
302: -- Unique integrity has been violated
303: --
304: ame_con_shd.constraint_error

Line 301: When hr_api.unique_integrity_violated Then

297: -- A check constraint has been violated
298: --
299: ame_con_shd.constraint_error
300: (p_constraint_name => hr_api.strip_constraint_name(SQLERRM));
301: When hr_api.unique_integrity_violated Then
302: -- Unique integrity has been violated
303: --
304: ame_con_shd.constraint_error
305: (p_constraint_name => hr_api.strip_constraint_name(SQLERRM));

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

301: When hr_api.unique_integrity_violated Then
302: -- Unique integrity has been violated
303: --
304: ame_con_shd.constraint_error
305: (p_constraint_name => hr_api.strip_constraint_name(SQLERRM));
306: When Others Then
307: --
308: Raise;
309: End dt_insert_dml;

Line 525: when hr_api.cannot_find_prog_unit then

521: );
522: --
523: exception
524: --
525: when hr_api.cannot_find_prog_unit then
526: --
527: hr_api.cannot_find_prog_unit_error
528: (p_module_name => 'AME_CONDITIONS'
529: ,p_hook_type => 'AI');

Line 527: hr_api.cannot_find_prog_unit_error

523: exception
524: --
525: when hr_api.cannot_find_prog_unit then
526: --
527: hr_api.cannot_find_prog_unit_error
528: (p_module_name => 'AME_CONDITIONS'
529: ,p_hook_type => 'AI');
530: --
531: end;

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

556: --
557: -- Post Failure:
558: -- The Lck process can fail for:
559: -- 1) When attempting to lock the row the row could already be locked by
560: -- another user. This will raise the HR_Api.Object_Locked exception.
561: -- 2) When attempting to the lock the parent which doesn't exist.
562: -- For the entity to be locked the parent must exist!
563: --
564: -- Developer Implementation Notes:

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

608: ,p_rec in out nocopy ame_con_shd.g_rec_type
609: ) is
610: --
611: l_proc varchar2(72) := g_package||'ins';
612: l_datetrack_mode varchar2(30) := hr_api.g_insert;
613: l_validation_start_date date;
614: l_validation_end_date date;
615: --
616: Begin