DBA Data[Home] [Help]

APPS.PER_DIS_INS dependencies on HR_API

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

99: --
100: -- If the datetrack_mode is not INSERT then we must populate the WHO
101: -- columns with the 'old' creation values and 'new' updated values.
102: --
103: If (p_datetrack_mode <> hr_api.g_insert) then
104: hr_utility.set_location(l_proc, 10);
105: --
106: -- Select the 'old' created values
107: --

Line 313: When hr_api.check_integrity_violated Then

309: --
310: hr_utility.set_location(' Leaving:'||l_proc, 15);
311: --
312: Exception
313: When hr_api.check_integrity_violated Then
314: -- A check constraint has been violated
315: --
316: per_dis_shd.constraint_error
317: (p_constraint_name => hr_api.strip_constraint_name(SQLERRM));

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

313: When hr_api.check_integrity_violated Then
314: -- A check constraint has been violated
315: --
316: per_dis_shd.constraint_error
317: (p_constraint_name => hr_api.strip_constraint_name(SQLERRM));
318: When hr_api.unique_integrity_violated Then
319: -- Unique integrity has been violated
320: --
321: per_dis_shd.constraint_error

Line 318: When hr_api.unique_integrity_violated Then

314: -- A check constraint has been violated
315: --
316: per_dis_shd.constraint_error
317: (p_constraint_name => hr_api.strip_constraint_name(SQLERRM));
318: When hr_api.unique_integrity_violated Then
319: -- Unique integrity has been violated
320: --
321: per_dis_shd.constraint_error
322: (p_constraint_name => hr_api.strip_constraint_name(SQLERRM));

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

318: When hr_api.unique_integrity_violated Then
319: -- Unique integrity has been violated
320: --
321: per_dis_shd.constraint_error
322: (p_constraint_name => hr_api.strip_constraint_name(SQLERRM));
323: When Others Then
324: --
325: Raise;
326: End dt_insert_dml;

Line 637: when hr_api.cannot_find_prog_unit then

633: );
634: --
635: exception
636: --
637: when hr_api.cannot_find_prog_unit then
638: --
639: hr_api.cannot_find_prog_unit_error
640: (p_module_name => 'PER_DISABILITIES_F'
641: ,p_hook_type => 'AI');

Line 639: hr_api.cannot_find_prog_unit_error

635: exception
636: --
637: when hr_api.cannot_find_prog_unit then
638: --
639: hr_api.cannot_find_prog_unit_error
640: (p_module_name => 'PER_DISABILITIES_F'
641: ,p_hook_type => 'AI');
642: --
643: end;

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

668: --
669: -- Post Failure:
670: -- The Lck process can fail for:
671: -- 1) When attempting to lock the row the row could already be locked by
672: -- another user. This will raise the HR_Api.Object_Locked exception.
673: -- 2) When attempting to the lock the parent which doesn't exist.
674: -- For the entity to be locked the parent must exist!
675: --
676: -- Developer Implementation Notes:

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

730: ,p_rec in out nocopy per_dis_shd.g_rec_type
731: ) is
732: --
733: l_proc varchar2(72) := g_package||'ins';
734: l_datetrack_mode varchar2(30) := hr_api.g_insert;
735: l_validation_start_date date;
736: l_validation_end_date date;
737: --
738: Begin