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_GCF_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 227: When hr_api.check_integrity_violated Then

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

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

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

Line 232: When hr_api.unique_integrity_violated Then

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

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

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

Line 518: when hr_api.cannot_find_prog_unit then

514: );
515: --
516: exception
517: --
518: when hr_api.cannot_find_prog_unit then
519: --
520: hr_api.cannot_find_prog_unit_error
521: (p_module_name => 'AME_APPROVAL_GROUP_CONFIG'
522: ,p_hook_type => 'AI');

Line 520: hr_api.cannot_find_prog_unit_error

516: exception
517: --
518: when hr_api.cannot_find_prog_unit then
519: --
520: hr_api.cannot_find_prog_unit_error
521: (p_module_name => 'AME_APPROVAL_GROUP_CONFIG'
522: ,p_hook_type => 'AI');
523: --
524: end;

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

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

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

630: ,p_rec in out nocopy ame_gcf_shd.g_rec_type
631: ) is
632: --
633: l_proc varchar2(72) := g_package||'ins';
634: l_datetrack_mode varchar2(30) := hr_api.g_insert;
635: l_validation_start_date date;
636: l_validation_end_date date;
637: --
638: Begin