APPS.PAY_LIV_INS dependencies on HR_API

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

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

Line 197: When hr_api.check_integrity_violated Then

193: pay_liv_shd.g_api_dml := false; -- Unset the api dml status
194: hr_utility.set_location(' Leaving:'||l_proc, 15);
195: --
196: Exception
197: When hr_api.check_integrity_violated Then
198: -- A check constraint has been violated
199: pay_liv_shd.g_api_dml := false; -- Unset the api dml status
200: pay_liv_shd.constraint_error
201: (p_constraint_name => hr_api.strip_constraint_name(SQLERRM));

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

197: When hr_api.check_integrity_violated Then
198: -- A check constraint has been violated
199: pay_liv_shd.g_api_dml := false; -- Unset the api dml status
200: pay_liv_shd.constraint_error
201: (p_constraint_name => hr_api.strip_constraint_name(SQLERRM));
202: When hr_api.unique_integrity_violated Then
203: -- Unique integrity has been violated
204: pay_liv_shd.g_api_dml := false; -- Unset the api dml status
205: pay_liv_shd.constraint_error

Line 202: When hr_api.unique_integrity_violated Then

198: -- A check constraint has been violated
199: pay_liv_shd.g_api_dml := false; -- Unset the api dml status
200: pay_liv_shd.constraint_error
201: (p_constraint_name => hr_api.strip_constraint_name(SQLERRM));
202: When hr_api.unique_integrity_violated Then
203: -- Unique integrity has been violated
204: pay_liv_shd.g_api_dml := false; -- Unset the api dml status
205: pay_liv_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.unique_integrity_violated Then
203: -- Unique integrity has been violated
204: pay_liv_shd.g_api_dml := false; -- Unset the api dml status
205: pay_liv_shd.constraint_error
206: (p_constraint_name => hr_api.strip_constraint_name(SQLERRM));
207: When Others Then
208: pay_liv_shd.g_api_dml := false; -- Unset the api dml status
209: Raise;
210: End dt_insert_dml;

Line 417: when hr_api.cannot_find_prog_unit then

413: );
414: --
415: exception
416: --
417: when hr_api.cannot_find_prog_unit then
418: --
419: hr_api.cannot_find_prog_unit_error
420: (p_module_name => 'PAY_LINK_INPUT_VALUES_F'
421: ,p_hook_type => 'AI');

Line 419: hr_api.cannot_find_prog_unit_error

415: exception
416: --
417: when hr_api.cannot_find_prog_unit then
418: --
419: hr_api.cannot_find_prog_unit_error
420: (p_module_name => 'PAY_LINK_INPUT_VALUES_F'
421: ,p_hook_type => 'AI');
422: --
423: end;

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

448: --
449: -- Post Failure:
450: -- The Lck process can fail for:
451: -- 1) When attempting to lock the row the row could already be locked by
452: -- another user. This will raise the HR_Api.Object_Locked exception.
453: -- 2) When attempting to the lock the parent which doesn't exist.
454: -- For the entity to be locked the parent must exist!
455: --
456: -- Developer Implementation Notes:

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

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