DBA Data[Home] [Help]

APPS.PER_PGS_INS dependencies on HR_API

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

112: --
113: -- If the datetrack_mode is not INSERT then we must populate the WHO
114: -- columns with the 'old' creation values and 'new' updated values.
115: --
116: If (p_datetrack_mode <> hr_api.g_insert) then
117: hr_utility.set_location(l_proc, 10);
118: --
119: -- Get the object version number for the insert
120: --

Line 203: When hr_api.check_integrity_violated Then

199: per_pgs_shd.g_api_dml := false; -- Unset the api dml status
200: hr_utility.set_location(' Leaving:'||l_proc, 15);
201: --
202: Exception
203: When hr_api.check_integrity_violated Then
204: -- A check constraint has been violated
205: per_pgs_shd.g_api_dml := false; -- Unset the api dml status
206: per_pgs_shd.constraint_error
207: (p_constraint_name => hr_api.strip_constraint_name(SQLERRM));

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

203: When hr_api.check_integrity_violated Then
204: -- A check constraint has been violated
205: per_pgs_shd.g_api_dml := false; -- Unset the api dml status
206: per_pgs_shd.constraint_error
207: (p_constraint_name => hr_api.strip_constraint_name(SQLERRM));
208: When hr_api.unique_integrity_violated Then
209: -- Unique integrity has been violated
210: per_pgs_shd.g_api_dml := false; -- Unset the api dml status
211: per_pgs_shd.constraint_error

Line 208: When hr_api.unique_integrity_violated Then

204: -- A check constraint has been violated
205: per_pgs_shd.g_api_dml := false; -- Unset the api dml status
206: per_pgs_shd.constraint_error
207: (p_constraint_name => hr_api.strip_constraint_name(SQLERRM));
208: When hr_api.unique_integrity_violated Then
209: -- Unique integrity has been violated
210: per_pgs_shd.g_api_dml := false; -- Unset the api dml status
211: per_pgs_shd.constraint_error
212: (p_constraint_name => hr_api.strip_constraint_name(SQLERRM));

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

208: When hr_api.unique_integrity_violated Then
209: -- Unique integrity has been violated
210: per_pgs_shd.g_api_dml := false; -- Unset the api dml status
211: per_pgs_shd.constraint_error
212: (p_constraint_name => hr_api.strip_constraint_name(SQLERRM));
213: When Others Then
214: per_pgs_shd.g_api_dml := false; -- Unset the api dml status
215: Raise;
216: End dt_insert_dml;

Line 427: when hr_api.cannot_find_prog_unit then

423: );
424: --
425: exception
426: --
427: when hr_api.cannot_find_prog_unit then
428: --
429: hr_api.cannot_find_prog_unit_error
430: (p_module_name => 'PER_GRADE_SPINES_F'
431: ,p_hook_type => 'AI');

Line 429: hr_api.cannot_find_prog_unit_error

425: exception
426: --
427: when hr_api.cannot_find_prog_unit then
428: --
429: hr_api.cannot_find_prog_unit_error
430: (p_module_name => 'PER_GRADE_SPINES_F'
431: ,p_hook_type => 'AI');
432: --
433: end;

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

458: --
459: -- Post Failure:
460: -- The Lck process can fail for:
461: -- 1) When attempting to lock the row the row could already be locked by
462: -- another user. This will raise the HR_Api.Object_Locked exception.
463: -- 2) When attempting to the lock the parent which doesn't exist.
464: -- For the entity to be locked the parent must exist!
465: --
466: -- Developer Implementation Notes:

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

517: ,p_rec in out nocopy per_pgs_shd.g_rec_type
518: ) is
519: --
520: l_proc varchar2(72) := g_package||'ins';
521: l_datetrack_mode varchar2(30) := hr_api.g_insert;
522: l_validation_start_date date;
523: l_validation_end_date date;
524: --
525: Begin