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_CFV_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 229: When hr_api.check_integrity_violated Then

225: --
226: hr_utility.set_location(' Leaving:'||l_proc, 15);
227: --
228: Exception
229: When hr_api.check_integrity_violated Then
230: -- A check constraint has been violated
231: --
232: ame_cfv_shd.constraint_error
233: (p_constraint_name => hr_api.strip_constraint_name(SQLERRM));

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

229: When hr_api.check_integrity_violated Then
230: -- A check constraint has been violated
231: --
232: ame_cfv_shd.constraint_error
233: (p_constraint_name => hr_api.strip_constraint_name(SQLERRM));
234: When hr_api.unique_integrity_violated Then
235: -- Unique integrity has been violated
236: --
237: ame_cfv_shd.constraint_error

Line 234: When hr_api.unique_integrity_violated Then

230: -- A check constraint has been violated
231: --
232: ame_cfv_shd.constraint_error
233: (p_constraint_name => hr_api.strip_constraint_name(SQLERRM));
234: When hr_api.unique_integrity_violated Then
235: -- Unique integrity has been violated
236: --
237: ame_cfv_shd.constraint_error
238: (p_constraint_name => hr_api.strip_constraint_name(SQLERRM));

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

234: When hr_api.unique_integrity_violated Then
235: -- Unique integrity has been violated
236: --
237: ame_cfv_shd.constraint_error
238: (p_constraint_name => hr_api.strip_constraint_name(SQLERRM));
239: When Others Then
240: --
241: Raise;
242: End dt_insert_dml;

Line 452: when hr_api.cannot_find_prog_unit then

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

Line 454: hr_api.cannot_find_prog_unit_error

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

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

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

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

535: ,p_rec in out nocopy ame_cfv_shd.g_rec_type
536: ) is
537: --
538: l_proc varchar2(72) := g_package||'ins';
539: l_datetrack_mode varchar2(30) := hr_api.g_insert;
540: l_validation_start_date date;
541: l_validation_end_date date;
542: --
543: Begin