APPS.AME_ATY_INS dependencies on HR_API

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

120: --
121: -- If the datetrack_mode is not INSERT then we must populate the WHO
122: -- columns with the 'old' creation values and 'new' updated values.
123: --
124: If (p_datetrack_mode <> hr_api.g_insert) then
125: hr_utility.set_location(l_proc, 10);
126: --
127: -- Get the object version number for the insert
128: --

Line 228: When hr_api.check_integrity_violated Then

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

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

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

Line 233: When hr_api.unique_integrity_violated Then

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

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

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

Line 446: when hr_api.cannot_find_prog_unit then

442: );
443: --
444: exception
445: --
446: when hr_api.cannot_find_prog_unit then
447: --
448: hr_api.cannot_find_prog_unit_error
449: (p_module_name => 'AME_ACTION_TYPES'
450: ,p_hook_type => 'AI');

Line 448: hr_api.cannot_find_prog_unit_error

444: exception
445: --
446: when hr_api.cannot_find_prog_unit then
447: --
448: hr_api.cannot_find_prog_unit_error
449: (p_module_name => 'AME_ACTION_TYPES'
450: ,p_hook_type => 'AI');
451: --
452: end;

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

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

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

529: ,p_rec in out nocopy ame_aty_shd.g_rec_type
530: ) is
531: --
532: l_proc varchar2(72) := g_package||'ins';
533: l_datetrack_mode varchar2(30) := hr_api.g_insert;
534: l_validation_start_date date;
535: l_validation_end_date date;
536: --
537: Begin