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_RLU_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 243: When hr_api.check_integrity_violated Then

239: --
240: hr_utility.set_location(' Leaving:'||l_proc, 15);
241: --
242: Exception
243: When hr_api.check_integrity_violated Then
244: -- A check constraint has been violated
245: --
246: ame_rlu_shd.constraint_error
247: (p_constraint_name => hr_api.strip_constraint_name(SQLERRM));

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

243: When hr_api.check_integrity_violated Then
244: -- A check constraint has been violated
245: --
246: ame_rlu_shd.constraint_error
247: (p_constraint_name => hr_api.strip_constraint_name(SQLERRM));
248: When hr_api.unique_integrity_violated Then
249: -- Unique integrity has been violated
250: --
251: ame_rlu_shd.constraint_error

Line 248: When hr_api.unique_integrity_violated Then

244: -- A check constraint has been violated
245: --
246: ame_rlu_shd.constraint_error
247: (p_constraint_name => hr_api.strip_constraint_name(SQLERRM));
248: When hr_api.unique_integrity_violated Then
249: -- Unique integrity has been violated
250: --
251: ame_rlu_shd.constraint_error
252: (p_constraint_name => hr_api.strip_constraint_name(SQLERRM));

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

248: When hr_api.unique_integrity_violated Then
249: -- Unique integrity has been violated
250: --
251: ame_rlu_shd.constraint_error
252: (p_constraint_name => hr_api.strip_constraint_name(SQLERRM));
253: When Others Then
254: --
255: Raise;
256: End dt_insert_dml;

Line 457: when hr_api.cannot_find_prog_unit then

453: );
454: --
455: exception
456: --
457: when hr_api.cannot_find_prog_unit then
458: --
459: hr_api.cannot_find_prog_unit_error
460: (p_module_name => 'AME_RULE_USAGES'
461: ,p_hook_type => 'AI');

Line 459: hr_api.cannot_find_prog_unit_error

455: exception
456: --
457: when hr_api.cannot_find_prog_unit then
458: --
459: hr_api.cannot_find_prog_unit_error
460: (p_module_name => 'AME_RULE_USAGES'
461: ,p_hook_type => 'AI');
462: --
463: end;

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

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

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

562: ,p_rec in out nocopy ame_rlu_shd.g_rec_type
563: ) is
564: --
565: l_proc varchar2(72) := g_package||'ins';
566: l_datetrack_mode varchar2(30) := hr_api.g_insert;
567: l_validation_start_date date;
568: l_validation_end_date date;
569: --
570: Begin