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

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

175: --
176: -- If the datetrack_mode is not INSERT then we must populate the WHO
177: -- columns with the 'old' creation values and 'new' updated values.
178: --
179: If (p_datetrack_mode <> hr_api.g_insert) then
180: hr_utility.set_location(l_proc, 10);
181: --
182: -- Get the object version number for the insert
183: --

Line 293: When hr_api.check_integrity_violated Then

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

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

293: When hr_api.check_integrity_violated Then
294: -- A check constraint has been violated
295: --
296: ame_rul_shd.constraint_error
297: (p_constraint_name => hr_api.strip_constraint_name(SQLERRM));
298: When hr_api.unique_integrity_violated Then
299: -- Unique integrity has been violated
300: --
301: ame_rul_shd.constraint_error

Line 298: When hr_api.unique_integrity_violated Then

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

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

298: When hr_api.unique_integrity_violated Then
299: -- Unique integrity has been violated
300: --
301: ame_rul_shd.constraint_error
302: (p_constraint_name => hr_api.strip_constraint_name(SQLERRM));
303: When Others Then
304: --
305: Raise;
306: End dt_insert_dml;

Line 522: when hr_api.cannot_find_prog_unit then

518: );
519: --
520: exception
521: --
522: when hr_api.cannot_find_prog_unit then
523: --
524: hr_api.cannot_find_prog_unit_error
525: (p_module_name => 'AME_RULES'
526: ,p_hook_type => 'AI');

Line 524: hr_api.cannot_find_prog_unit_error

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

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

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

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

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