APPS.PAY_CAL_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 202: When hr_api.check_integrity_violated Then

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

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

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

Line 207: When hr_api.unique_integrity_violated Then

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

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

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

Line 425: when hr_api.cannot_find_prog_unit then

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

Line 427: hr_api.cannot_find_prog_unit_error

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

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

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

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

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